From Fedora Project Wiki
(use wiki syntax for wiki link) |
(remove finished project) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
** You will need it to login to various systems | ** You will need it to login to various systems | ||
** You will need it to upload code changes, make changes to this wiki and etc. | ** You will need it to upload code changes, make changes to this wiki and etc. | ||
* After you have created your account and signed the | * After you have created your account and signed the FPCA, you should then subscribe to the {{fplist|rel-eng}} mailing list. | ||
* Join the #fedora-releng channel on Freenode. | * Join the #fedora-releng channel on Freenode. | ||
* Join us for our [[ReleaseEngineering#Meetings|weekly meeting]]. | * Join us for our [[ReleaseEngineering#Meetings|weekly meeting]]. | ||
| Line 15: | Line 15: | ||
= Next Steps = | = Next Steps = | ||
* Decide if there's an area of Release Engineering which interests you and let the team know. If there's an applicable [[Category:Release_Engineering_SOPs|Release Engineering SOP]], familiarize yourself with it. If there's not and you think there should be one, let us know. | * Decide if there's an area of Release Engineering which interests you and let the team know. If there's an applicable [[:Category:Release_Engineering_SOPs|Release Engineering SOP]], familiarize yourself with it. If there's not and you think there should be one, let us know. | ||
* Monitor the tickets queue | * Monitor the [https://fedorahosted.org/rel-eng/report/1 tickets queue] for tasks that interest you. | ||
* Assist with one of the EasyFix tickets | * Assist with one of the [https://fedoraproject.org/easyfix/#rel-eng EasyFix tickets] or a coding/scripting task below, which do not require access to privileged systems. Submit patches to the [https://fedorahosted.org/rel-eng/newticket rel-eng̣] issue tracker (or the relevant project's mailing list). | ||
= Available Projects = | = Available Projects = | ||
| Line 23: | Line 23: | ||
The projects/tasks below are mainly coding or scripting tasks which (mostly) do not require access to privileged systems to work on. | The projects/tasks below are mainly coding or scripting tasks which (mostly) do not require access to privileged systems to work on. | ||
* Add more things to this list | * Add more things to this list | ||
Latest revision as of 13:40, 7 September 2014
Draft Document
This document is a new draft and may contain wild inaccuracies. You are likely to be eaten by a grue.
This document is a new draft and may contain wild inaccuracies. You are likely to be eaten by a grue.
Basic Requirements
- First you will need to read through and understand how to be a successful contributor.
- Next you will need to create a Fedora Account:
- This account will be used for just about everything you do as a member of the Fedora Community
- You will need it to sign the FPCA which is required to contribute to the Fedora Community
- You will need it to login to various systems
- You will need it to upload code changes, make changes to this wiki and etc.
- After you have created your account and signed the FPCA, you should then subscribe to the rel-eng mailing list.
- Join the #fedora-releng channel on Freenode.
- Join us for our weekly meeting.
Next Steps
- Decide if there's an area of Release Engineering which interests you and let the team know. If there's an applicable Release Engineering SOP, familiarize yourself with it. If there's not and you think there should be one, let us know.
- Monitor the tickets queue for tasks that interest you.
- Assist with one of the EasyFix tickets or a coding/scripting task below, which do not require access to privileged systems. Submit patches to the rel-eng̣ issue tracker (or the relevant project's mailing list).
Available Projects
The projects/tasks below are mainly coding or scripting tasks which (mostly) do not require access to privileged systems to work on.
- Add more things to this list