From: Jeremy Maitin-Shepard <jbms@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: [gentoo-doc] Re: [gentoo-portage-dev] coveted features
Date: Mon, 29 Dec 2003 16:31:05 -0500 [thread overview]
Message-ID: <87d6a7tip2.fsf@jbms.ath.cx> (raw)
In-Reply-To: <20031229192218.GA3152@gentoo.org> (Sven Vermeulen's message of "Mon, 29 Dec 2003 20:22:18 +0100")
Sven Vermeulen <swift@gentoo.org> writes:
> On Mon, Dec 29, 2003 at 06:55:50PM +0100, Bart Lauwers wrote:
> [snip]
>> So let me rephrase that portage docs need to be complete and up to date at
>> all times (at least an english version, devs should know enough english).
>> Linking the documentation to the code is the only way I can see this happen.
> Creating documentation automatically always reduces the readability of the
> documentation. It all depends on who's the intended reader. If it is a
> developer (and *only* a developer) then creating documentation automatically
> might be suggesteable (although not official as there is no QA on it - don't
> dare send me bugreports on automatically created documentation :)
> If it also involves users, then sorry, I don't think this is a good
> idea.
Indeed, in my experience, documentation generated by Doxygen is very
rarely of decent quality. Provided that people are willing to write
documentation from time to time, ``hand-written'' documentation is
generally of higher quality. If you just want a function reference, it
works, but compare the documentation in linux/Documentation to the
garbage you might get if you were to generate Doxygen documentation from
it.
--
Jeremy Maitin-Shepard
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-12-29 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312271631.45947.blauwers@gentoo.org>
2003-12-28 23:02 ` [gentoo-portage-dev] coveted features Daniel Robbins
2003-12-29 17:55 ` Bart Lauwers
2003-12-29 19:22 ` [gentoo-portage-dev] Re: [gentoo-doc] " Sven Vermeulen
2003-12-29 21:31 ` Jeremy Maitin-Shepard [this message]
2003-12-29 23:55 ` Bart Lauwers
2003-12-30 4:45 ` Jeremy Maitin-Shepard
2003-12-30 0:13 ` Bart Lauwers
2004-01-07 21:12 ` Jason Mobarak
[not found] ` <288B2E98-3891-11D8-BB5E-0003938E7E46@gentoo.org>
2003-12-29 18:02 ` Bart Lauwers
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=87d6a7tip2.fsf@jbms.ath.cx \
--to=jbms@gentoo.org \
--cc=gentoo-doc@lists.gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.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