All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Fri, 7 Aug 2026 19:19:57 -0400	[thread overview]
Message-ID: <anZi9nDTNu4WNc3s@mit.edu> (raw)
In-Reply-To: <8ae41b73983eee6ba716a61b8701df6522a02baa.camel@HansenPartnership.com>

On Thu, Aug 06, 2026 at 11:34:09AM -0500, James Bottomley wrote:
> It continued as a 2 day event co-located with
> Ottawa Linux Symposium (still run by USENIX) until 2008 when it mostly
> co-located with Plumbers and was run by the LF.  In 2015 Linus
> complained that he didn't find the KS talks that valuable and he'd like
> to discuss process with a smaller audience, so in 2016 the kernel
> summit was split and the talks went to the kernel summit track in
> Plumbers and a 1 day Maintainer Summit was born.

When the Kernel Summit grew from ~50 people to a bit over 150 people,
it started getting a lot more unwieldy, and it became impossible to
make sure all of the people needed for a particular technical topic
could be issued invites.  The flip side was that when there was that
many people in the room, it was too hard to have focused process
discussions.

So that was the reason why the the split took place; it was getting
too large for process discussions, and it was too small for technical
discussions.

Today, the Maintainer Summit is basically a half-day event, with
around 30 people (plus any sponsored attendees), and is only focused
on process questions, with the technical discussions taking place at
the Plumbers Conference where it is colocated --- the miniconferences,
Refereed and Kernel Summit tracker, and the BOF's.  And I think that's
worked pretty well.

As such, the costs of the Maintainers Summit is actually pretty cheap,
especiallly since there is no A/V, and a room that can hold ~30 people
is not really that big of deal.  So I doubt it is as expensive as what
James has estimated.  If we did want to economize, we could do things
like drop the Kernel Summit dinner and the "sponsor gift".  I can talk
to the Linux Foundation to see what they are willing to fund, but
given some of the process discussions that have taken place such as
"The End of the Rust Experiment"[1], and the discussions around AI
that almost certianly will take place this year, I think the value
Maintainer Summit is one where hopefully the LF would be willing to
support it one way or another.

[1] https://lwn.net/Articles/1049831/


We can split this discussion a couple of different ways.  The first is
how can we make the Maintainers Summit more valuable.  I do think that
in the last couple of years, there *have* been a number of quite
valuable discussions, but it's always worthwhile to consider ways in
which we can improve the discussion.  So that's on the "benefits" side
of the equation.

The second is on the "costs" side of the equation.  There are a couple
of things, such as the dinner and the gift, that we can almost
certainly slim down, if this is becoming too much of a burden to the
LF.

Getting more sponsorship dollars is going to be challenging.
When we had the the technical content in the Kernel Summit as part of
the invite-only portion of the event, companies would pay $$$ because
they wanted to introduce specific technical ideas, to better support
their products because what they were paying for was the attention of
the Kernel Developers.  This "attention economy" dynamic is one of the
things that does still work and drives sponsorship with LSF/MM, by the
way.

						- Ted

      parent reply	other threads:[~2026-08-07 23:20 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
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 [this message]

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=anZi9nDTNu4WNc3s@mit.edu \
    --to=tytso@mit.edu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=ksummit@lists.linux.dev \
    /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.