Re: Automating the NonResponsiveMaintainers policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux