m (Fixed missing curly bracket) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 16: | Line 16: | ||
== About Us == | == About Us == | ||
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 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 / Matrix and e-mail. | ||
=== Officers === | === Officers === | ||
| Line 25: | Line 25: | ||
* Infrastructure Lead - [[ user:Kevin |Kevin Fenzi]] | * Infrastructure Lead - [[ user:Kevin |Kevin Fenzi]] | ||
* Security Officer - [[ user:Puiterwijk |Patrick Uiterwijk]] | * Security Officer - [[ user:Puiterwijk |Patrick Uiterwijk]] | ||
* Development Manager - [[ user: | * Development Manager - [[ user:abompard|Aurélien Bompard]] | ||
* Quality Engineering - [[ user:tflink |Tim Flink ]] | * Quality Engineering - [[ user:tflink |Tim Flink ]] | ||
| Line 51: | Line 51: | ||
The mailing list of the Fedora Infrastructure Project is: {{fplist|infrastructure}} | The mailing list of the Fedora Infrastructure Project is: {{fplist|infrastructure}} | ||
=== Fedora Discussions === | |||
Our category/tag in Fedora Discussion is [https://discussion.fedoraproject.org/tag/infrastructure-team infrastructure-team]. | |||
== Contribute to Fedora Infrastructure == | == Contribute to Fedora Infrastructure == | ||
| Line 76: | Line 81: | ||
Do you have a desire to work with us on a new project and need resources? Then please read our [[Request For Resources]] section. | Do you have a desire to work with us on a new project and need resources? Then please read our [[Request For Resources]] section. | ||
Here's a list of [[Infrastructure/Projects]] that are on our plate. If you're a developer and you want to contribute to the Fedora Services, this is a good place to start. | |||
Please note that for scripts and services written especially for Fedora, we have a [[Infrastructure Licensing|licensing policy]] and prefer using the GPL (v2+) or LGPL (v2+). If you would like to use only 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 [[Infrastructure Licensing|licensing policy]] page contains details and answers to frequently asked questions so please review it before asking us questions. | Please note that for scripts and services written especially for Fedora, we have a [[Infrastructure Licensing|licensing policy]] and prefer using the GPL (v2+) or LGPL (v2+). If you would like to use only 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 [[Infrastructure Licensing|licensing policy]] page contains details and answers to frequently asked questions so please review it before asking us questions. | ||
| Line 81: | Line 88: | ||
=== Standard Operating Procedures === | === 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 Fedora Infrastructure team maintains a set of [https:// | 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 Fedora Infrastructure team maintains a set of [https://docs.fedoraproject.org/en-US/infra/ Standard Operating Procedures (SOPs)] that contain instructions on how to maintain each service we run. See something missing from the SOPs? Contribute to [https://pagure.io/infra-docs-fpo/ infrastructure documentation repository]. | ||
== Bugs and Requests == | == Bugs and Requests == | ||
Latest revision as of 10:25, 16 February 2024
Contributing Roles in the Infrastructure Project
About Us
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 / Matrix and e-mail.
Officers
The team has officers for a number of areas, please consult with them on matters under their area:
Who is responsible:
* Infrastructure Lead - Kevin Fenzi * Security Officer - Patrick Uiterwijk * Development Manager - Aurélien Bompard * Quality Engineering - Tim Flink
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 Council. 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 Council. Such decisions, however, are rare.
For more information on our officers and governance method see our Officers page.
Communicating
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 libera.chat, and the mailing list.
| How to contact the Infrastructure team | |
|---|---|
| Mailing list: infrastructure Visit this link to sign up for the email list for the Infrastructure team. |
Chat: #fedora-admin[?] This is where real-time chat with Infrastructure team members happens. |
Application development efforts take place in the #fedora-apps[?] IRC channel, and system administration related efforts take place in the #fedora-noc[?] IRC channel.
Meetings
We also hold weekly meetings in #fedora-meeting-3[?] each Thursday at 16:00 UTC. See the UTC Howto for instructions to convert UTC to your local time.
See the meetings page for details and historical archives.
IRC
You can find core members and contributors in the #fedora-admin[?] channel.
Additionally, for things specific to application development and testing we have the #fedora-apps[?] channel, and for things related to alerts/outages and general sysadmin tasks the #fedora-noc[?] channel.
New to IRC? Have a read of our Beginner's Guide to IRC Beginner's Guide To IRC -- Fedora Magazine
Mailing list
The mailing list of the Fedora Infrastructure Project is: infrastructure
Fedora Discussions
Our category/tag in Fedora Discussion is infrastructure-team.
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!
Our Architecture
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.libera.chat, or mail our list at infrastructure.
Infrastructure health status
You can quickly check if there are any known problems ongoing in our infrastructure on our status page:
Note that this page is hosted in a completely different infrastructure (OpenShift online), and is manually updated when we are working on issues. So, check status first and if you don't see the issue you are hitting, report it to us.
Fedora Services
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.
Here's a list of Infrastructure/Projects that are on our plate. If you're a developer and you want to contribute to the Fedora Services, this is a good place to start.
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 only 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 Fedora Infrastructure team maintains a set of Standard Operating Procedures (SOPs) that contain instructions on how to maintain each service we run. See something missing from the SOPs? Contribute to infrastructure documentation repository.
Bugs and Requests
Fedora Infrastructure Bugs and Requests are tracked in a pagure.io instance.
Make sure you've read the CommonProblems page and the ReportProblem page before reporting a bug or filing a request. Thank you for your help!
Donations
The Fedora Project has occasionally received donations of hardware and co-location space which is used for the Fedora Infrastructure.
If you are interested in donating, please see our donations page. You too could appear with our other Sponsors on our sponsors page.