Slashdot Mirror

← Back to Stories (view on slashdot.org)

Tackling Open-Source Book Projects?

Posted by Cliff on from the taking-a-book-by-its-horns dept.

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

3 of 135 comments (clear)

  1. Here's your license by Anonymous Coward · · Score: 2, Funny

    What you are reading is your book.

    You may share this book with anyone, provided the following:

    1) You must provide a full copy of the book, including this license to each person you are sharing this book with.

    2) If you make changes to this book, you may not remove this license.

    That wasn't so hard, was it?

  2. Re:What's wrong with the GNU Documentation License by Anonymous Coward · · Score: 1, Funny

    What's wrong with the GNU Documentation License?

    The FSF.

  3. opensource everything by timecop · · Score: 0, Funny

    that's the key to world domination
    thats why microsoft invented shared source license