From: Sasha Levin <sashal@kernel.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Merge tree too flat?
Date: Tue, 4 Jun 2024 18:33:42 -0400 [thread overview]
Message-ID: <Zl-WRpN0-rBVS7F-@sashalap> (raw)
In-Reply-To: <nycvar.YFH.7.76.2406041151590.24940@cbobk.fhfr.pm>
On Wed, Jun 05, 2024 at 12:03:45AM +0200, Jiri Kosina wrote:
>On last year's maintainer summit, there was a session where Linus asked
>the participants to bring up topics / questions [1].
>
>I myself was the one raising the concern of the merge tree feeling a
>little bit too flat, and there seemed to be general agreement on that.
>
>Checking the git repository as of now, it seems like we have not changed
>anything in that respect over the past year, and a lot of things are going
>directly to Linus although they could be cascaded a little bit better,
>contributing to better load-balancing on all maintainer levels (including
>the top-level one, of course).
I'm not sure we should be pushing for a more hierarchial tree. Yes, it's
flat, but is it the issue we're trying to address?
With heirarchy, we're asking folks to layer one on top of the other, but
for most subsystems this doesn't work as well (outside, maybe, drivers
that fall under a single subsystem).
I'd argue that what we want is more co-maintainer groups where several
folks share the burden. This, in turn, makes the tree look flat (all of
"x86" is one maintainer group, for example).
I'd also point to the LWN article you've linked: the flat model isn't
called out as an issue either by Linus or by the rest of the group
(which is what I recall from the discussion). Yes, it's flat, but the
solution isn't to make it a pyramid.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-06-04 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 22:03 Jiri Kosina
2024-06-04 22:21 ` Steven Rostedt
2024-06-04 22:34 ` Jiri Kosina
2024-06-04 22:45 ` Steven Rostedt
2024-06-05 11:31 ` Mark Brown
2024-06-14 9:15 ` Wolfram Sang
2024-06-04 22:33 ` Sasha Levin [this message]
2024-06-04 22:38 ` Jiri Kosina
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=Zl-WRpN0-rBVS7F-@sashalap \
--to=sashal@kernel.org \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
/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