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?"