- 1 Contributing Roles in the Infrastructure Project
- 2 About Us
- 3 Communicating
- 4 Contribute to Fedora Infrastructure
- 5 Our Architecture
- 6 Bugs and Requests
- 7 Donations
Contributing Roles in the Infrastructure Project
The Infrastructure Team consists of dedicated volunteers and professionals managing the servers, building the tools and utilities, and creating new applications to make Fedora development a smoother process. We're located all over the globe and communicate primarily by IRC and e-mail.
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.
The Infrastructure Team coordinates their activities using a variety of tools. Our primary methods of communication are weekly IRC meetings, the IRC channel #fedora-admin located on irc.freenode.net, and the mailing list.
We hold weekly meetings in #fedora-meeting each Thursday at 19:00 UTC.
See the Meetings page for details and historical archives.
You can find core members and contributors on irc.freenode.net in the #fedora-admin channel. (Need help?)
The mailing list for the Fedora Infrastructure project is: firstname.lastname@example.org .
Contribute to Fedora Infrastructure
Fedora is known for creating and using new technologies. The Infrastructure team helps build many of these new technologies and uses many of them on a regular basis. We are always interested in discussing these technologies from an academic and theoretical perspective.
If you're ready to work with the Fedora Infrastructure team we're looking for smart, dedicated system administrators and developers to help maintain our systems and write code. The Fedora Infrastructure team is a perfect way to give back to the community! So what are you waiting for? Take a look at our Getting Started Page!
Fedora User and Developer Conference (FUDCon)
Fedora holds four conferences each year. These conferences are held in various parts of the world. These conferences provide contributors with an opportunity to work together in real-time. If you are coming to a FUDCon and would like to work on something in particular that is infrastructure related then please add it to the appropriate list:
An overview of our technical Network Architecture is available online. If you have a question or constructive comment about our Network Architecture please send an e-mail to our admin inbox or stop by the #fedora-admin channel on irc.freenode.net.
The Fedora Infrastructure team develops, deploys, and maintains various services for the Fedora Project.
Do you have a desire to work with us on a new project and need resources? Then please read our Request For Resources section.
Please note that for scripts and services written especially for Fedora, we have a licensing policy and prefer using the GPL (v2) or LGPL (v2). If you would like to use a newer version of these two licenses or a different license please start a discussion through our regular meetings, IRC or the mailing list. The licensing policy page contains details and answers to frequently asked questions so please review it before asking us questions.
Standard Operating Procedures
Working on a ticket and need to remember which commands to run to create a new hosted project? Or notice that a service is down and want to troubleshoot what's wrong with it? The Category:Infrastructure SOPs page contains instructions on common issues and resolutions and how to go about implementing them.