Automating the NonResponsiveMaintainers policy

"Jóhann B. Guðmundsson" johannbg at
Fri Mar 2 11:12:56 UTC 2012

On 03/02/2012 11:02 AM, Marcela Mašláňová wrote:
> Ok, so you'll automatically start non-responsive maintainer process,
> because maintainer didn't work on a one bug. But he might be working on
> different component for whole month. He might be working on a new
> upstream release and not paying attention to low priority bugzillas.
> You should take more parameters than one bug to kick someone from Fedora.

This is based on more then one bug against one component and through 
observation in several release cycles.

If an maintainer does not want to be affected by the automatic non 
responsive process all he would have to do would simply be something 
like changing the report status from new to assigned and leave feed back 
on it.


More information about the devel mailing list