All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Documentation issues
Date: Sun, 25 Jun 2017 10:13:37 -0600	[thread overview]
Message-ID: <20170625101337.1ac93e34@lwn.net> (raw)
In-Reply-To: <1779146.rtcHP5MkoH@aspire.rjw.lan>

On Sat, 24 Jun 2017 14:20:40 +0200
"Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:

> At the same time I think it would be good to take that as an opportinity to
> improve the *content* of the documentation files as well, so not just
> convert them, but also make them more up to date etc in the process.

This is certainly an area of ongoing concern.  There has been a fair
amount of energy put into the transition, which is great, but if it comes
down to "make a bunch of crufty old stuff look better with
cross-references to other crufty old stuff", it's not that big a win.

My hope, I guess, is that making the documentation more coherent and
approachable will inspire more people to also work to make it better.

jon

  parent reply	other threads:[~2017-06-25 16:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 18:39 [Ksummit-discuss] [MAINTAINERS SUMMIT] Documentation issues Jonathan Corbet
2017-06-23 23:09 ` Rafael J. Wysocki
2017-06-24 12:03   ` Rafael J. Wysocki
2017-06-24 10:46 ` Mauro Carvalho Chehab
2017-06-24 12:20   ` Rafael J. Wysocki
2017-06-24 13:41     ` Mauro Carvalho Chehab
2017-06-25 20:56       ` Jiri Kosina
2017-06-26  1:20         ` Mauro Carvalho Chehab
2017-06-26 21:18           ` Rafael J. Wysocki
2017-06-26  5:58         ` Takashi Iwai
2017-06-26 21:28           ` Rafael J. Wysocki
2017-06-27  8:41             ` Daniel Vetter
2017-06-27 10:31               ` Mauro Carvalho Chehab
2017-06-26 22:18         ` Jonathan Corbet
2017-06-27 18:42           ` Bird, Timothy
2017-06-28 19:48           ` Geert Uytterhoeven
     [not found]       ` <CAFhKne8ZttmqWYJToCw9EDywzeMdp=eiFpoZ+O5xrzmKnpA09Q@mail.gmail.com>
     [not found]         ` <CAFhKne_W-EbjUd_Cm4kyBHrVK6K9r8Ss3gY0ogO1nztbQZYBEg@mail.gmail.com>
2017-06-25 21:32           ` Matthew Wilcox
2017-06-25 21:42             ` Rafael J. Wysocki
2017-06-26  1:15               ` Mauro Carvalho Chehab
2017-06-26 21:16                 ` Rafael J. Wysocki
2017-06-26  0:58             ` Mauro Carvalho Chehab
2017-06-25 16:13     ` Jonathan Corbet [this message]
2017-06-26 12:19 ` Mark Brown
2017-06-27  8:38   ` Daniel Vetter
2017-06-27 15:33     ` Mark Brown

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=20170625101337.1ac93e34@lwn.net \
    --to=corbet@lwn.net \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=mchehab@s-opensource.com \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.