Automating the NonResponsiveMaintainers policy
vondruch at redhat.com
Fri Mar 2 12:03:44 UTC 2012
Dne 2.3.2012 12:56, "Jóhann B. Guðmundsson" napsal(a):
> On 03/02/2012 11:16 AM, Vít Ondruch wrote:
>> Actually I support such initiative. We have also filled a few bugs
>> against Ruby components which needs some love due to Ruby update and
>> it happens that we have no response. If there would be tool that
>> reports "yes, the maintainer was active in some Fedora project 3 days
>> ago", then it would be meaningful to nag him again, because the BZ
>> was probably somewhere lost/forgotten, but if you see that the
>> maintainer have been non-active for last 6 months, you know that you
>> should probably start "NonResponsiveMaintainer" process.
> Yeah I suspected that I was not alone in this regard since I am just
> dealing with ca 5% of packages in the distribution.
> This could be beneficial in various project processes although I'm not
> familiar with how FPC ensures that FPG is being followed and is
> updated each time changes are made to the guidelines but let's assume
> they are using this workflow.
Are the changes enforced? I don't think so ...
More information about the devel