On 03/02/2012 11:20 AM, "Jóhann B. Guðmundsson" wrote: > 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. 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. Marcela > > 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 ). > > JBG -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
