public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Vegard Nossum <vegard.nossum@oracle.com>,
	Thorsten Leemhuis <linux@leemhuis.info>
Cc: regressions@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v1] docs: new text on bisecting which also covers bug validation
Date: Sun, 03 Mar 2024 08:35:01 -0700	[thread overview]
Message-ID: <87frx7z5ui.fsf@meer.lwn.net> (raw)
In-Reply-To: <99b7841b-62d4-404e-815b-5eb5cccd2580@oracle.com>

Vegard Nossum <vegard.nossum@oracle.com> writes:

> Something I really like about the current set of books is that they are,
> at least in theory, roughly divided by their target audience
> (user/admin, userspace dev, kernel dev).

That's good, since that was one of my primary goals when I took on the
docs maintainership :)

> I'd worry that "tutorials"
> as a top-level book would unintentionally end up as a very mixed bag of
> documents that don't have a clearly defined target audience.

Could be.  The thing is, there's two axes (at least) that can be used to
describe an audience.  One is who the readers are; that's what we have
been working toward over the years.  The other, though, is the type of
information they want, traditionally divided into tutorials, how-to
guides, explanations, and reference manuals.  Mixing those types (as we
do now) tends to lead to not doing any of them well.

Perhaps the bisection doc is more of a howto, now that I think of it.

Anyway, that is a problem that we're not going to be able to solve for
the 6.9 merge window, but adding this document is.

Thanks,

jon

      parent reply	other threads:[~2024-03-03 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16  8:54 [PATCH v1] docs: new text on bisecting which also covers bug validation Thorsten Leemhuis
2024-02-16 19:41 ` Petr Tesařík
2024-02-17 15:46   ` Thorsten Leemhuis
2024-02-19 22:12     ` Jonathan Corbet
2024-02-20 10:28       ` Thorsten Leemhuis
2024-02-19 22:07 ` Jonathan Corbet
2024-02-20 10:26   ` Thorsten Leemhuis
2024-02-29 21:55   ` Vegard Nossum
2024-03-01  8:45     ` Thorsten Leemhuis
2024-03-03 15:35     ` 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=87frx7z5ui.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=nathan@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=vegard.nossum@oracle.com \
    /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