Make a policy requirement that:
- At least two ["DDs"] must be willing to maintain a package before it is accepted into the archive.
- If there are not at least two developers interested in the package, it should be removed from the archive (to be enforced at a certain date in the future).
- Sponsoring a package counts as a form of co-maintainership also during the NM process.
- If the group of developers for a package is not able to check up on a package (follow up in the BTS, etc) for a few weeks or months (set your favorite acceptable period of time), another co-maintainer should be requested for those packages.
Last time I saw it quoted, there were almost one thousand maintainers in Debian. A developer shouldn't have to worry about their packages while they are away at a conference or on a trip or vacation.
I expect that this will allow little excuse for RC bugs, objections about ["NMUs"], etc., since there is already a group of maintainers per package that should be able to handle those issues quickly. If not, a RFM (Request for Maintainer) should be sent out to request someone with the required skills and interest.
I suspect that once the doors are open to mass co-maintainership, the need for ["RFMs"] will be infrequent. --MikeFedyk
Back to ReleaseProposals