Automating the NonResponsiveMaintainers policy

Aleksandar Kurtakov akurtako at
Fri Mar 2 11:52:42 UTC 2012

----- Original Message -----
> From: "J├│hann B. Gu├░mundsson" <johannbg at>
> To: "Development discussions related to Fedora" <devel at>
> Sent: Friday, March 2, 2012 12:20:10 PM
> Subject: Automating the NonResponsiveMaintainers policy
> I am a feature owner for a feature that involves components in the
> hundreds and is heavily depended on maintainers responsiveness.
> For me to start enacting the non responsive maintainers policy is a
> tremendous work thus I'm wondering if there is something preventing
> us
> from automating the non responsive maintainer policy?
> An bugzilla script that acts something like if maintainer has not
> responded to a bug report with the status new in a week ( or some
> other
> time ) the non responsive maintainers policy automatically starts
> taking
> effect.

Well, this is plain nonsense. Do you know how many bug reports do a number of the packagers have ? 
And speaking for "A WEEK" is something that is even offensive. People tend to take 2 weeks of vacation still.

So I would make a contra-proposal. 

If a maintainer doesn't respond to a bug repord with the status new in a week - give commit rights to the reporter in pkgdb so he/she can fix it himself.

I really think this is way more fare and people that tend to think that packagers are just a bunch of lazy guys should step in do some of this dirty work to get an idea what we speak about.


> To get out of that automatic non responsive process the maintainer
> would
> have to comment on the bug and set it's status assigned ( or
> something
> similar ).
> --
> devel mailing list
> devel at

More information about the devel mailing list