RE: linux-kernel-documentation, proposal

[Garst R. Reese]

Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Copeland, Matthew" <[e-mail]>

Summarizing...

[snip]
>Possible Tasks:

        1.      Beef up documentation in linux/Documentation making 
        it more clear and verbose. (Plain text) (using possibly
        using Garst's du &> kerneldu as an outline)
        2.      Create an Linux Device Driver manual that can be 
        easily updateable.  (SGML/Docbook)

>Did I miss anything and is anything incorrect?

I would just like to restate that I think it extremely important that we
choose an outline and format. My personal preference would be to use
LyX, but this could be because I find the documentation of DocBook and
sgml-lite so inscrutable :) 
 Most of the details can be sorted out when we have a list, but we will
have a basic dependancy on the code writers to supply the basics, and
our success will depend on them percieving it as a valuable service,
rather than just something else eating away their time.
 Garst