From: Jonathan Corbet <corbet@lwn.net>
To: Runxi Yu <me@runxiyu.org>, Sasha Levin <sashal@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Runxi Yu <runxiyu@umich.edu>, SeongJae Park <sj@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v2] README: Don't organize the README by arbitrary "roles"
Date: Fri, 15 May 2026 07:52:13 -0600 [thread overview]
Message-ID: <87h5o8srua.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260514000954.32172-1-me@runxiyu.org>
Runxi Yu <me@runxiyu.org> writes:
> From: Runxi Yu <runxiyu@umich.edu>
>
> * Removes the basic introduction to what Linux is. It's reasonable
> assumed knowledge for someone with this repository.
> * Consolidate the IRC, bugzilla, building, and mailing lists from across
> the front and back, to the front only.
> * Remove the "Who Are You?" section that consists solely of role names
> and an one line gloss each.
> * Remove the concept of different contributor "roles" (since there
> really aren't such distinct roles); instead phrase them based on the
> class of action. The "New Kernel Developer" archetype was mostly
> alright, but "Academic Researcher" was essentially a list of
> subsystems that applies for almost any kernel developer. "Security
> Expert" sounded a bit like corporate marketing language, and really,
> developers/admin that don't focus on security could still learn a lot
> from these sections. Backport/maintenance/ sysadmin/maintainer mostly
> stays as is with slight changes in firm; "Hardware Vendor" becomes
> "Driver Development" because as much as we'd like vendors to
> assist/guide/lead driver development, many independent driver
> developers still exist.
I agree with Kees on this. This file, like the rest of the kernel, is
not perfect, but it does convey the message we were going for the last
time it was thrashed. I appreciate efforts to improve the
documentation, but perhaps start a bit smaller as you learn how things
are done?
Thanks,
jon
prev parent reply other threads:[~2026-05-15 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 0:09 [PATCH v2] README: Don't organize the README by arbitrary "roles" Runxi Yu
2026-05-14 1:46 ` Kees Cook
2026-05-14 1:50 ` Runxi Yu
2026-05-14 1:53 ` Kees Cook
2026-05-15 13:52 ` Jonathan Corbet [this message]
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=87h5o8srua.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@runxiyu.org \
--cc=rdunlap@infradead.org \
--cc=runxiyu@umich.edu \
--cc=sashal@kernel.org \
--cc=sj@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