(→Ruoli Collaborazione nel Infrastructure Project)
|Line 17:||Line 17:|
Infrastructure , Fedora. IRC e mail.
* Infrastructure - [[KevinFenzi | Kevin Fenzi]]
* /Package - [[DennisGilmore | Dennis Gilmore]]
* Security - [[LukeMacken | Luke Macken]]
* Manager - [[ToshioKuratomi | Toshio Kuratomi]]
Fedora . Fedora Project Board. , Fedora Project Board, .
[[Infrastructure/Officers | Officers]].
== Communicating ==
== Communicating ==
Revision as of 14:48, 8 March 2012
- 1 Ruoli Collaborazione nel Infrastructure Project
- 2 Chi sono
- 3 Communicating
- 4 Contribute to Fedora Infrastructure
- 5 Our Architecture
- 6 Bugs and Requests
- 7 Donations
Ruoli Collaborazione nel Infrastructure Project
Il Team Infrastructure è composto da volontari e professionisti che gesticono server, costruiscono strumenti ed utility e creano nuove applicazioni per rendere più agevole lo sviluppo di Fedora. Sono presenti in tutto il mondo e comunicano principalmente tramite IRC e mail.
La lista dei responsabili è un tentativo per portare maggiore ordine e proprietà a Fedora Infrastructure.
Chi è responsabile:
- Guida Infrastructure - Kevin Fenzi
- Manager BuildSystem/Package - Dennis Gilmore
- Responsabile Security - Luke Macken
- Manager Sviluppo - Toshio Kuratomi
I responsabili decidono cosa è necessario fare nelle operazioni giornaliere nei vari servizi infrastrutturali Fedora . Loro stessi lavorano per gli sviluppatori e gli utenti finali ma ultimamente riferiscono al Fedora Project Board. Fondamentalmente fanno il possibile per risolvere i problemi e colmare le esigenze, in caso la decisione finale spetta al Fedora Project Board, anche se succede raramente.
Per maggiori informazioni su responsabili e metodo d'amministrazione, vedere la pagina Officers.
The Infrastructure Team coordinates their activities using a variety of tools. Our primary methods of communication are weekly IRC meetings, the IRC channellocated on freenode.net, and the mailing list.
We also hold weekly meetings ineach Thursday at 19:00 UTC.
See the Meetings page for details and historical archives.
You can find core members and contributors in thechannel.
The mailing list of the Fedora Infrastructure Project is: infrastructure
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 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.