From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Documentation
Date: Wed, 05 Aug 2015 00:00:59 +0300 [thread overview]
Message-ID: <1891718.ZRACi8n4El@avalon> (raw)
In-Reply-To: <55C102AF.5020006@sonymobile.com>
Hi Tim,
On Tuesday 04 August 2015 11:21:35 Tim Bird wrote:
> On 08/04/2015 07:42 AM, Konstantin Ryabitsev wrote:
> > On Tue, Aug 04, 2015 at 04:50:44PM +0300, Dan Carpenter wrote:
> >> Presumably, someone has a webpage with all the docs pre-built.
> >
> > https://www.kernel.org/doc/htmldocs/
>
> That's good. When this thread started I tried looking for
> an online instance of prebuilt docs, but the latest one I found
> was for 2.6.30.
>
> If this is maintained consistently, maybe this site should be
> (wait for it...) documented somewhere. ;-)
>
> On a more serious note, I'd be in favor of:
> 1) switching to markdown or AsciiDoc. Pandoc markdown
> looks pretty capable, but I wouldn't want to introduce
> a dependency on Haskell. I think for the types of things
> we do, just about any markdown would do. Pandoc claims
> to be able to convert between many different formats,
> including AsciiDoc, and to convert to many different outputs.
>
> I think having plain text will lower the barrier to
> editing the docs.
>
> 2) keeping the intro texts in the source files. That
> way doc changes should be more visible to maintainers,
> and they're arguably more accessible when you're poking
> around the code.
It's more than intro text in my opinion. Look at
https://www.kernel.org/doc/htmldocs/drm/index.html, it tries to be a
guide/walk-through type of documentation. The amount of documentation is so
large that it would be quite impractical to keep it in source files. Or we
could have source files containing only documentation comments, but that would
defeat the point :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-08-04 21:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 14:41 Jonathan Corbet
2015-08-02 7:07 ` Davidlohr Bueso
2015-08-03 13:35 ` Rafael J. Wysocki
2015-08-03 13:27 ` Konstantin Ryabitsev
2015-08-03 14:33 ` Jonathan Corbet
2015-08-03 20:45 ` Dmitry Torokhov
2015-08-04 10:59 ` Daniel Vetter
2015-08-04 0:52 ` Rafael J. Wysocki
2015-08-04 12:50 ` Laurent Pinchart
2015-08-04 13:03 ` Daniel Vetter
2015-08-04 14:28 ` Laurent Pinchart
2015-08-04 14:30 ` Daniel Vetter
2015-08-04 13:50 ` Dan Carpenter
2015-08-04 14:05 ` Geert Uytterhoeven
2015-08-04 14:29 ` Daniel Vetter
2015-08-04 14:30 ` Laurent Pinchart
2015-08-04 17:10 ` Geert Uytterhoeven
2015-08-04 14:42 ` Konstantin Ryabitsev
2015-08-04 18:21 ` Tim Bird
2015-08-04 21:00 ` Laurent Pinchart [this message]
2015-08-04 15:35 ` Mark Brown
2015-08-05 17:07 ` Michael Kerrisk (man-pages)
2015-08-04 17:24 ` Jonathan Corbet
2015-08-04 7:12 ` Michael Ellerman
2015-08-04 7:42 ` Marcel Holtmann
2015-08-04 8:33 ` Peter Huewe
2015-08-05 17:08 ` Michael Kerrisk (man-pages)
2015-08-05 17:19 ` josh
2015-08-05 17:21 ` Konstantin Ryabitsev
2015-08-04 12:54 ` Laurent Pinchart
2015-08-04 13:07 ` Daniel Vetter
2015-08-04 11:09 ` Daniel Vetter
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=1891718.ZRACi8n4El@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ksummit-discuss@lists.linuxfoundation.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