From: Jakub Kicinski <kuba@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: What to do on MIA maintainers?
Date: Thu, 11 Jan 2024 09:40:55 -0800 [thread overview]
Message-ID: <20240111094055.3efa6157@kernel.org> (raw)
In-Reply-To: <ZZ_JuZd0RJUzIrgY@archie.me>
On Thu, 11 Jan 2024 17:58:01 +0700 Bagas Sanjaya wrote:
> Earlier in late last December, I sent a patch removing Karsten Keil
> <isdn@linux-pingi.de> from MAINTAINERS due to inactivity [1], but Greg was
> unsure about that [2]. So I privately tried to reach Karsten (asking for
> confirmation), but until now he is still not responding to my outreach, hence
> IMO he is MIA.
>
> What to do on this situation? Should he be removed from MAINTAINERS?
Well. I'm not sure you should do anything about it.. In an ideal world
with properly set up maintainer structure it should be up to the next
level maintainer to decide when to do the cleanups. Random people
initiating that sort of work can backfire in too many ways. IDK what
a good analogy would be here, but you wouldn't for example come up
to an employee in a store, when you think they aren't doing anything,
and tell them to go stock shelves.
If there are patches on the list that needs reviewing and the person
is not reviewing them, or questions being asked / regressions being
reported and they go unanswered - the upper level maintainer can act.
But trust me, it's impossible for someone who is not an upper
maintainer to judge the situation.
next prev parent reply other threads:[~2024-01-11 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 10:58 What to do on MIA maintainers? Bagas Sanjaya
2024-01-11 17:40 ` Jakub Kicinski [this message]
2024-01-12 14:03 ` Bagas Sanjaya
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=20240111094055.3efa6157@kernel.org \
--to=kuba@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).