From: Mark Brown <broonie@kernel.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Documentation issues
Date: Tue, 27 Jun 2017 16:33:18 +0100 [thread overview]
Message-ID: <20170627153318.m77j53wfh34mxbwt@sirena.org.uk> (raw)
In-Reply-To: <CAKMK7uHwS0UsJtdOLstg01h3VajtPh_J7pzxQH65+fkJHfhgrQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Tue, Jun 27, 2017 at 10:38:54AM +0200, Daniel Vetter wrote:
> Looking at MAINTAINERS, there's relatively few entries for files under
> Documentation/, and most are for individual files (about 450). None
> are for one of the remaining DocBook files still in 4.12 afaics. I
> think we can fix this problem by making sure that a) docs are sorted
> usefully into directories (e.g. we put all the gpu stuff into
> Documentation/gpu/) and b) there's MAINTAINERS entries for all of them
> (which atm doesn't seem to be the case for a lot of stuff).
Yeah, there's directories there for my subsystems but I have to confess
I'd not checked the broader picture recently.
> But I think the lack of clear maintainer responsibilities for docs was
> something Jon already brough up at the previous KS, and we didn't
> really get anywhere with it.
Is that a case of people actively getting in the way somehow or more a
case that we're not able to generate enough interest for people to
actually work on improving the docs (which is partly about us showing
that we care of course)?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-06-27 15:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 18:39 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
2017-06-26 12:19 ` Mark Brown
2017-06-27 8:38 ` Daniel Vetter
2017-06-27 15:33 ` Mark Brown [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=20170627153318.m77j53wfh34mxbwt@sirena.org.uk \
--to=broonie@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=ksummit-discuss@lists.linux-foundation.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