Fedora Package Maintainers Policies
This document should give you a quick overview of all the relevant policies for Fedora Package Collection. It covers only the most important things -- each section has a link to a document with more detailed explanations and examples that outline how to lay out the rules. For a full list of documents see the end of this document .
On maintaining packages
Who is allowed to modify which packages
Read on for more more details about this topic .
What to do if a Maintainer is absent
Read on for more more details about this topic
Co-Maintainership
Read on for more more details about this topic
Special rules for Packages with kernel modules
- Verify that there is an acceptable license for a kernel-module by asking on fedora-devel-list.
- A kernel-module should be merged into the upstream kernel.
- Open a review bug in bugzilla with an explanation from the maintainer of the kernel-module why it is not yet merged with the mainline kernel and a planned merge date.
- Send FESCo an email asking for permission to allow the module in Fedora. FESCo will investigate and vote if the kernel-module is suitable for Fedora.
- While anyone can review a kernel-module package, once it is set to APPROVED by the reviewer, a Fedora Sponsor or someone experienced with kernel modules should examine the package and post an additional approval notice before it is imported into CVS.
Read on for more more details about this topic
Fedora Maintenance Lifecycle Policy
PackageMaintainers/Policy/EOL,, from="^
Read on for more more details about this topic
Review workflow
What to do with stalled reviews
PackageMaintainers/Policy/StalledReviews,, from="^
Read on for more more details about this topic
FESCo
FESCo elections
PackageMaintainers/Policy/FESCoElections,, from="^
Read on for more more details about this topic
All approved Fedora policy documents
If you want more details look at the individual documents that cover the policies in depth:
[[PageList('PackageMaintainers/Policy/')]