Automating the NonResponsiveMaintainers policy

Aleksandar Kurtakov akurtako at redhat.com
Fri Mar 2 17:07:00 UTC 2012



----- Original Message -----
> From: "J├│hann B. Gu├░mundsson" <johannbg at gmail.com>
> To: devel at lists.fedoraproject.org
> Sent: Friday, March 2, 2012 6:56:47 PM
> Subject: Re: Automating the NonResponsiveMaintainers policy
> 
> On 03/02/2012 04:49 PM, Rahul Sundaram wrote:
> > What access do you need?  If you need something to test and you
> > don't
> > have access, run your own instance.
> 
> Here you assume that people have enough hw or vm capable hardware to
> do
> so which is not in my case.
> 
> And this only requires copying the current EOL script and make the
> necessary changes in use so the can be done on technical level if
> consciousness is reached for this.
> 
> Thus if people agree on this I shall put work on getting it done but
> before hand forget it.

Running the NonResponsiveMaintainers automatically based on single bug report is something that shouldn't be even discussed!

If something like this should be discussed it should have a lot different constraints:
* way longer period - (Eclipse.org marks people as not active after 9 months.) - at least 3 months
* not a single bugzilla - at least 3 bugzillas
* no commits in these 3 months
* no builds in these 3 months

And all of these should happen in the very same 3 months period to mark a person as inactive.

Alex


> 
> JBG
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel


More information about the devel mailing list