Package maintainer policy
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
Normally the maintainer that is listed as primary maintainer in the PackageDB (formerly this was owners.list) of a package is the only one who modifies the package or gives others permission (e.g. by accepting them as co-maintainers) to commit and build changes for that package. Bugzilla is normally the best way to contact the package maintainer or to send him patches and suggestions because it is neutral and trackable; but poking people once or twice in IRC or directly via mail might be a good idea.
But there are certain exceptions where the maintainer has to accept that other packagers will modify his packages. Those exception are described in detail below -- it mostly boils down to this:
- a packager doesn't fix important bugs in time,
- there are problems known that might be bad for the whole Project or a lot of users of the repo/a particular package,
- the changes are quite minor or considered as a general cleanup to a lot of packages, or
- the changes are part of a Fedora Objective, with a specific plan approved by FESCo,
then provenpackagers are allowed to fix stuff in other peoples packages.
What to do if a Maintainer is absent
Special rules for Packages with kernel modules
Fedora Maintenance Lifecycle Policy
What to do with stalled reviews
All approved Fedora policy documents
If you want more details look at the individual documents that cover the policies in depth: