linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Sreevani Sreejith <ssreevani@meta.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Kernel Documentation Backlog
Date: Thu, 09 Feb 2023 17:04:51 -0700	[thread overview]
Message-ID: <874jruqtb0.fsf@meer.lwn.net> (raw)
In-Reply-To: <758FF6F9-460B-4323-9C1F-80901255B9F0@fb.com>

Sreevani Sreejith <ssreevani@meta.com> writes:

> I am a tech writer interested in improving kernel documentation. Where
> do I find kernel-related documentation to-do list/bugs listed?

I have a general list of useful tasks in
Documentation/doc-guide/contributing.rst, also visible at
https://www.kernel.org/doc/html/latest/doc-guide/contributing.html.

Beyond that, it's a matter of what kinds of work you're looking to do.
Feel free to ask if you have any questions, and I'm looking forward to
your patches.

Thanks,

jon

      reply	other threads:[~2023-02-10  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 18:55 Kernel Documentation Backlog Sreevani Sreejith
2023-02-10  0:04 ` 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=874jruqtb0.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=ssreevani@meta.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;
as well as URLs for NNTP newsgroup(s).