From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Theodore Tso <tytso@mit.edu>
Cc: "Liam R. Howlett" <liam@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev, Dave Airlie <airlied@gmail.com>
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Mon, 10 Aug 2026 09:08:32 +0100 [thread overview]
Message-ID: <anmD822InwjWKmhy@gremlin> (raw)
In-Reply-To: <ankkb2siES7o86qd@mit.edu>
+cc David as reference below.
On Sun, Aug 09, 2026 at 09:26:53PM -0400, Theodore Tso wrote:
> On Sun, Aug 09, 2026 at 05:56:45PM -0500, Liam R. Howlett wrote:
> >
> > We could have a reserved number of seats dedicated for specific
> > subject that are temporary seats that would be used for a specific
> > topic. As a specific topic expert or interested party, they would
> > be less likely to stay quiet or be disregarded as not knowing the
> > workings of a specific policy.
>
> One of the reasons why we discuss maintainers summit topics in advance
> is partially to create the agenda, but to also be aware who some of
> the interested parties will be. And the program committee *does* take
> that into account.
>
> The other reason why the discussions on the ksummit list are so useful
> is that it *is* a pre-MS discussion. Everyone gets to hear the voices
> who feel strongly about a particular topic --- for example, such as
> the AI/LLM discussion. The voices and ideas that are presented in the
> mailing list is absolutely something that influences the discussion
> that happens in the room.
Your emails are really unclear.
They say this:
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.
(Though I question whether 'most active' is a good metric or one that's
actually being used).
OK cool - as David Airlie says - it's Linus's staff meeting and people he
most interacts with are invited, fine.
But then you say this:
Anybody proposing a topic before July 24th will be added to the list
of potential attendees selected by the program committee; other
potential nominees can be proposed (as a self-nomination or by others)
by sending a note to the ksumimt list saying why that person's
presence would help the discussion.
Which is like a CFP at any other conference implying that topic submission
is tied to attendance.
I think you should make it clear that topic suggestion is entirely separate.
Right now it seems to me to be a bit of a muddle.
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-10 8:08 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) [this message]
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)
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=anmD822InwjWKmhy@gremlin \
--to=ljs@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=liam@infradead.org \
--cc=rostedt@goodmis.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