All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Theodore Tso <tytso@mit.edu>,
	Linus Torvalds <torvalds@linux-foundation.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 17:09:18 -0400	[thread overview]
Message-ID: <20260809170918.218792b2@gandalf.local.home> (raw)
In-Reply-To: <87y0efi08u.fsf@trenco.lwn.net>

On Sun, 09 Aug 2026 13:04:33 -0600
Jonathan Corbet <corbet@lwn.net> wrote:

> We could perhaps do better, maybe with a rule that N% of the seats
> should be filled by first-time attendees.  But we do also have to be
> sure that the right people are in the room handle the topics under
> consideration, and that will inevitably include a number of old-timers
> who have been there before.

The thing is, we need people there that are responsible for the actions
decided at the conference. Getting new folks that do not have a stake in
the decisions is not going to be helpful. This is one reason the same
people are there all the time. They are usually the maintainers that may be
most affected by the decisions made.

For instance, last year the session about best practices with linux-next[1],
DRM was brought up as one of the subsystems that did a lot of rebases.
Without Dave Airlie there to explain why he does it the way he does, there
may have been decisions made that could have negatively impacted the DRM
subsytem.

What is the goal of Maintainers Summit? Is it to fix issues that we are
currently having with the process? If so, it is best to get the people
there that are having the issues and those that can help solve them. It
should not be a vanity affair where people can have bragging rights for
attending.

This should not hinder new people from being invited. As the kernel
changes, new people start to have more stake in the kernel. People like
Miguel and I would even argue for Lorenzo ;-)

-- Steve


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

  reply	other threads:[~2026-08-09 21:09 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 [this message]
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-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=20260809170918.218792b2@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=corbet@lwn.net \
    --cc=ksummit@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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.