m (→Account System) |
(Update some) |
||
| (18 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
The Fedora Infrastructure Administration homepage is used as a portal to a great deal of our infrastructure. It contains links to our sites, what they are, who we are, who to contact, etc. | The Fedora Infrastructure Administration homepage is used as a portal to a great deal of our infrastructure. It contains links to our sites, what they are, who we are, who to contact, etc. | ||
For any additional information, go to the [ | For any additional information, go to the [[Infrastructure]] wiki page. | ||
| Line 20: | Line 18: | ||
https://bugzilla.redhat.com | https://bugzilla.redhat.com | ||
Bugs related to Fedora Infrastructure are tracked in Fedora's ticketing system [https:// | Bugs related to Fedora Infrastructure are tracked in Fedora's ticketing system [https://fedoraproject.org/wiki/Infrastructure/Tickets Infrastructure Tickets] . | ||
<BR><BR> | <BR><BR> | ||
You found a bug, [ | You found a bug, [[Infrastructure/ReportProblem|Report it!]] | ||
=== CLA === | === CLA === | ||
The purpose of the Contributor License Agreement (CLA) is to establish copyright control under Red Hat, Inc. on behalf of the Fedora Project. By having a single entity hold copyright: | The purpose of the Contributor License Agreement (CLA) is to establish copyright control under Red Hat, Inc. on behalf of the Fedora Project. By having a single entity hold copyright: | ||
* It is easier to be more | * It is easier to be more flexible with future re-licensing needs | ||
* That one incorporated entity can handle being sued | * That one incorporated entity can handle being sued | ||
* The project can act singularly on the behalf of all the code and documentation without having to make costly and lengthy research into responses from every copyright holder | * The project can act singularly on the behalf of all the code and documentation without having to make costly and lengthy research into responses from every copyright holder | ||
| Line 33: | Line 31: | ||
All individual contributors to the Fedora Project are required to agree to the Individual Contributor License Agreement and all of their contributions are subject to it. | All individual contributors to the Fedora Project are required to agree to the Individual Contributor License Agreement and all of their contributions are subject to it. | ||
Request the [https://admin.fedoraproject.org/accounts/ | Request the [https://admin.fedoraproject.org/accounts/fpca/ The Fedora Project Individual Contributor License Agreement]. | ||
=== Package Database === | === Package Database === | ||
The [http://admin.fedoraproject.org/pkgdb/ Fedora Package Database] aims to consolidate the information on the packages present in Fedora | The [http://admin.fedoraproject.org/pkgdb/ Fedora Package Database] aims to consolidate the information on the packages present in Fedora. It will allow us to perform queries on packages and their maintainers as well as some of the administrative tasks associated with them (branch co-maintainer requests, etc.) | ||
<BR><BR> | <BR><BR> | ||
The [ | The [[Infrastructure/PackageDatabase|Fedora Package Database documentation]] page contains a lot of useful information. Go ahead and read it. | ||
=== Updates System === | === Updates System === | ||
[https://fedorahosted.org/bodhi Bodhi] is currently [https://admin.fedoraproject.org/updates deployed] and is responsible for pushing package updates for Fedora 7 and beyond. See [[Infrastructure/UpdatesSystem | [https://fedorahosted.org/bodhi Bodhi] is currently [https://admin.fedoraproject.org/updates deployed] and is responsible for pushing package updates for Fedora 7 and beyond. See [[Infrastructure/UpdatesSystem]] and the [https://fedorahosted.org/bodhi/ bodhi project homepage] for more information. | ||
=== Schedule === | === Schedule === | ||
The Infrastructure agenda [ | The Infrastructure agenda [[Infrastructure/Schedule|Schedule]] contains information about: | ||
* Ongoing tasks | * Ongoing tasks | ||
* Wishlist tasks | * Wishlist tasks | ||
| Line 51: | Line 49: | ||
=== Tickets === | === Tickets === | ||
In order to better support the Fedora developers and the community at large, the Infrastructure team has created a ticketing system to track issues, feature requests and anything else related to the Fedora infrastructure. | In order to better support the Fedora developers and the community at large, the Infrastructure team has created a ticketing system to track issues, feature requests and anything else related to the Fedora infrastructure. | ||
The [https://fedorahosted.org/fedora-infrastructure/] | The [https://fedorahosted.org/fedora-infrastructure/ Fedora Infrastructure ticketing system] requires a valid username and password in the [[Infrastructure/AccountSystem|Fedora accounting system]]. In order to request an account please see the [https://admin.fedoraproject.org/accounts/ Fedora Account System] . Those who are not able to create an account or have a pressing issue that cannot wait for account approval please send an email to tickets (at) fedoraproject [dot] org. | ||
=== Version Control === | === Version Control === | ||
The Fedora Infrastructure CVS repository holds such things as the fedora.redhat.com website, the Fedora Core "fedora-release" sources, and a mirror list manager project. | The Fedora Infrastructure CVS repository holds such things as the fedora.redhat.com website, the Fedora Core "fedora-release" sources, and a mirror list manager project. | ||
<BR><BR> | <BR><BR> | ||
You can request write access by applying for membership in the <code>cvsfedora</code> group in the [https://admin.fedoraproject.org/accounts/ Fedora Account System] . Furthermore, you must be approved and added to the appropriate ACLs. Normally, write access is granted only to those who are known and have established a prior need to commit to one of the modules in this repository. As a measure to prove yourself, you can always send us patches created using anonymous read-only access. You can file bugs and submit patches against Fedora Infrastructure using [ | You can request write access by applying for membership in the <code>cvsfedora</code> group in the [https://admin.fedoraproject.org/accounts/ Fedora Account System] . Furthermore, you must be approved and added to the appropriate ACLs. Normally, write access is granted only to those who are known and have established a prior need to commit to one of the modules in this repository. As a measure to prove yourself, you can always send us patches created using anonymous read-only access. You can file bugs and submit patches against Fedora Infrastructure using [https://bugzilla.redhat.com/ Bugzilla] . | ||
<BR><BR> | <BR><BR> | ||
A web interface for browsing this repository is available: | A web interface for browsing this repository is available: | ||
| Line 70: | Line 68: | ||
* Git | * Git | ||
Go to the [ | Go to the [[Infrastructure/VersionControl|VCS choice]] page for more information. | ||
=== Mirroring === | === Mirroring === | ||
| Line 77: | Line 75: | ||
https://admin.fedoraproject.org/mirrormanager | https://admin.fedoraproject.org/mirrormanager | ||
See [[Infrastructure/Mirroring | See [[Infrastructure/Mirroring]] for instructions on mirroring Fedora. | ||
| Line 91: | Line 89: | ||
=== IRC === | === IRC === | ||
You can find the #fedora-admin channel on [http://freenode.net/ freenode] .<BR> | You can find the #fedora-admin channel on [http://freenode.net/ freenode] .<BR> | ||
This is where we hold our weekly meetings. See the [ | This is where we hold our weekly meetings. See the [[Infrastructure/Meetings | Meetings]] page for details. | ||
{{Anchor|officers}} | {{Anchor|officers}} | ||
=== Officers === | === Officers === | ||
The officers list is an attempt to bring more order and ownership to the Fedora Infrastructure. | The officers list is an attempt to bring more order and ownership to the Fedora Infrastructure. | ||
<BR><BR> | <BR><BR> | ||
Who is responsible | Who is responsible: | ||
* Infrastructure Lead - [ | * Infrastructure Lead - [[KevinFenzi | Kevin Fenzi]] | ||
* Build System/Package Manager - [ | * Build System/Package Manager - [[DennisGilmore | Dennis Gilmore]] | ||
* Security Officer - [[LukeMacken | Luke Macken]] | |||
* Security Officer - [ | * Development Manager - [[ToshioKuratomi | Toshio Kuratomi]] | ||
* Development Manager - [ | |||
The officers generally decide what needs to be done in the day to day operations of the various Fedora infrastructure facilities. The officers themselves work for the developers and end users but ultimately report to the Fedora Project Board. This basically means that we'll try to do whatever we can to fill needs and fix things but if we refuse for whatever reason, the final decision can be made by the Fedora Project Board. Such decisions, however, are rare. | The officers generally decide what needs to be done in the day to day operations of the various Fedora infrastructure facilities. The officers themselves work for the developers and end users but ultimately report to the Fedora Project Board. This basically means that we'll try to do whatever we can to fill needs and fix things but if we refuse for whatever reason, the final decision can be made by the Fedora Project Board. Such decisions, however, are rare. | ||
<BR><BR> | <BR><BR> | ||
For more information on our officers and governance method see our [ | For more information on our officers and governance method see our [[Infrastructure/Officers | Officers]] page. | ||
== Donations == | == Donations == | ||
The Fedora Project has occasionally received donations of hardware which is used for the Fedora [ | The Fedora Project has occasionally received donations of hardware which is used for the Fedora [[Infrastructure]]. | ||
<BR><BR> | <BR><BR> | ||
Here is our [ | Here is our [[Donations | donations]] and [http://fedoraproject.org/sponsors sponsors] page. | ||
<BR><BR> | <BR><BR> | ||
Latest revision as of 22:05, 22 December 2011
The Fedora Infrastructure Administration homepage is used as a portal to a great deal of our infrastructure. It contains links to our sites, what they are, who we are, who to contact, etc.
For any additional information, go to the Infrastructure wiki page.
Infrastructure pieces
Account System
The Fedora Account System keeps track of Fedora Project contributors and the projects they work on. It is used to grant authentication and authorization to various components. This currently includes the various CVS repositories and Bugzilla .
Bugzilla
Bugzilla is the Fedora bug-tracking system and is used to submit and review bugs that have been found in Fedora distributions. Bugzilla is not an avenue for technical assistance or support, but simply a bug tracking system. If you submit a defect, please provide detailed information in your submission after you have queried Bugzilla to ensure the defect has not been reported yet. Defects will go directly to the engineer responsible for the component you filed the defect against. Engineers have many responsibilities and will get to the bugs you have submitted in due time.
Bugzilla is available at:
Bugs related to Fedora Infrastructure are tracked in Fedora's ticketing system Infrastructure Tickets .
You found a bug, Report it!
CLA
The purpose of the Contributor License Agreement (CLA) is to establish copyright control under Red Hat, Inc. on behalf of the Fedora Project. By having a single entity hold copyright:
- It is easier to be more flexible with future re-licensing needs
- That one incorporated entity can handle being sued
- The project can act singularly on the behalf of all the code and documentation without having to make costly and lengthy research into responses from every copyright holder
All individual contributors to the Fedora Project are required to agree to the Individual Contributor License Agreement and all of their contributions are subject to it.
Request the The Fedora Project Individual Contributor License Agreement.
Package Database
The Fedora Package Database aims to consolidate the information on the packages present in Fedora. It will allow us to perform queries on packages and their maintainers as well as some of the administrative tasks associated with them (branch co-maintainer requests, etc.)
The Fedora Package Database documentation page contains a lot of useful information. Go ahead and read it.
Updates System
Bodhi is currently deployed and is responsible for pushing package updates for Fedora 7 and beyond. See Infrastructure/UpdatesSystem and the bodhi project homepage for more information.
Schedule
The Infrastructure agenda Schedule contains information about:
- Ongoing tasks
- Wishlist tasks
- Fedora Infrastructure Agenda
Tickets
In order to better support the Fedora developers and the community at large, the Infrastructure team has created a ticketing system to track issues, feature requests and anything else related to the Fedora infrastructure.
The Fedora Infrastructure ticketing system requires a valid username and password in the Fedora accounting system. In order to request an account please see the Fedora Account System . Those who are not able to create an account or have a pressing issue that cannot wait for account approval please send an email to tickets (at) fedoraproject [dot] org.
Version Control
The Fedora Infrastructure CVS repository holds such things as the fedora.redhat.com website, the Fedora Core "fedora-release" sources, and a mirror list manager project.
You can request write access by applying for membership in the cvsfedora group in the Fedora Account System . Furthermore, you must be approved and added to the appropriate ACLs. Normally, write access is granted only to those who are known and have established a prior need to commit to one of the modules in this repository. As a measure to prove yourself, you can always send us patches created using anonymous read-only access. You can file bugs and submit patches against Fedora Infrastructure using Bugzilla .
A web interface for browsing this repository is available:
http://cvs.fedoraproject.org/viewcvs/?root=fedora
We are currently discussing the new VCS for some future version of Fedora. Here we compare the following VCS:
- CVS
- Subversion
- Mercurial
- Bazaar
- Git
Go to the VCS choice page for more information.
Mirroring
MirrorManager is our database tracking all public and private Fedora mirrors. It has an administrative interface at
https://admin.fedoraproject.org/mirrormanager
See Infrastructure/Mirroring for instructions on mirroring Fedora.
Communicating
Our preferred method of communication is the Mailing list though many of us hang out on IRC. Recently, officers have been chosen to aid in leading certain areas of our Infrastructure.
Mailing list
The mailing list for the Fedora Infrastructure project is fedora-infrastructure-list@redhat.com .
IRC
You can find the #fedora-admin channel on freenode .
This is where we hold our weekly meetings. See the Meetings page for details.
Officers
The officers list is an attempt to bring more order and ownership to the Fedora Infrastructure.
Who is responsible:
- Infrastructure Lead - Kevin Fenzi
- Build System/Package Manager - Dennis Gilmore
- Security Officer - Luke Macken
- Development Manager - Toshio Kuratomi
The officers generally decide what needs to be done in the day to day operations of the various Fedora infrastructure facilities. The officers themselves work for the developers and end users but ultimately report to the Fedora Project Board. This basically means that we'll try to do whatever we can to fill needs and fix things but if we refuse for whatever reason, the final decision can be made by the Fedora Project Board. Such decisions, however, are rare.
For more information on our officers and governance method see our Officers page.
Donations
The Fedora Project has occasionally received donations of hardware which is used for the Fedora Infrastructure.
Here is our donations and sponsors page.