From: Jonathan Corbet <corbet@lwn.net>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [CORE-TOPIC] Documentation
Date: Mon, 13 Jul 2015 20:36:47 -0600 [thread overview]
Message-ID: <20150713203647.1fdb8bb4@lwn.net> (raw)
In-Reply-To: <201507132146.47186.PeterHuewe@gmx.de>
On Mon, 13 Jul 2015 21:46:46 +0200
Peter Hüwe <PeterHuewe@gmx.de> wrote:
> > kerneldoc does work, after a fashion. It works well enough that people
> > use it, and I hear about it quickly when somebody's comment change breaks
> > the docs build. I don't think we can remove it in the absence of
> > something better.
> Jonathan, do you keep an up-to-date copy of the generated files somewhere?
> (I cannot get it to work out of the box on my machine)
I don't, sorry. That would probably be a good thing for me to do for a
number of reasons.
> > Creating "something better" is actually on my list of things to do. The
> > only problem is that I've had to buy a second 4TB drive to hold that list,
> > so I don't know when I'll have time to think about it.
> Where do you think are the major issues from your point of view?
Well, as mentioned before, kerneldoc is fragile. A little while back
somebody changed a struct to a union without updating the comments to
match; that was enough to break the entire document build process. That
kind of thing happens a lot; I don't think it should have to be that way.
Beyond that, DocBook is a major pain. I get a fair number of patches
along the lines of "that </para> should really have been ahead of that
</whatever>". It's verbose, intimidating to newcomers, and causes more
worn-out shift keys than anything else. We don't need something with the
complexity of DocBook; something closer to Markdown or ReST would do us
just fine and make the documentation much more accessible.
But making any such change is a big job, and convincing the community to
go with a change in tooling is probably a bigger job. So I'm not rushing
into it.
> Would doxygen be "something better"? The kernel-doc style looks already quite
> similar.
> Maybe the kernel should not reinvent everything :)
Doxygen may be worth a look. I'm personally fond of Sphinx, though I
still haven't done a big project in it.
But this is all just dreaming until somebody has the time to do a major
docs overhaul and sell it to everybody else. Until then, I'm focused on
slowly improving what we have now...
jon
next prev parent reply other threads:[~2015-07-14 2:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 22:38 Peter Hüwe
2015-07-12 23:15 ` Julia Lawall
2015-07-14 11:59 ` Mauro Carvalho Chehab
2015-07-13 9:47 ` Alexey Dobriyan
2015-07-13 16:01 ` Randy Dunlap
2015-07-13 16:37 ` Steven Rostedt
2015-07-13 16:46 ` David Woodhouse
2015-07-13 17:35 ` Steven Rostedt
2015-07-13 19:22 ` Peter Hüwe
2015-07-13 19:28 ` Peter Hüwe
2015-07-13 17:42 ` Jason Cooper
2015-07-13 18:11 ` Steven Rostedt
2015-07-14 3:56 ` Zefan Li
2015-07-13 19:25 ` Peter Hüwe
2015-07-13 22:10 ` Laurent Pinchart
2015-07-13 17:45 ` Jonathan Corbet
2015-07-13 19:46 ` Peter Hüwe
2015-07-14 2:36 ` Jonathan Corbet [this message]
2015-07-14 8:40 ` Laurent Pinchart
2015-07-14 11:19 ` Daniel Vetter
2015-07-14 12:43 ` Mauro Carvalho Chehab
2015-07-14 12:53 ` Jonathan Corbet
2015-07-14 13:57 ` Laurent Pinchart
2015-07-14 6:44 ` Johannes Berg
2015-07-13 19:20 ` Peter Hüwe
2015-07-13 23:01 ` Laurent Pinchart
2015-07-13 17:05 ` Lai Jiangshan
2015-07-13 17:42 ` Jonathan Corbet
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=20150713203647.1fdb8bb4@lwn.net \
--to=corbet@lwn.net \
--cc=PeterHuewe@gmx.de \
--cc=dan.carpenter@oracle.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