linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Add a document on how to contribute to the documentation
Date: Thu, 23 Jan 2020 12:03:44 +0200	[thread overview]
Message-ID: <878slyij5r.fsf@intel.com> (raw)
In-Reply-To: <20200122162030.5b789232@lwn.net>

On Wed, 22 Jan 2020, Jonathan Corbet <corbet@lwn.net> wrote:
> This is mostly a collection of thoughts for how people who want to help out
> can make the docs better.  Hopefully the world will respond with a flurry
> of useful patches.

Thanks for writing this!

FWIW,

Acked-by: Jani Nikula <jani.nikula@intel.com>


> +The documentation TODO list
> +---------------------------
> +
> +There is an endless list of tasks that need to be carried out to get our
> +documentation to where it should be.

This reminds me of an old LCA talk of yours where you said,

"If we do this, we end up with, some years from now, this beautiful,
integrated documentation tree, that covers things in a comprehensive
way, where you can find what you want, looks pretty when you look at
it. It's a nice vision, I hear angels singing when I think about it and
so on, it's where I want to go."

Perhaps it would be time to include some concrete overall goals, a
mission statement if you will, somewhere near the top? I mean other than
"top-quality, comprehensive, better". Or "angels singing". ;)

Of course, can absolutely be a follow-up patch on top.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

      parent reply	other threads:[~2020-01-23 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 23:20 [PATCH] Add a document on how to contribute to the documentation Jonathan Corbet
2020-01-22 23:46 ` Randy Dunlap
2020-01-22 23:53 ` Matthew Wilcox
2020-01-22 23:54   ` Randy Dunlap
2020-01-22 23:58     ` Matthew Wilcox
2020-01-22 23:59       ` Randy Dunlap
2020-01-23  0:23   ` Jonathan Corbet
2020-01-23 10:03 ` Jani Nikula [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=878slyij5r.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@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 NNTP newsgroup(s).