Slashdot Mirror
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?"
Bruce Eckel publishes books (like "Thinking in Java") as both a free online book, yet sells the printed copy. What he does is publishes the book like normal, but also makes them available for free on his webpage. So if you ever need it to reference, you can jump online to read it. And to support him, most people buy a copy of his book. Its the best of both worlds.
Another nice advantage is he has books that he isn't finished with available online ("Thinking in Patterns" is one of his), where people can read it and give him feedback before he takes it to the press... Check grammar, find things that are easier to reword, play around with his example code, etc... Its almost like an open source project right there. And he makes money on his books (cause, any java coder that has read "Thinking in Java" owns a copy. Its like a Bible for Java).
This may be a technique you may consider...
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
My technology skills are too soft to contribute as a developer to an open-source project, but I'm an experienced editor who'd love to have the opportunity to copy edit for a project or two.
I wouldn't know where to start to find a match for my time and skills. Are there resources that list projects like the one above looking for editorial assistance? If not, should there be one?