Infrastructure/GettingStarted

From FedoraProject

< Infrastructure(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
m (Cleanup.)
Line 1: Line 1:
<!-- Do not remove
+
{{header|infra}}
-->
+
<!-- StartHeader
+
-->
+
<pre>#!html
+
<div style="height:66px; width:100%; background-color:#002867;">
+
<a href = "http://fedoraproject.org/wiki/Infrastructure"> <img style="float:right;padding-top:3px;" src="http://fedoraproject.org/wiki/Infrastructure?action=AttachFile&do=get&target=InfrastructureTeamN1.png" /></a>
+
</div>
+
 
+
<HR style="height:2px; background-color:#00578E;" />
+
</pre>
+
<!-- EndHeader
+
-->
+
  
 
== Help Wanted ==
 
== Help Wanted ==
Line 35: Line 23:
 
Joining the Infrastructure group is easy.
 
Joining the Infrastructure group is easy.
 
* Subscribe to the [http://www.redhat.com/mailman/listinfo/fedora-infrastructure-list fedora-infrastructure-list@redhat.com]  
 
* Subscribe to the [http://www.redhat.com/mailman/listinfo/fedora-infrastructure-list fedora-infrastructure-list@redhat.com]  
* Sign up for a [[Infrastructure/AccountSystem|  Fedora Account]]  and sign the [[Legal/Licenses/CLA| CLA]]  
+
* Sign up for a [[Infrastructure/AccountSystem|  Fedora Account]]  and sign the [[Legal/Licenses/CLA|CLA]]  
 
* Get [[WikiEditing|  Wiki Edit]]  access (Note, the wiki and the Fedora Accounts System are currently not linked, you'll need an account on both)
 
* Get [[WikiEditing|  Wiki Edit]]  access (Note, the wiki and the Fedora Accounts System are currently not linked, you'll need an account on both)
 
* Send an introduction with some notes about your experience and skill level to the fedora-infrastructure list (Don't forget this!)
 
* Send an introduction with some notes about your experience and skill level to the fedora-infrastructure list (Don't forget this!)
* Become familiar with the [[Infrastructure| Infrastructure]]  section on the wiki (Especially the [[Infrastructure/Schedule|  Schedule]]  page)
+
* Become familiar with the [[Infrastructure|Infrastructure]]  section on the wiki (Especially the [[Infrastructure/Schedule|  Schedule]]  page)
* Attend the weekly [[Infrastructure/Meetings| Meetings]]  on IRC
+
* Attend the weekly [[Infrastructure/Meetings|Meetings]]  on IRC
* Once you are familiar with the team and know some people, take some time to join a [[Infrastructure/FIGs| FIG]]  and [[Infrastructure/GettingSponsored| Get Sponsored]]  
+
* Once you are familiar with the team and know some people, take some time to join a [[Infrastructure/FIGs|FIG]]  and [[Infrastructure/GettingSponsored|Get Sponsored]]  
 
+
  
 
Even if you don't want to be involved on a regular basis at this point, please feel free to watch over things and report bugs and RFEs as you see fit.  Showing interest now is a great way to make it easier to join the team's activities later.
 
Even if you don't want to be involved on a regular basis at this point, please feel free to watch over things and report bugs and RFEs as you see fit.  Showing interest now is a great way to make it easier to join the team's activities later.
 
  
 
== How the team works ==
 
== How the team works ==
Line 52: Line 38:
 
New members are encouraged to join the list and attend a few meetings before they request sponsorship.  Getting a feel for how the group works is important.
 
New members are encouraged to join the list and attend a few meetings before they request sponsorship.  Getting a feel for how the group works is important.
  
----
 
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]

Revision as of 21:11, 25 May 2008

Infrastructure InfrastructureTeamN1.png


Help Wanted

We're looking for dedicated and energetic people to join the fun times in the Fedora Infrastructure team. What fun stuff is waiting to be done?

  • Getting the personal thanks of the many Fedora developers after helping fix a system issue for them.
  • Running the servers that make the Fedora project possible
  • Creating new custom applications that help developers be more productive doing what they do best: developing
  • Building tools that enhance and grow the Fedora community

The skills you may want to learn to do this work include:

  • Being nice to other hard-working hackers and helping them do what they enjoy
  • Knowing how to write scripts for system administration
  • Knowing how to write web applications using Python and SQL or equivalent technologies (*** we can especially use skills in this area ***)
  • Knowing how the Fedora project works behind the scenes

Other pluses

  • Have previous systems admin experience
  • Have access to your own testing machines for testing and proof of concepts (Huge plus! Our resources are limited, especially for testing)
  • Work in other areas of Fedora like Packaging or Documentation

Getting Started

Joining the Infrastructure group is easy.

  • Subscribe to the fedora-infrastructure-list@redhat.com
  • Sign up for a Fedora Account and sign the CLA
  • Get Wiki Edit access (Note, the wiki and the Fedora Accounts System are currently not linked, you'll need an account on both)
  • Send an introduction with some notes about your experience and skill level to the fedora-infrastructure list (Don't forget this!)
  • Become familiar with the Infrastructure section on the wiki (Especially the Schedule page)
  • Attend the weekly Meetings on IRC
  • Once you are familiar with the team and know some people, take some time to join a FIG and Get Sponsored

Even if you don't want to be involved on a regular basis at this point, please feel free to watch over things and report bugs and RFEs as you see fit. Showing interest now is a great way to make it easier to join the team's activities later.

How the team works

The team itself consists of volunteer and Red Hat members. Our preferred method of communication is on irc.freenode.net in #fedora-admin though we also heavily use the fedora-infrastructure-list. We try to be as transparent as possible though when security is involved we'll use our private list.

New members are encouraged to join the list and attend a few meetings before they request sponsorship. Getting a feel for how the group works is important.