Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	 James Bottomley <James.Bottomley@hansenpartnership.com>,
	ksummit@lists.linux.dev, Theodore Tso <tytso@mit.edu>,
	 Jiri Kosina <jkosina@suse.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Sun, 9 Aug 2026 19:42:21 +0100	[thread overview]
Message-ID: <anjJiuyYisxP79mk@lucifer> (raw)
In-Reply-To: <anii3u-87kSrB9K3@lucifer>

+cc Ted, Sasha, Jiri

(Sorry, hit send before adding cc's...!)

On Sun, Aug 09, 2026 at 07:39:43PM +0100, Lorenzo Stoakes (ARM) wrote:
> On Fri, Aug 07, 2026 at 10:27:27AM -0700, Linus Torvalds wrote:
> > The maintainer summit being a pretty constant "in-group" is
> > fundamental, but it still feels a bit sad and wrong to me.
>
> It feels less like a naturally emerging in-group and more like a clique,
> and I've heard the same view expressed to me by a good few other
> maintainers.
>
> Its exclusivity is pretty well signalled ([0]):
>
> 	"The Linux Kernel Maintainer Summit brings together the world’s
> 	leading core kernel developers to discuss the state of the existing
> 	kernel and plan the next development cycle. This is an invite-only
> 	event."
>
> The procedure for selecting attendees is rather vague ([1]):
>
> 	"Linus has generated a list of people for the program committee to
> 	consider. People who suggest topics that should be discussed at the
> 	Maintainers Summit will also be added to the list for
> 	consideration. ... Late submissions will be considered, but people
> 	submit submissions before September 10th will be considered for
> 	receiving an invite."
>
> Though seemed to change (maybe?) for 2026 ([2]):
>
> 	"The attendees are jointly selected by Linus Torvlads (who has
> 	provided us with a roughly a dozen maintainers that he would like
> 	to attend), and the program committee, who choose from maintainers
> 	and developers who have been the most active in the past year.
> 	... Anybody proposing a topic before July 24th will be added to the
> 	list of potential attendees selected by the program committee ... "
>
> All of this seems to tie topic submission with attendance.
>
> It's a little unclear too whether somebody submitting a topic is also
> proposing to present it at the session or not. It's somewhat implied but it
> doesn't seem to be the case in practice.
>
> For instance, I made a submission last year (I was nagged to by somebody :)
> but I had no expectation of being invited as I did not (nor do not)
> consider myself anywhere near elite or established enough to fulfil the
> criteria above.
>
> I was however slightly disappointed that a session was run on essentially
> the same topic I submitted and whose summary ([3], read out at the start)
> was posted in the same thread.
>
> The session was run by Sasha who hadn't submitted a topic that year (Jiri
> had also made a submission related to LLMs but more specifically about
> kernel patch attribution, though he did attend).
>
> That experience overall made it seem very vague as to how topic selection,
> who runs the session and attendance actually works.
>
> So at the very least some clarity is needed.
>
> Ted's data from elsewhere in this thread is also rather misleading I feel:
>
>   # Summits
>   Attended   #      %
>   ------------------------
>   4          9    18.37%
>   3          8    16.33%
>   2         10    20.41%
>   1         22    44.90%
>
> It's dealing in people but not seats - i.e. actual conference attendances.
>
> Consider:
>
>   # Summits
>   Attended   #      %
>   ------------------------
>   4         27    55.10%
>   1         22    44.90%
>
> It'd _still_ suggest that there was a healthy 44.9% of new faces, even
> though this would mean that 83% of every conference was the exact same
> people :)
>
> What's missing is factoring in the # summits attended.
>
> So by Ted's data there were 102 seats over the 4 years (9 * 4 + 8 * 3 + 10
> * 2 + 22 * 1).
>
> Taking that into account the numbers look very different:
>
>   # Summits
>   Attended   #    Seats occupied   %    Cuml %
>   --------------------------------------------
>   4          9          36       35.3     35.3
>   3          8          24       23.5     58.8
>   2         10          20       19.6     78.4
>   1         22          22       21.6    100.0
>
> That puts the number of seats filled by one-time attendees at any
> conference at 21.6%, not 44.9%.
>
> It means that 78.4% of the seats at any given summit on average are filled
> by repeat attendees, with 58.8% on average filled by people who attended 3
> or 4 conferences.
>
> Which entirely backs up that it is a clique - the same majority in every
> room.
>
> Also, the committee who select attendees (through unclear criteria) are
> themselves drawn from that same core of repeat attendees.
>
> I mean I don't know, maybe it's necessary to run it as a tight ship of
> trusted people, but I think we should at least be more clear about that.
>
> However I wonder whether we should look at an alternative approach like
> those with M: entries in MAINTAINERS voting on topics, or something
> similar.
>
> Not sure if that's a good or terrible idea but it's something :)
>
> --
> Cheers, Lorenzo
>
> [0]:https://events.linuxfoundation.org/linux-kernel-maintainer-summit/
> [1]:https://lore.kernel.org/all/20250805144357.GA762104@mit.edu/
> [2]:https://lore.kernel.org/all/alW3eJ9x6iJ8Juhi@mit.edu/
> [3]:https://lore.kernel.org/all/aTYmE53i3FJ_lJH2@laps/

--
Cheers, Lorenzo

  reply	other threads:[~2026-08-09 18:42 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 15:34 [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit? James Bottomley
2026-08-06 23:41 ` Steven Rostedt
2026-08-07 13:53   ` Rafael J. Wysocki (Intel)
2026-08-07 14:53     ` Steven Rostedt
2026-08-07 16:33     ` James Bottomley
2026-08-07 17:27   ` Linus Torvalds
2026-08-07 19:03     ` James Bottomley
2026-08-07 19:51     ` Steven Rostedt
2026-08-07 20:12       ` Shuah Khan
2026-08-09  1:51     ` Theodore Tso
2026-08-09 18:47       ` Randy Dunlap
2026-08-09 19:04       ` Jonathan Corbet
2026-08-09 21:09         ` Steven Rostedt
2026-08-10  8:14           ` Lorenzo Stoakes (ARM)
2026-08-10 13:20             ` Steven Rostedt
2026-08-10 20:35               ` Liam R. Howlett
2026-08-10 21:05                 ` Steven Rostedt
2026-08-11  0:14                 ` Theodore Tso
2026-08-18 13:09                   ` Liam R. Howlett
2026-08-18 14:02                     ` Theodore Tso
2026-08-18 14:21                       ` David Hildenbrand (Arm)
2026-08-18 15:32                         ` Liam R. Howlett
2026-08-18 17:46                           ` Theodore Tso
2026-08-18 18:18                             ` Lorenzo Stoakes (ARM)
2026-08-18 14:51                   ` Lorenzo Stoakes (ARM)
2026-08-18 14:52                     ` Lorenzo Stoakes (ARM)
2026-08-18 16:45                     ` Theodore Tso
2026-08-18 17:00                       ` James Bottomley
2026-08-18 17:25                       ` Lorenzo Stoakes (ARM)
2026-08-09 21:56         ` Liam R. Howlett
2026-08-10  1:26           ` Theodore Tso
2026-08-10  2:40             ` Liam R. Howlett
2026-08-10  8:08             ` Lorenzo Stoakes (ARM)
2026-08-10 14:56               ` Theodore Tso
2026-08-10 15:49                 ` Lorenzo Stoakes (ARM)
2026-08-09 18:39     ` Lorenzo Stoakes (ARM)
2026-08-09 18:42       ` Lorenzo Stoakes (ARM) [this message]
2026-08-09 22:10       ` Dave Airlie
2026-08-10  7:26         ` Lorenzo Stoakes (ARM)
2026-08-10 13:11           ` Steven Rostedt
2026-08-10 13:32             ` James Bottomley
2026-08-10 14:24               ` Steven Rostedt
2026-08-10 15:23                 ` Mark Brown
2026-08-10 15:52                   ` Randy Dunlap
2026-08-11  3:24                     ` Dave Airlie
2026-08-11  5:29                       ` Randy Dunlap
2026-08-11  6:53                         ` Geert Uytterhoeven
2026-08-11 13:29                       ` Mark Brown
2026-08-10 22:47                   ` Mark Brown
2026-08-11  3:29                   ` Dave Airlie
2026-08-11  7:12                     ` Geert Uytterhoeven
2026-08-11  8:16                       ` Geert Uytterhoeven
2026-08-11 19:54                       ` Rodrigo Vivi
2026-08-11 23:10                         ` Mark Brown
2026-08-12 20:33                           ` Dave Airlie
2026-08-13 11:48                             ` Mark Brown
2026-08-18  9:38                               ` Jani Nikula
2026-08-18 16:50                                 ` Mark Brown
2026-08-19  8:28                                 ` Takashi Iwai
2026-08-19 16:44                                   ` Linus Torvalds
2026-08-11 14:26                     ` Mark Brown
2026-08-12  6:00                     ` Krzysztof Kozlowski
2026-08-12  6:20                       ` Dave Airlie
2026-08-12  7:07                         ` Krzysztof Kozlowski
2026-08-12  7:41                         ` Greg KH
2026-08-12  8:05                           ` Dave Airlie
2026-08-12 12:48                             ` Mark Brown
2026-08-10 21:30           ` Dave Airlie
2026-08-10 21:45             ` Liam R. Howlett
2026-08-11  8:22               ` Lorenzo Stoakes (ARM)
2026-08-11  8:19             ` Lorenzo Stoakes (ARM)
2026-08-11  9:06               ` Jiri Kosina
2026-08-11  9:34                 ` Dave Airlie
2026-08-11 13:47                 ` Steven Rostedt
2026-08-10  7:42         ` Geert Uytterhoeven
2026-08-10 15:07           ` Theodore Tso
2026-08-07 12:58 ` Laurent Pinchart
2026-08-07 13:09   ` James Bottomley
2026-08-07 13:28     ` Laurent Pinchart
2026-08-07 20:15     ` H. Peter Anvin
2026-08-07 19:15 ` Chris Mason
2026-08-07 19:53   ` Steven Rostedt
2026-08-07 23:19 ` Theodore Tso
2026-08-10 13:54   ` James Bottomley
2026-08-10 14:41     ` Steven Rostedt

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=anjJiuyYisxP79mk@lucifer \
    --to=ljs@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jkosina@suse.com \
    --cc=ksummit@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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