Ideas about allowing Co-maintainer

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Hi,

I have a crazy idea about when/how to allow co-maintainers for
packages and this probably becomes one big flamewar. But here we go:

Some maintainer have packages with lots of bugs but are very
teritorial about the package. Getting them to allow NMUs or offering
them to become co-maintainer just ends in them screaming obsceneties
back (overstated for dramnatic purposes).

I propose that when a package has <X> open bug (or RC bugs) for a
reasonable long time without activity anyone can just declare themself
co-maintainer and do the work.

Alternatively there could be a warning mechanism where one becaomes a
delayed co-maintainer and the real maintainer has <Y> days to get his
package below the <X> open bugs limit. Personally I think it would be
the maintainers own fault to get a co-maintainer without warning for
not fixing the bugs and no warning should be neccessary.

Another option would be to assign some values to bugs depending on age
(and maybe severity) and if the sum goes over <Z> anyone can declare
themself co-maintainer. That way 3 5 year old bugs would be as bad a
50 3 month old ones.


Let the flamewar begin.
        Goswin