From: "Theodore Tso" <tytso@mit.edu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dave Airlie <airlied@gmail.com>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
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: Mon, 10 Aug 2026 11:07:34 -0400 [thread overview]
Message-ID: <annmzHu_s3X6LxOH@mit.edu> (raw)
In-Reply-To: <CAMuHMdWCnGVQeSJiVfWrcBGpcq-Zr_oQGPLNUFhcpxishmT_FQ@mail.gmail.com>
On Mon, Aug 10, 2026 at 09:42:12AM -0500, Geert Uytterhoeven wrote:
> On Sat, 8 Aug 2026 at 01:20, Theodore Tso <tytso@mit.edu> wrote:
> > 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
>
> Forgive my ignorance, how do the sponsored attendees fit into this
> picture?
Sponsored attendees are part of the "pay to play" aspect of how we try
to get sponsorship dollars. There can be up to 5 sponsored attendees,
but I don't think we've ever had more than 2 sponsored attendees;
sometimes a sponsor won't even send an attendee even if their
sponsorship level would entitle them to do so.
In practice, it's rare that a sponsored attendee actually speaks up at
the Maintainers Summit, and for last 3 years, we haven't had any
sponsors, so more recently Linux Foundation, not the sponsors have
been paying the cost.
The "Pay to Play" model for invite-only workshops has worked much
better for LSF/MM, because companies are generally much more willing
to pay $$$ to get in front of the upstream developers to get them to
consider some technical proposal. When we had technical discussions
happening at the Kernel Summit, that was definitely the dynamic. But
most companies are much less interested in trying to inject proposals
into process discussions. Especially in recent years, allocating
dollars to pay for more AI data centers seem to be more important than
many things, not just conference sponsorships. :-)
Cheers,
- Ted
next prev parent reply other threads:[~2026-08-10 15:08 UTC|newest]
Thread overview: 58+ 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-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-10 22:47 ` Mark Brown
2026-08-11 8:12 ` Dup commits in NFC trees [Was: Time to call it quits for the maintainer summit?] Matthieu Baerts
2026-08-11 3:29 ` [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit? Dave Airlie
2026-08-11 7:12 ` Geert Uytterhoeven
2026-08-11 8:16 ` Geert Uytterhoeven
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-10 7:42 ` Geert Uytterhoeven
2026-08-10 15:07 ` Theodore Tso [this message]
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=annmzHu_s3X6LxOH@mit.edu \
--to=tytso@mit.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=airlied@gmail.com \
--cc=geert@linux-m68k.org \
--cc=ksummit@lists.linux.dev \
--cc=ljs@kernel.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.