Automating the NonResponsiveMaintainers policy
vondruch at redhat.com
Fri Mar 2 12:08:51 UTC 2012
Dne 2.3.2012 12:52, Aleksandar Kurtakov napsal(a):
> ----- Original Message -----
>> From: "Jóhann B. Guðmundsson"<johannbg at gmail.com>
>> To: "Development discussions related to Fedora"<devel at lists.fedoraproject.org>
>> 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
>> 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
>> time ) the non responsive maintainers policy automatically starts
> 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.
But what if that is one bug who the maintainer don't want touch ATM
although he fixes others? I have my own priorities and as long as there
is no time for some bug, I'm not touching it at all. So one bug is not
enough IMO. There should be some broader amount of activities taken in
More information about the devel