Revamping the non responsive maintainer process

[Till Maas]

On Fri, Nov 02, 2012 at 06:12:02PM +0000, "Jóhann B. Guðmundsson" wrote:
> On 11/02/2012 06:05 PM, Jon Ciesla wrote:
> >
> >No, they might simply have had nothing to do.  Sometimes
> >applications are stable, have no releases, and have no bugs files
> >against them.
> 
> <sigh>
> 
> Then those individuals would simply respond to the email that that
> was the case and they are still alive and active within the project
> and they might even have to take an step and simply "login" to
> prevent them from being ping next time the cron-job runs .
> 
> Seriously we can just cross that bridge if and when that case
> happens that surely beats doing nothing as things stand now
> 
> Have fun bringing up all the hypothetical issue in the world, I
> however got better things to do with my time than trying to convince
> people that is extremely necessary and deal with any hypothetical
> issue that might arise should we try to automate that process...

The easiest thing to convince people is to propose a concrete proposal
for the time frame and show numbers of how many false positives this
would lead to. Some information about how many packagers were inactive
for how long would be helpful, too. All this information would be easy
to get with the cron job script, which needs to be written anyway.

Regards
Till