From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
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 16:28:52 +0300 [thread overview]
Message-ID: <20260807132852.GM2201016@killaraus.ideasonboard.com> (raw)
In-Reply-To: <8f07d379f3f4c67b2a9a62330e43066d312d42a4.camel@HansenPartnership.com>
On Fri, Aug 07, 2026 at 09:09:05AM -0400, James Bottomley wrote:
> On Fri, 2026-08-07 at 15:58 +0300, Laurent Pinchart wrote:
> > On Thu, Aug 06, 2026 at 11:34:09AM -0400, James Bottomley wrote:
> > > What got me thinking about this is the obvious funding problem: MS
> > > is free to attendees, but only had one sponsor in 2024, none in
> > > 2025 and is on track to have none this year.
> >
> > The sponsorship prospectus ([1]) indicates that the "attendee gift"
> > category is sold out, does it mean one sponsor signed up ?
>
> The LF paid for the attendee gift last year. Since they have to be
> ordered some way ahead of the conference I'd guess the same is true
> this year.
>
> [...]
>
> > The maintainer summit is limited to 30 guests, plus up to 7 sponsored
> > attendee according to [1]. Assuming neither Linus nor the program
> > committee are counted as guests, that would be 43 people in total, so
> > a rough cost of $2500 per person for one day.
>
> I take it you've never seen the bill for attending a USENIX (or a lot
> of other) one day events.
USENIX, no. That was unfortunately before my days.
> > I understand that hosting events in large venues is expensive, but if
> > the maintainer summit is an invite-only, separate event, would it be
> > an option to drastically cut costs by hosting it in a nearby but
> > separate location ?
>
> Is there any point wittering about your speculated numbers vs mine?
> The bottom line is there is a cost and someone has to pay it if there
> are no sponsors.
Please don't speculate that I'm speculating. I've organized multiple
one-day events for crowds between 15 and 25 people, at costs of around
100€ per attendee for a meeting room and lunch. I know it doesn't scale
linearly, and I'm sure we don't want to organize the maintainers summit
at the lowest possible cost, but there's quite a gap.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-08-07 13:28 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 [this message]
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=20260807132852.GM2201016@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox