Differences between revisions 7 and 8
Revision 7 as of 2005-01-10 19:20:15
Size: 1219
Editor: anonymous
Comment:
Revision 8 as of 2005-01-10 19:28:36
Size: 1291
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * Reduced tendency for lone maintainer to degenerate into a slumlord.  * Reduce the tendency for bit-rot in packages with only one maintainer.
Line 21: Line 21:
 * none ;)  * Can create problems if changes are not coordinated between the co-maintainers.

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 found for those packages.

Last time I saw the figure quoted there were almost one thousand maintainers in Debian. It should be possible to find at least two for any package that is worthwhile including in Debian.

Pros:

  • A maintainer doesn't have to worry about their packages when they are travelling.
  • Allows little excuse for RC bugs.
  • Should reduce the need for ["NMUs"].
  • Promotes teamwork.
  • Reduce the tendency for bit-rot in packages with only one maintainer.

Cons:

  • Can create problems if changes are not coordinated between the co-maintainers.

This proposal was originated by MikeFedyk.

Back to ReleaseProposals.