From Fedora Project Wiki
(A few more SOP for Fedora Program Manager) |
|||
| Line 14: | Line 14: | ||
* [[Fedora_Program_Management/GoNoGoSOP| The Go/No-Go meeting]] | * [[Fedora_Program_Management/GoNoGoSOP| The Go/No-Go meeting]] | ||
* [[Fedora_Program_Management/ReadinessSOP| The Readiness meeting]] | * [[Fedora_Program_Management/ReadinessSOP| The Readiness meeting]] | ||
* [[Fedora_Program_Management/ChangesSOP | Change Process]] | |||
* [[Fedora_Program_Management/EOLRebaseSOP | End Of Life and Rawhide Rebase]] | |||
* [[Fedora_Program_Management/ScheduleSOP | Schedule maintenance]] | |||
= Useful links = | = Useful links = | ||
Revision as of 11:22, 16 March 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 hold by Jaroslav Reznik <jreznik@fedoraproject.org>.
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