From: Jakub Kicinski <kuba@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, gregkh@linuxfoundation.org,
linux@leemhuis.info, krzk@kernel.org
Subject: Re: [PATCH docs v2] docs: maintainer: document expectations of small time maintainers
Date: Wed, 19 Jul 2023 11:26:46 -0700 [thread overview]
Message-ID: <20230719112646.52977803@kernel.org> (raw)
In-Reply-To: <71224ff9-98d0-4148-afb8-d35b45519c79@sirena.org.uk>
On Tue, 18 Jul 2023 20:55:37 +0100 Mark Brown wrote:
> > +Maintainers must be human, however, it is not acceptable to add a mailing
> > +list or a group email as a maintainer. Trust and understanding are the
> > +foundation of kernel maintenance and one cannot build trust with a mailing
> > +list.
>
> If you're revising this I'd add a note about the L: tag in MAINTAINERS
> here, or possibly just adding a list in addition to humans. It is
> sensible and often helpful for companies to want to get mail copied to a
> wider distribution list internally but they're not really what we mean
> by list since external people typically can't join them.
👍️ Added: "Having a mailing list *in addition* to humans is perfectly
fine."
next prev parent reply other threads:[~2023-07-19 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 15:58 [PATCH docs v2] docs: maintainer: document expectations of small time maintainers Jakub Kicinski
2023-07-18 16:55 ` Andrew Lunn
2023-07-18 17:34 ` Greg KH
2023-07-18 18:06 ` Krzysztof Kozlowski
2023-07-18 19:19 ` Benjamin Poirier
2023-07-18 19:55 ` Mark Brown
2023-07-19 18:26 ` Jakub Kicinski [this message]
2023-07-18 22:02 ` Shannon Nelson
2023-07-19 7:27 ` Leon Romanovsky
2023-07-19 17:54 ` Rob Herring
2023-07-19 18:36 ` Jakub Kicinski
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=20230719112646.52977803@kernel.org \
--to=kuba@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=netdev@vger.kernel.org \
--cc=workflows@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).