public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 0/4] Rewrite the top-level index.rst
Date: Fri, 23 Sep 2022 10:45:41 -0700	[thread overview]
Message-ID: <202209230942.E199E35F@keescook> (raw)
In-Reply-To: <87r102nnef.fsf@meer.lwn.net>

On Fri, Sep 23, 2022 at 09:03:36AM -0600, Jonathan Corbet wrote:
> For better or for worse, our most prominent user-facing documentation is
> the man pages, which are not a part of the kernel repository.  (Hmm...it
> wouldn't hurt to add a link to them to the front page, if and when a
> site with current man pages exists again).

Oh, yes, good idea!

> I don't have that much invested in the current ordering, we can
> certainly change it - anytime we want.  Anybody else have an opinion on
> that topic?

I think you, as the recognized leader of the doc project, can
establish some guiding principles on this, providing a bit of top-down
order. e.g. adopt a specific "Linux kernel documentation project mission
statement / strategy" that takes a distinctly opinionated stand on
anything that has been debated. For example, a strawman, not meant
to block this series in any way:

	Our primary audience is kernel developers, especially new
	contributors. Our next priority is people who want to engage
	with the developer community, but may not strictly be kernel
	developers (e.g. testers, bug reporters, researchers, press,
	etc). Next is users of the kernel, especially for how to use
	various features or configurations.

	Topics are ordered from least complexity to greatest complexity,
	with ties solved alphabetically.

	Links to development conversations must use Lore URLs unless
	they are specifically not available.

	Links to external documentation is strongly encouraged. Any
	dead links will be removed if not updated within 6 months.

	The "htmldocs" build target is expected to build without
	warnings.

It could live in Documentation/doc-guide/contributing.rst, and be the
tie-break for anything that comes up. Obviously, it, too, could change.

> I guess my feelings are that (1) I've had enough promises to help with
> documentation over the years to learn not to count on such until said
> help actually materializes, and (2) demonstrating what we can do can, I
> hope, only inspire people who know more than me to show what we *really*
> can do...

Ship it! "Patches welcome", etc. :)

-- 
Kees Cook

  reply	other threads:[~2022-09-23 17:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 20:41 [PATCH v2 0/4] Rewrite the top-level index.rst Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 1/7] docs: promote the title of process/index.html Jonathan Corbet
2022-09-23 17:53   ` David Vernet
2022-09-23 18:31     ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 2/7] docs: Rewrite the front page Jonathan Corbet
2022-09-23 19:02   ` Randy Dunlap
2022-09-23 19:07     ` Jonathan Corbet
2022-09-24  2:05   ` David Vernet
2022-09-22 20:41 ` [PATCH v2 3/7] docs: reconfigure the HTML left column Jonathan Corbet
2022-09-24  2:13   ` David Vernet
2022-09-22 20:41 ` [PATCH v2 4/7] docs: remove some index.rst cruft Jonathan Corbet
2022-09-24  2:14   ` David Vernet
2022-09-22 20:41 ` [PATCH v2 5/7] docs: move asm-annotations.rst into core-api Jonathan Corbet
2022-09-23  7:45   ` Bagas Sanjaya
2022-09-24  2:10   ` kernel test robot
2022-09-24  2:20   ` David Vernet
2022-09-25  3:54   ` Bagas Sanjaya
2022-09-25 21:29     ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 6/7] docs: Expand the front-page CPU-architecture section Jonathan Corbet
2022-09-24  2:25   ` David Vernet
2022-09-25 21:50     ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book Jonathan Corbet
2022-09-23  4:25   ` Bagas Sanjaya
2022-09-23 13:39     ` Jonathan Corbet
2022-09-25  3:18       ` Bagas Sanjaya
2022-09-25  3:48         ` Randy Dunlap
2022-09-25  3:52           ` Bagas Sanjaya
2022-09-23 18:44   ` Randy Dunlap
2022-09-23 19:06     ` Jonathan Corbet
2022-09-23  8:09 ` [PATCH v2 0/4] Rewrite the top-level index.rst Jani Nikula
2022-09-23  8:55 ` Thorsten Leemhuis
2022-09-23 13:45   ` Jonathan Corbet
2022-09-23 14:43     ` Thorsten Leemhuis
2022-09-23 15:03       ` Jonathan Corbet
2022-09-23 17:45         ` Kees Cook [this message]
2022-09-24  1:56         ` David Vernet
2022-09-23 18:48     ` Randy Dunlap

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=202209230942.E199E35F@keescook \
    --to=keescook@chromium.org \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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