ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: ksummit@lists.linux.dev
Subject: [MAINTAINERS SUMMIT] Merge tree too flat?
Date: Wed, 5 Jun 2024 00:03:45 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2406041151590.24940@cbobk.fhfr.pm> (raw)

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'd like to propose this as a proper discussion topic slot this year, by 
e.g. looking at:

- the actual numbers and current merge graph

- is this really something that could improve maintainer load (on all 
  levels) and throughput if done properly?

- how could we motivate maintainers to change the process and delegate 
  more into proper hierarchical sub-trees?

- potentially identify particular trees and changes that could be made in
  the merge graph/path to improve the process

[1] https://lwn.net/Articles/952146/

-- 
Jiri Kosina
SUSE Labs


             reply	other threads:[~2024-06-04 22:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 22:03 Jiri Kosina [this message]
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
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=nycvar.YFH.7.76.2406041151590.24940@cbobk.fhfr.pm \
    --to=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