From: "Theodore Tso" <tytso@mit.edu>
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:42:33 -0400 [thread overview]
Message-ID: <anSpoxZ9SUBvFOZj@mit.edu> (raw)
In-Reply-To: <87y0ekm9nw.fsf@trenco.lwn.net>
On Wed, Aug 05, 2026 at 05:26:11PM -0500, Jonathan Corbet wrote:
> Do we need some sort of more organized onboarding structure and, if so,
> are we able to create and sustain it?
>
> 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.
I wonder if we could make the bot more sophisticated than just sending
a welcome message. If the patch is white-space damaged, or doesn't
apply against upstream (or if there are indications that it was
applied against an LTS branch without an explicit LTS tag or something
indicating that it is a backport), one could imagine having the bot
sending a newer contributor a more specific set of constructive
criticisms.
Some, of this could, perhaps be something that we could add to
Sashiko, with an eye towards giving a more friendly message. Just
today I had to let a new submitter know that they had sent a
white-space damaged patch, and given they were using a gmail.com
e-mail address, it could be possible to send a more useful message.
(Since I was in a hurry, I just pointed them at the Submitting Patches
document, which is rather long. :-)
- Ted
next prev parent reply other threads:[~2026-08-06 15:43 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
2026-08-06 10:10 ` Dan Carpenter
2026-08-06 15:42 ` Theodore Tso [this message]
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=anSpoxZ9SUBvFOZj@mit.edu \
--to=tytso@mit.edu \
--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.