Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 Steven Rostedt <rostedt@goodmis.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	 ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Tue, 11 Aug 2026 09:19:50 +0100	[thread overview]
Message-ID: <anrWlBpyy6fmfCu4@lucifer> (raw)
In-Reply-To: <CAPM=9tybMTBw0iz2BSQ_p+3ybk=SmoLuRgiyyE6BP+=1+2RkfQ@mail.gmail.com>

On Tue, Aug 11, 2026 at 07:30:48AM +1000, Dave Airlie wrote:
> On Mon, 10 Aug 2026 at 17:26, Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:
> >
> > On Mon, Aug 10, 2026 at 08:10:21AM +1000, Dave Airlie wrote:
> > ...
> > > I think people really have a misconception about what goes on at the
> > > maintainer summit, the best explanation I've been given was that it is
> > > Linus's staff meeting. The people that Linus works with closest, get
> > > invited to talk to Linus and help him figure out where the overall
> > > ship is going and where things are going wrong.
> > ...
> > > Your language choice already makes it feel like you see it as some
> > > elite or special group. It's a bunch of technical project managers
> > > talking about the processes of producing the kernel. If a talk about
> > > the technical content of the kernel sneaks in it's very rare and also
> > > usually not of interest to half the room.
> > ...
> > >
> > > > 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.
> >
> > I mean this is kinda my point.
> >
> > It is being advertised as X but is actually Y. So say it's Y.
> >
> > That's not what Ted's posts or the write ups or generally any comms about the MS
> > say it is.
> >
> > The CFP-ish bit is probably pretty redundant too on this basis?
>
> In my opinion, quite a lot of the problems that get raised by the CFP
> on this list, often get resolved on this list, which to my mind
> suggests we just need to have a better year round maintainers list
> that doesn't get consumed by patches or internal subsystem matters.

Yeah that's not a bad idea!

Though threads (especially bikesheddable ones) tend to go one of two ways:

1. Some good constructive discussion comes out of it and decisions are made
   (convergent)

2. The conversation turns into the world's biggest talking shop and I want
   to scoop out my eyes with a rusty teaspoon (divergent)

So probably we'd want a way to cut-to-the-chase and say either 'OK cool
let's do X' or STFU :)

>
> >
> > > >
> > > > However I wonder whether we should look at an alternative approach like
> > > > those with M: entries in MAINTAINERS voting on topics, or something
> > > > similar.
> > >
> > > Voting on what though, I'm already over the number of times
> > > maintainers with small potato problems think that the lives of
> > > maintainers with big potato problems would be much simpler if they
> > > just adopted their niche one-person mutt based review process.
> >
> > Ah good to know core mm is small potatoes ;)
>
> I was more referring to the idea that voting would make any sense in
> that forum, I do believe mm should be well represented, but also you
> have your own very successful forum, and maybe the mm leadership can
> meet at LSFMM and pick 1 or 2 delegates to send to the MS every year,
> and they would get auto accepted, this of course wouldn't stop
> additional mm folks from attending but at least make sure there are
> voices in the room.

Yeah I see that now, sorry I misunderstood, all I saw were the potatoes ;)
I guess being British I default to always seeing subtext...

And yeah, having 100 equal votes for people who maintain
random-driver-just-because-they-happen-to-work-at-company-X vs. 1 for the
burnout-adjacent maintainer of massive-vital-critical-subsystem-Y doesn't
seem fair either.

Your comment re: this being Linus's staff meeting I think is the best
insight on the thread and very much reflects what I felt it was, and what
I've heard from others about it.

So I think we're pretty much violently agreeing at this stage (well other
than the clique-ness but that's fine).

Anyway the TL;DR way to schtop Lorenzo moaning here (TM) is to edit the CFP
mail a bit to separate attendance from topic submission, something like:

https://lore.kernel.org/ksummit/anntucHhrzF_b4sy@lucifer/

That and ideally adding something in Documentation/process to explain what
the MS is and how it works.

Ted's response there was great and goes into oodles of detail, be good to
save that somewhere to help people (including myself of course) understand
it.

>
> Dave.

--
Cheers, Lorenzo

  parent reply	other threads:[~2026-08-11  8:20 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)
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) [this message]
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=anrWlBpyy6fmfCu4@lucifer \
    --to=ljs@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=airlied@gmail.com \
    --cc=ksummit@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /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