From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54242)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1Yd7oX-00064P-SA
	for qemu-devel@nongnu.org; Tue, 31 Mar 2015 21:51:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1Yd7oS-0001Jv-TX
	for qemu-devel@nongnu.org; Tue, 31 Mar 2015 21:51:29 -0400
Received: from mx1.redhat.com ([209.132.183.28]:48818)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1Yd7fz-00069u-Ht
	for qemu-devel@nongnu.org; Tue, 31 Mar 2015 21:42:39 -0400
Received: from int-mx11.intmail.prod.int.phx2.redhat.com
	(int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])
	by mx1.redhat.com (Postfix) with ESMTPS id F0FD0AECBA
	for <qemu-devel@nongnu.org>; Wed,  1 Apr 2015 01:42:38 +0000 (UTC)
Date: Wed, 1 Apr 2015 09:42:36 +0800
From: Fam Zheng <famz@redhat.com>
Message-ID: <20150401014236.GG8199@ad.nay.redhat.com>
References: <87h9t9i15j.fsf@blackfin.pond.sub.org>
	<5512D81D.5000309@redhat.com>
	<20150326131905.GB3932@noname.redhat.com>
	<55147BA9.3070309@redhat.com>
	<87fv8la3kv.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87fv8la3kv.fsf@blackfin.pond.sub.org>
Subject: Re: [Qemu-devel] Bouncing maintainers
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org

On Tue, 03/31 12:01, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
> 
> > On 03/26/2015 09:19 AM, Kevin Wolf wrote:
> >> Am 25.03.2015 um 16:45 hat John Snow geschrieben:
> >>>
> >>>
> >>> On 03/25/2015 10:48 AM, Markus Armbruster wrote:
> >>>> I just had another cc: to an address gotten from MAINTAINERS bounce with
> >>>> "user unknown".
> >>>>
> >>>> How do we weed out dead MAINTAINERS entries?
> >>>>
> >>>
> >>> Automated spambot that runs once a release cycle and reports back to
> >>> the list which entries were dead?
> >>
> >> I don't need more email. Why can't we just send a patch to MAINTAINERS
> >> dropping the line the first time someone actually notices it?
> >>
> >> Kevin
> >>
> >
> > Could make a bot that just watches from: addresses on the list. If it
> > sees a mail from you within the last release cycle, it assumes you are
> > still alive.
> 
> Is this something patchew could do for us?  It already watches list
> traffic.

Yes.

Patchew can be added a page to list active addresses by release cycles. By
comparing against MAINTAINERS file we know who are inactive.

Fam

> 
> > If it doesn't hear from you for an entire release cycle, it sends out
> > a small ping and looks for bounces.
> 
> I'm not sure I'd bother with the ping.  Post the list of absentee
> maintainers, and let humans take it from there.
> 
> > Only once a release would be not more than four times a year, and most
> > active maintainers would never see a single email.
> >
> > Or, yes, manually when it happens...