From: "Theodore Tso" <tytso@mit.edu>
To: "Liam R. Howlett" <liam@infradead.org>
Cc: 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
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Sun, 9 Aug 2026 21:26:53 -0400 [thread overview]
Message-ID: <ankkb2siES7o86qd@mit.edu> (raw)
In-Reply-To: <006B9A78-D7A3-4684-91C8-BCA700487B65@infradead.org>
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.
> This brings to mind something else which I've been think for some
> time, we should have delegates when someone cannot make it in
> person. Not as a replacement, but as someone that can speak up when
> things are relevant to their particular expertise - and potentially
> to help the succession planning of that subsystem.
As far as succession planning of a subsystem, I'd argue that MS isn't
the best place. For example, at this year's LSF/MM/BPF, the
discussion over succession planning of the mm subsystem took place
there. There was also a discussion about how the FUSE developers
would organize themselves that took place at LSF/MM. Those
discussions would not be of interest to most the attendees of the
Maintainers Summit, since most of those decisions are quite
decentralized, where a networking or BPF maintainer isn't going to be
dictating succession planning of MM subsystem (for example). This is
why other venues, such LSF/MM. KVM Forum, Networking Summit, Plumbers
Miniconfs or BOF's, are probably suitable for those sorts of
discussions.
Cheers,
- Ted
next prev parent reply other threads:[~2026-08-10 1:27 UTC|newest]
Thread overview: 26+ 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-09 21:56 ` Liam R. Howlett
2026-08-10 1:26 ` Theodore Tso [this message]
2026-08-10 2:40 ` Liam R. Howlett
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-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
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=ankkb2siES7o86qd@mit.edu \
--to=tytso@mit.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=liam@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.