Re: Ideas about allowing Co-maintainer
Petter Reinholdtsen <pere@hungry.com> writes:
> [Goswin von Brederlow]
> > 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.
>
> An accepted way to help maintainers is to send patches into BTS that
> fixes the reported problem, and tag the bug 'patch'. This way one can
> provide solutions for the maintainer to consider, and save them lots
> of time.
Which obviously DOES NOT WORK.
Just look at all the patches in the BTS that are realy easy to
integrate, are usefull and are still not used by the maintainer.
> I do not seem the need for forcing co-maintainers on maintainers doing
> a bad job until most bugs are ignored even if the bug reports have
> patches fixing the problem included.
>
> Your idea could be considered if there are packages with lots of open
> bugs were patches are included, and the maintainer are just ignoring
> these. Then the package should probably be hijacked or just NMUed.
> As far as I know, there are not many packages like that.
There are quite a lot. Too many.
And even after 3 years without any maintainer uploads and several NMUs
hijacking still wouldn't be allowed. Also hijacking a package when the
maintainer insistes on being active but not showing any signs of work
will proove to be impossible without a lot of screaming or forking the
package.
MfG
Goswin
Reply to: