Automating the NonResponsiveMaintainers policy
mmaslano at redhat.com
Fri Mar 2 11:47:27 UTC 2012
On 03/02/2012 12:09 PM, Reindl Harald wrote:
> Am 02.03.2012 12:02, schrieb Marcela Mašláňová:
>> 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.
> define "working"
> it is not too much "work" assign a bug of a owned package
> to give a sign of life not at least to the submitter even
> if we do not speak about any automatism
> if you are working the whole month on a different component
> and give no single feedback to a new reported bug you are
> ending in frustrated submitters - if they get a "assigned"
> they do not feel ignored
> so such automatism does not enforce anything which
> should not be mandatory for a package-owner to not
> get frustrated users no longer submitting bugreports
> because they feel ignored and wasted time do this
Some developers prefer ignore it until they have time. Why should I
write yes, yes, it's broken, I'll look at it next month. That's not
More information about the devel