English Portuguese (Brazil)
Policy for encouraging comaintainers of packages
All packages in Fedora should normally be maintained by a group of maintainers. Having at least two active maintainers for each package in Fedora is encouraged. Big and important packages should have more maintainers -- there is no upper limit.
Reasons for having more than one maintainer are:
One maintainer can commit fixes even when the other maintainers are away.
Maintainers can guide each other, leading to better overall package quality.
If a maintainer stops maintaining their package for whatever reason, co-maintainers can smoothly take over.
Co-maintainership gets new people involved in Fedora.
The burden of experienced maintainers is reduced, so they get a chance to get involved with more complicated and important parts of the project.
There is a primary maintainer who takes care of the package in general. It is their job to approve and find new maintainers and to make sure their efforts get coordinated, especially between Fedora and EPEL.
The maintainers should actively work towards getting at least one co-maintainer.
Who can be a co-maintainer?
Anybody who has been sponsored to the _packager_ group can be a co-maintainer. xref:Package_sponsor_policy.adoc[Package sponsor policy] has special instructions for the case where somebody who has not been sponsored yet wants to become a co-maintainer.
SIGs cannot be primary maintainers, but they can be co-maintainers.
Approving and rejecting co-maintainers
The primary maintainer approves or rejects new co-maintainers. They can also remove co-maintainers if there is a reason to do so.
The primary maintainer cannot block co-maintainers for EPEL only because they do not want to support EPEL. If they do not want to care about their package in EPEL, they have to accept somebody who does.
Assigning bugs
Bugs get assigned to the primary maintainer, who is in charge of the package. It does not mean that they have to do all the work, but they have to make sure the work gets done.