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.

Document our expectations and best practices. I'm hoping this doc
will be particularly useful to set expectations with HW vendors.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
v2:
 - use Thorsten's wording for bug fixing requirements
 - put more words into the review/response timeline expectations
v1: https://lore.kernel.org/all/20230713223432.1501133-1-kuba@kernel.org/ (local)

CC: workflows@vger.kernel.org
CC: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: gregkh@linuxfoundation.org
Cc: linux@leemhuis.info
Cc: broonie@kernel.org
Cc: krzk@kernel.org
---
 .../feature-and-driver-maintainers.rst        | 155 ++++++++++++++++++
 Documentation/maintainer/index.rst            |   1 +
 2 files changed, 156 insertions(+)
 create mode 100644 Documentation/maintainer/feature-and-driver-maintainers.rst

<...>

+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.

+1

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>