Re: [PATCH] RFC: add MAINTAINERS file

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 2, 2024, 17:00 UTC
Message-ID: <xmqqzfub66oq.fsf@gitster.g>
In-Reply-To: <ZgutC_ddW_Psmlcl@tanuki>

Patrick Steinhardt <ps@pks.im> writes:

Show 9 quoted lines

> On Wed, Mar 27, 2024 at 06:29:13AM -0700, Junio C Hamano wrote:
>> The development community has been fairly loosely organized so far,
>> but I'd like to see responsibility and authority spread a bit more
>> widely yet still not too thinly to compromise the project integrity.
>
> I guess the main motivation of this statement is to reduce your load in
> particular, right? If so, do you have any particular pain points that
> can be spread across the community that would help you? Or is it really
> only spreading the review load by relying more on subsystem-maintainers?

It is not for load reduction, per-se.

I wish people spent more time and effort on reviewing and helping others to polish topics as much as writing their own topic. We see corporate sponsored entities propose a feature, polish it with reviewers, and then after the topic lands and collect their perf scores, leave it bitrot, making it "the community's problem" to maintain it. They may even have to leave the project due to reorg.

Somebody comes with a patch in such an area, and receives no response. The only two ways I see to reduce such "abandoned parts" of the system are:

 * Those who are still with the project but their interest moved to
   other areas in the project to come back to help in the area they
   were involved in, and

 * Those who haven't been involved in an area to grow expertise in
   it.

The latter is far more sustainable than the former. People forget and become no longer more expert than others who have fresh interst in the same area. But for that to happen, we first need to know where the gaps of expertise coverage are. If we try to spread responsibility and authority, we will quickly identify these areas as we find no experts in these areas.