From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33202) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YczZz-0001dQ-B3 for qemu-devel@nongnu.org; Tue, 31 Mar 2015 13:03:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YczZw-0006bU-3R for qemu-devel@nongnu.org; Tue, 31 Mar 2015 13:03:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56498) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YczZv-0006bM-RH for qemu-devel@nongnu.org; Tue, 31 Mar 2015 13:03:52 -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 (8.14.4/8.14.4) with ESMTP id t2VH3ns5007937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 31 Mar 2015 13:03:50 -0400 Message-ID: <551AD375.4040905@redhat.com> Date: Tue, 31 Mar 2015 13:03:49 -0400 From: John Snow MIME-Version: 1.0 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> In-Reply-To: <87fv8la3kv.fsf@blackfin.pond.sub.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Bouncing maintainers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: Kevin Wolf , Fam Zheng , qemu-devel@nongnu.org On 03/31/2015 06:01 AM, Markus Armbruster wrote: > John Snow 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. > Good idea. We can add a Maintainers status page that shows how long it's been since it's heard from each maintainer, and sort them in order, and we can check the page here and again. (Or, when patchew is made to be more stable, incorporated into a quarterly status report that it sends out to the list) >> 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...