From Fedora Project Wiki
(A few more SOP for Fedora Program Manager) |
|||
| Line 7: | Line 7: | ||
* member of Fedora Council - Auxiliary Seat, Council secretary | * member of Fedora Council - Auxiliary Seat, Council secretary | ||
The position is currently | The position is currently held by [[User:Jreznik|Jaroslav Reznik]] <jreznik@fedoraproject.org> for Fedora 22 and Jan Kurik <jkurik@redhat.com> for Fedora 23+. | ||
= Program management SOPs = | = Program management SOPs = | ||
Revision as of 07:49, 29 May 2015
Fedora Program Manager
Within the Fedora Project, the Program Manager (FPGM) is primarily responsible for:
- planning and scheduling of Fedora releases
- tracking the changes/features during the development/testing cycle
- release coordination (within QA, releng, FESCo, etc.)
- processes behind Fedora Project
- member of Fedora Council - Auxiliary Seat, Council secretary
The position is currently held by Jaroslav Reznik <jreznik@fedoraproject.org> for Fedora 22 and Jan Kurik <jkurik@redhat.com> for Fedora 23+.
Program management SOPs
This SOP (Standard Operating Procedure) section contains a list of common FPGMs tasks.
- The Go/No-Go meeting
- The Readiness meeting
- Change Process
- End Of Life and Rawhide Rebase
- Schedule maintenance
Useful links
- Schedules in HTML/ICS formats with TaskJuggler 2 sources
- Fedora Project Schedule Trac to report scheduling issues, and GIT with scripts making FPGM happier
- Fedora Release Life Cycle aka how to schedule next Fedora release