From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: MAINTAINERS spring-cleaning
Date: Wed, 05 Nov 2025 07:02:07 +0100 [thread overview]
Message-ID: <87ikfpow4g.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFEAcA9oUfFSFXrN+swbCtr4LV+S+-DuUjdP5miGnSbkCt2ZYA@mail.gmail.com> (Peter Maydell's message of "Tue, 4 Nov 2025 17:36:47 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> I just did some analysis of our MAINTAINERS file with the aid of a
> local copy of the public-inbox archive of qemu-devel, and (unless my
> scripting is broken ;-)) of the 258 emails listed in MAINTAINERS,
> 50 have not sent an email to qemu-devel in the last three years.
>
> Some of that will be things like "the address somebody uses to send
> to the list is not quite the same as the one they have listed", so
> it will need some manual checking, but I think this shows we could
> use a bit of spring-cleaning of the file to remove stale entries.
>
> I propose to send some (not cc'd the list) emails to these people,
> asking (politely!) if they're still interested in being in the
> MAINTAINERS file, and treating "email bounces", "no" and "no reply
> within a month" as "I'm no longer interested in being cc'd on patches".
> Then we can update the file accordingly.
>
> (This was prompted by a series I sent out earlier today getting
> a load of "address unknown" bounce-mails from a corporate server;
> that's not a particularly rare thing to happen IME. And I also
> have developed a habit of manually curating cc lists to drop
> people I suspect of not actually being involved any more...)
Yes, please!
We talked about the issue of stale MAINTAINERS entries before, mostly
when e-mail bounces get sufficiently annoying for somebody to submit or
ask for a MAINTAINERS correction, but as far as I know it always stopped
at talk.
Ignored e-mail is arguably worse than bouncing e-mail. 50 entries out
of 258 is a lot.
If the cleaning you propose works, we should consider repeating it
regularly, to avoid backsliding. Annually?
prev parent reply other threads:[~2025-11-05 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 17:36 MAINTAINERS spring-cleaning Peter Maydell
2025-11-04 17:58 ` Thomas Huth
2025-11-05 6:02 ` Markus Armbruster [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=87ikfpow4g.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.