From: Shuah Khan <skhan@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Fri, 7 Aug 2026 14:12:53 -0600 [thread overview]
Message-ID: <457e6344-aae2-473c-9bec-bcdbe8aeb606@linuxfoundation.org> (raw)
In-Reply-To: <20260807155120.7142e78b@gandalf.local.home>
On 8/7/26 13:51, Steven Rostedt wrote:
> On Fri, 7 Aug 2026 10:27:27 -0700
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>> The maintainer summit being a pretty constant "in-group" is
>> fundamental, but it still feels a bit sad and wrong to me.
The current format for MS is definitely more focused and easier
to discuss maintainership process and issues.
The larger format we had prior to the current one had some benefits
as it allowed wider participation compared to the current. I definitely
benefited from listening in on these discussions to get a feel for how
the community makes technical and process decisions when we had the
larger format.
MS PC continues to invite new developers though fewer probably compared
to the old format.
Maybe we could look into bringing that aspect back by making some
discussions wider and make that part of the kernel summit track.
It would become more important as the top maintainers reduce their
engagement overtime.
thanks,
-- Shuah
next prev parent reply other threads:[~2026-08-07 20:12 UTC|newest]
Thread overview: 17+ 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 [this message]
2026-08-09 1:51 ` 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
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=457e6344-aae2-473c-9bec-bcdbe8aeb606@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.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 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.