Tackling Open-Source Book Projects?

Wheeler asks: "I am currently writing a book ('The Directory Services Cookbook', shameless self-plug), which I plan to publish under some form of open license, once it's finished. At this point I am really looking for clues on which license would be appropriate for your classic, not-necessary-digital work of creation. And while we're at it: Can other OS book projects share experience on how to tackle the process of writing in general. I personally think a little Linus T. should be in every project doing editing, checking for style and layout, the works. Any comments?"

Comments

basic editing principles

[Em Emalb]

Well,

I don't have much experience in writing OS books, but I would say, start with your basics:

Outline what you plan to do
Get a rough idea of chapters, etc.
get a rough draft
submit it to friends for editing/proofreading, etc.
get it back, "spice" it up some, re-submit for editing.
Have them check this version out and make any additional changes, etc...and submit for our approval ;)

btw, this is all basic stuff, but I wanted to help and this is all I had to offer.

Guess that makes me pathetic :0