From: Jakub Kicinski <kuba@kernel.org>
To: corbet@lwn.net
Cc: torvalds@linux-foundation.org, linux-doc@vger.kernel.org,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: [RFC] MAINTAINERS: direct process doc changes to a dedicated ML
Date: Wed, 10 May 2023 19:02:04 -0700 [thread overview]
Message-ID: <20230511020204.910178-1-kuba@kernel.org> (raw)
It's hard to keep track of changes to the process docs.
Subsystem maintainers should probably know what's going on,
to ensure reasonably uniform developer experience across
trees.
We also need a place where process discussions can be held
(i.e. designated mailing list which can be CCed on naturally
arising discussions). I'm using workflows@ in this RFC,
but a new list may be better.
No change to the patch flow intended.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
I've been pondering the lack of cross-maintainer communication
as the kernel grows, and I hope this could help bring us together
a little. Plus twice over the last 2 weeks someone popped up on
netdev with what I personally considered incorrect interpretation
of the process docs, so it'd be nice to CC a list on my replies
so I can be corrected, in case I'm wrong.
Opinions more than welcome!
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1c78e61a3387..58239fbc7007 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6223,6 +6223,12 @@ X: Documentation/power/
X: Documentation/spi/
X: Documentation/userspace-api/media/
+DOCUMENTATION PROCESS
+M: Jonathan Corbet <corbet@lwn.net>
+S: Maintained
+F: Documentation/process/
+L: workflows@vger.kernel.org
+
DOCUMENTATION REPORTING ISSUES
M: Thorsten Leemhuis <linux@leemhuis.info>
L: linux-doc@vger.kernel.org
--
2.40.1
next reply other threads:[~2023-05-11 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 2:02 Jakub Kicinski [this message]
2023-05-16 21:05 ` [RFC] MAINTAINERS: direct process doc changes to a dedicated ML Kees Cook
2023-05-19 15:17 ` Jonathan Corbet
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=20230511020204.910178-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).