From: Matthieu Baerts <matttbe@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Coping with the new-developer flood
Date: Thu, 6 Aug 2026 11:24:09 +0200 [thread overview]
Message-ID: <cf1691f4-9fe9-4635-b758-eb3f3914ff62@kernel.org> (raw)
In-Reply-To: <87y0ekm9nw.fsf@trenco.lwn.net>
Hi Jon,
On 06/08/2026 01:26, Jonathan Corbet wrote:
> Do we need some sort of more organized onboarding structure and, if so,
> are we able to create and sustain it?
Good idea to find solutions to reduce the training load on maintainers!
> At a minimum, one could imagine a bot that notices a patch posted by
> somebody who has not been seen before and responds with a "Welcome!
> Here's how we do things here" email.
FYI, that's what the Netdev maintainers are already doing to cope with
the high load:
https://github.com/linux-netdev/nipa/blob/main/ml-agent/form-letters/welcome
This part should be re-usable to work on other trees, monitoring other
mailing lists (public-inboxes to be precise). But I guess it would be
easier to have something global, instead of asking each subtree
maintainer to set all that up.
> In a better-funded world, we could
So many things we could do in this world :)
(BTW, that's a shame there is no "kernel foundation" within the Linux
Foundation, where the TAB could quickly allocate budgets to improve
various things, helping maintainers in different areas like tooling, CI,
funding, local AI, documentation, regression, etc. But that's another
subject :) )
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-08-06 9:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 23:26 [MAINTAINERS SUMMIT] Coping with the new-developer flood Jonathan Corbet
2026-08-06 9:24 ` Matthieu Baerts [this message]
2026-08-06 10:10 ` Dan Carpenter
2026-08-06 15:42 ` Theodore Tso
2026-08-06 15:57 ` Greg KH
2026-08-06 17:28 ` Konstantin Ryabitsev
2026-08-06 18:56 ` Shuah Khan
2026-08-06 19:32 ` Dan Carpenter
2026-08-06 21:14 ` Mark Brown
2026-08-07 3:23 ` Theodore Tso
2026-08-07 9:20 ` Matthieu Baerts
2026-08-07 11:56 ` Laurent Pinchart
2026-08-07 12:28 ` James Bottomley
2026-08-07 12:40 ` Laurent Pinchart
2026-08-07 12:47 ` Arnaldo Carvalho de Melo
2026-08-07 13:36 ` Laurent Pinchart
2026-08-07 13:56 ` Rafael J. Wysocki (Intel)
2026-08-07 16:38 ` Miguel Ojeda
2026-08-07 12:51 ` James Bottomley
2026-08-07 13:34 ` Laurent Pinchart
2026-08-07 13:42 ` Mark Brown
2026-08-07 13:02 ` Mimi Zohar
2026-08-07 13:12 ` Dan Carpenter
2026-08-07 16:37 ` Miguel Ojeda
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=cf1691f4-9fe9-4635-b758-eb3f3914ff62@kernel.org \
--to=matttbe@kernel.org \
--cc=corbet@lwn.net \
--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.