public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Crutcher Dunnavant <crutcher@datastacks.com>
To: Charles Samuels <charles@kde.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Documentation
Date: Tue, 17 Jul 2001 17:18:43 -0400	[thread overview]
Message-ID: <20010717171843.C21825@mueller.datastacks.com> (raw)
In-Reply-To: <200107172102.OAA19756@altair.dhs.org>
In-Reply-To: <200107172102.OAA19756@altair.dhs.org>; from charles@kde.org on Tue, Jul 17, 2001 at 02:02:05PM -0700

++ 17/07/01 14:02 -0700 - Charles Samuels:
> On 2001-07-17 20:46:24, Ignacio Vazquez-Abrams <ignacio@openservices.net> 
> wrote:
> 
> > This is probably a silly question, but why doesn't your site just use
> > DocBook?
> 
> DocBook is more "bookish" complete with chapters and all.  I've used it 
> before, it's nice, but not for this, in my opinion.  Also, the backend just 
> moves the XML data into a temporary MySQL database for easy searching, and 
> sorting, and something like that, I think, would be much more difficult with 
> docbook.

2 things:

1: there is a project in the kernel to establish API references.
you should not duplicate this work, but should add to it.
Reason: There is no way you can get or stay ahead.

2: the secondary issue of documenting best practices in the
kernel is a different matter altogether. I, myself, have started
a project to do this. I'm sorta scared of letting people know
about it at this point, but I feel it is necessary.

the entry point is:
http://bama.ua.edu/~dunn001/journeyman/

I /am/ looking for help, but it is very early. I am NOT looking
for exposure, so dont even bother looking if you dont want to write
docs; there isnt anything there for you.

-- 
Crutcher        <crutcher@datastacks.com>
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
    R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$

  reply	other threads:[~2001-07-17 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 21:02 Kernel Documentation Charles Samuels
2001-07-17 21:18 ` Crutcher Dunnavant [this message]
2001-07-17 21:25   ` Charles Samuels
2001-07-17 21:31     ` Charles Samuels
2001-07-18  2:19     ` John Levon
2001-07-18  9:06       ` Tim Jansen
2001-07-18 10:18         ` Tim Waugh
2001-07-17 21:28   ` Ignacio Vazquez-Abrams
2001-07-17 21:32   ` Crutcher Dunnavant
2001-07-17 21:28 ` Wichert Akkerman
  -- strict thread matches above, loose matches on Subject: below --
2001-07-17 20:24 Charles Samuels
2001-07-17 20:46 ` Ignacio Vazquez-Abrams

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=20010717171843.C21825@mueller.datastacks.com \
    --to=crutcher@datastacks.com \
    --cc=charles@kde.org \
    --cc=linux-kernel@vger.kernel.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