Infrastructure

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Communicating)
(bunch of cleanups)
 
(11 intermediate revisions by 7 users not shown)
Line 3: Line 3:
  
 
== Contributing Roles in the Infrastructure Project ==
 
== Contributing Roles in the Infrastructure Project ==
{{admon/tip|Contributing roles|These are only suggestions for contributing roles. Only your imagination sets the limits. }}
 
  
 
{|class="nobordersplz"
 
{|class="nobordersplz"
Line 20: Line 19:
  
 
=== Officers ===
 
=== Officers ===
The officers list is an attempt to bring more order and ownership to the Fedora Infrastructure.
+
 
 +
The team has officers for a number of areas, please consult with them on matters under their area:
 
<BR>
 
<BR>
 
Who is responsible:
 
Who is responsible:
 
  * Infrastructure Lead - [[KevinFenzi | Kevin Fenzi]]  
 
  * Infrastructure Lead - [[KevinFenzi | Kevin Fenzi]]  
 
  * Build System/Package Manager - [[DennisGilmore | Dennis Gilmore]]  
 
  * Build System/Package Manager - [[DennisGilmore | Dennis Gilmore]]  
  * Security Officer - [[LukeMacken | Luke Macken]]  
+
  * Security Officer - [[ User:Puiterwijk | Patrick Uiterwijk]]  
  * Development Manager - [[ToshioKuratomi | Toshio Kuratomi]]  
+
  * Development Manager - [[user:pingou|Pierre-Yves Chibon]]
 +
* Quality Engineering - [[ User:tflink | 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 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 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.
 
<BR>
 
<BR>
 
For more information on our officers and governance method see our [[Infrastructure/Officers | Officers]]  page.
 
For more information on our officers and governance method see our [[Infrastructure/Officers | Officers]]  page.
Line 34: Line 35:
 
== Communicating ==
 
== Communicating ==
 
The Infrastructure Team coordinates their activities using a variety of tools. Our primary methods of communication are weekly IRC meetings, the IRC channel {{fpchat|#fedora-admin}} located on freenode.net, and the mailing list.  
 
The Infrastructure Team coordinates their activities using a variety of tools. Our primary methods of communication are weekly IRC meetings, the IRC channel {{fpchat|#fedora-admin}} located on freenode.net, and the mailing list.  
{{Team contact|Infrastructure|infrastructure|#fedora-admin}}
+
{{Team contact|Infrastructure|infrastructure|#fedora-admin}}. Application development efforts take place in the {{fpchat|#fedora-apps}} IRC channel, and system administration related efforts take place in the {{fpchat|#fedora-noc} IRC channel.
 
=== Meetings ===
 
=== Meetings ===
We also hold weekly meetings in {{fpchat|#fedora-meeting}} each '''Thursday''' at '''19:00 UTC'''. See the [[UTCHowto|UTC Howto]] for instructions to convert UTC to your local time.  
+
We also hold weekly meetings in {{fpchat|#fedora-meeting}} each '''Thursday''' at '''18:00 UTC'''. See the [[UTCHowto|UTC Howto]] for instructions to convert UTC to your local time.  
 
<div style="float: right;">[[Image:WikiElements_meetingL.png]]</div>
 
<div style="float: right;">[[Image:WikiElements_meetingL.png]]</div>
  
See the [[/Meetings|  Meetings]] page for details and historical archives.
+
See the [https://meetbot.fedoraproject.org meetings] page for details and historical archives.
  
 
=== IRC ===
 
=== IRC ===
 
You can find core members and contributors in the {{fpchat|#fedora-admin}} channel.
 
You can find core members and contributors in the {{fpchat|#fedora-admin}} channel.
 +
 +
Additionally, for things specific to application development and testing we have the {{fpchat|#fedora-apps}} channel, and for things related to alerts/outages and general sysadmin tasks the {{fpchat|#fedora-noc}} channel.
 +
 +
 +
New to IRC?  Have a read of our  Beginner's Guide to IRC      [https://fedoramagazine.org/beginners-guide-irc/ Beginner's Guide To IRC -- Fedora Magazine]
 +
 
=== Mailing list ===
 
=== Mailing list ===
 +
 
The mailing list of the Fedora Infrastructure Project is: {{fplist|infrastructure}}
 
The mailing list of the Fedora Infrastructure Project is: {{fplist|infrastructure}}
  
Line 52: Line 60:
 
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 [[Infrastructure/GettingStarted|  Getting Started Page]]!
 
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 [[Infrastructure/GettingStarted|  Getting Started Page]]!
  
=== Fedora User and Developer Conference (FUDCon) ===
+
== Our Architecture ==
  
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 [[Infrastructure/Architecture | Network Architecture]]  is available online. If you have a question or constructive comment about our [[Infrastructure/Architecture|Network Architecture]] please send an e-mail to our [mailto:admin@fedoraproject.org admin inbox] or stop by the {{fpchat|#fedora-admin}} channel on irc.freenode.net, or mail our list at {{fplist|infrastructure}}.
  
[[Infrastructure/FUDCon/Blacksburg2012 | FUDCon - Blacksburg, VA 2012]]
+
=== Infrastructure health status ===
  
[[Fedora_infrastructure_tasks_2013 | FUDCon - Lawrence, KS 2013]]
+
You can quickly check if there are any known problems ongoing in our infrastructure at our status page:
  
== Our Architecture ==
+
[http://status.fedoraproject.org Fedora Infrastructure Status]
An overview of our technical [[Infrastructure/Architecture | Network Architecture]]  is available online. If you have a question or constructive comment about our [[Infrastructure/Architecture|Network Architecture]] please send an e-mail to our [mailto:admin@fedoraproject.org admin inbox] or stop by the {{fpchat|#fedora-admin}} channel on irc.freenode.net.
+
  
=== Infrastructure health status ===
+
Note that this page is hosted in a completely different infrastructure (OpenShift online), and is manually updated when we are working on issues.
[http://status.fedoraproject.org Fedora Infrastructure Status]
+
So, check status first and if you don't see the issue you are hitting, report it to us.  
  
 
=== Fedora Services ===
 
=== Fedora Services ===
The Fedora Infrastructure team develops, deploys, and maintains various [[Infrastructure/Services | 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 [[Infrastructure/RFR| Request For Resources]] section.
+
The Fedora Infrastructure team develops, deploys, and maintains various [https://apps.fedoraproject.org services] for the Fedora Project.
  
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 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.
+
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 [[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.
  
 
=== 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 [[:Category:Infrastructure SOPs]] page contains instructions on common issues and resolutions and how to go about implementing them.
+
 
 +
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 [[https://infrastructure.fedoraproject.org/infra/docs infra docs]] page contains instructions on common issues and resolutions and how to go about implementing them.
  
 
== Bugs and Requests ==
 
== Bugs and Requests ==
  
Fedora Infrastructure Bugs and Requests are tracked in a [https://fedorahosted.org/fedora-infrastructure Trac instance].  More information about access and usage of this system can be found on the [[Infrastructure/Tickets|Infrastructure Tickets Wiki Page]].  
+
Fedora Infrastructure Bugs and Requests are tracked in a [https://pagure.io/fedora-infrastructure pagure.io instance].
  
 
Make sure you've read the [[/CommonProblems | CommonProblems]] page and the [[/ReportProblem | ReportProblem]] page before reporting a bug or filing a request. Thank you for your help!
 
Make sure you've read the [[/CommonProblems | CommonProblems]] page and the [[/ReportProblem | ReportProblem]] page before reporting a bug or filing a request. Thank you for your help!
Line 84: Line 93:
 
== Donations ==
 
== Donations ==
  
The Fedora Project has occasionally received donations of hardware which is used for the Fedora [[Infrastructure]].
+
The Fedora Project has occasionally received donations of hardware and co-location space which is used for the Fedora [[Infrastructure]].
 
<BR>
 
<BR>
Here is our [[Donations | donations]] and [http://fedoraproject.org/sponsors sponsors]  page.
+
If you are interested in donating, please see our [[Donations | donations]] page. You too could appear with our other Sponsors on our [http://fedoraproject.org/sponsors sponsors]  page.
  
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]
 
[[Category:Fedora sub-projects]]
 
[[Category:Fedora sub-projects]]

Latest revision as of 20:22, 7 November 2016

Infrastructure InfrastructureTeamN1.png

Contents

[edit] Contributing Roles in the Infrastructure Project

Join OSDeveloper.png
OS Developer

Join WebDeveloper.png
Web Developer or Administrator

[edit] 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.

[edit] 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 
* Build System/Package Manager -  Dennis Gilmore 
* Security Officer -  Patrick Uiterwijk 
* Development Manager - Pierre-Yves Chibon
* 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.

[edit] 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 freenode.net, 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 {{fpchat|#fedora-noc} IRC channel.

[edit] Meetings

We also hold weekly meetings in #fedora-meeting[?] each Thursday at 18:00 UTC. See the UTC Howto for instructions to convert UTC to your local time.

WikiElements meetingL.png

See the meetings page for details and historical archives.

[edit] 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

[edit] Mailing list

The mailing list of the Fedora Infrastructure Project is: infrastructure

[edit] 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!

[edit] 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.freenode.net, or mail our list at infrastructure.

[edit] Infrastructure health status

You can quickly check if there are any known problems ongoing in our infrastructure at our status page:

Fedora Infrastructure Status

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.

[edit] 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.

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.

[edit] 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 [infra docs] page contains instructions on common issues and resolutions and how to go about implementing them.

[edit] 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!

[edit] 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.