[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71224ff9-98d0-4148-afb8-d35b45519c79@sirena.org.uk>
Date: Tue, 18 Jul 2023 20:55:37 +0100
From: Mark Brown <broonie@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: corbet@....net, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, gregkh@...uxfoundation.org,
linux@...mhuis.info, krzk@...nel.org
Subject: Re: [PATCH docs v2] docs: maintainer: document expectations of small
time maintainers
On Tue, Jul 18, 2023 at 08:58:14AM -0700, Jakub Kicinski wrote:
> We appear to have a gap in our process docs. We go into detail
> on how to contribute code to the kernel, and how to be a subsystem
> maintainer. I can't find any docs directed towards the thousands
> of small scale maintainers, like folks maintaining a single driver
> or a single network protocol.
I'm not super comfortable with all of the musts here but this is
probably fine so
Reviewed-by: Mark Brown <broonie@...nel.org>
One note:
> +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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists