qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bouncing maintainers
Date: Wed, 1 Apr 2015 09:42:36 +0800	[thread overview]
Message-ID: <20150401014236.GG8199@ad.nay.redhat.com> (raw)
In-Reply-To: <87fv8la3kv.fsf@blackfin.pond.sub.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...

      parent reply	other threads:[~2015-04-01  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 14:48 [Qemu-devel] Bouncing maintainers Markus Armbruster
2015-03-25 15:45 ` John Snow
2015-03-26 13:19   ` Kevin Wolf
2015-03-26 21:35     ` John Snow
2015-03-31 10:01       ` Markus Armbruster
2015-03-31 17:03         ` John Snow
2015-04-01  1:42         ` Fam Zheng [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150401014236.GG8199@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).