Fedora’s Change Process is important to coordinate the development of the next Fedora release. We need to know about disrupting changes coming to the next release to set the scope of release, but it also helps as marketing tool even for leaf changes. For more details on Change Process, see the Changes Policy.
The Program Manager’s key responsibility is to maintain the Changes Process — announcements, submission, processing, tracking, deferring, dropping. Completed Changes are closed as part of the Release Day SOP. One of the main responsibilities is helping Change owners through the submission process. The Program Manager works on the Changes Policy with the Fedora Engineering Steering Committee (FESCo), Working Groups and other Fedora teams and bodies (documentation, marketing, etc.).
Want to help? Learn how to contribute to Fedora Docs ›