Received-SPF: pass (google.com: domain of linux-kernel+bounces-23945-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Thu, 11 Jan 2024 09:40:55 -0800
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?
Message-ID: <20240111094055.3efa6157@kernel.org>
In-Reply-To: <ZZ_JuZd0RJUzIrgY@archie.me>
References: <ZZ_JuZd0RJUzIrgY@archie.me>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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.