Fedora Infrastructure administration homepage
Fedora Infrastructure Administration homepage
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.
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 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:
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.
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.
The Infrastructure agenda Schedule contains information about:
- Ongoing tasks
- Wishlist tasks
- Fedora Infrastructure Agenda
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.
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:
We are currently discussing the new VCS for some future version of Fedora. Here we compare the following VCS:
Go to the VCS choice page for more information.
MirrorManager is our database tracking all public and private Fedora mirrors. It has an administrative interface at
See Infrastructure/Mirroring for instructions on mirroring Fedora.
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.
The mailing list for the Fedora Infrastructure project is email@example.com .
The officers list is an attempt to bring more order and ownership to the Fedora Infrastructure.
Who is responsible:
- Infrastructure Lead - Mike McGrath
- Build System/Package Manager - Dennis Gilmore
- OS Manager - Jeffrey Tadlock
- Security Officer - Luke Macken
- Development Manager - Toshio Kuratomi
- Red Hat Liaison - Warren Togami
- Community Liaison - Seth Vidal
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.