Advice On Creating an Open Source Textbook?
Occamboy writes "I wrote a slightly successful (30,000+ copies sold) computer communications textbook a number of years back that was published via the traditional textbook publishing route. The royalties were nice, but, frankly, the bigger money came from the boost in my professional standing (I'm a practicing engineer, not a professor). I also felt bad when the publisher hiked the price dramatically every year because students were stuck once a professor adopted a text — $50 for a smallish paperback seemed very high (although I like to think what they learned was worth it!). I'm thinking of writing another textbook, this time about the practice of software engineering in critical systems, using the experience I've gained in the decades I've spent developing, and managing the development of, software-driven medical devices. Poking around on the Net, I've found several intriguing options for distributing open source texts, such as Flatworld Knowledge, Lulu, and Connexions. This concept of free or inexpensive texts intrigues me — the easy adoption and lack of price-gouging. Do any Slashdotters have experience with this new paradigm? Any suggestions or experiences to share from authors, students, and/or professors, who've written, read, or adopted open source or low-cost texts from any source?"
Have you looked at Wikipedia?
You can try some ideas from books already available in print as well as in electronic versions.
SICP
Stony Brook Algorithm Repository
This site's work seems interesting. http://www.ck12.org/
The royalties were nice, but, frankly, the bigger money came from the boost in my professional standing (I'm a practicing engineer, not a professor).
So I work for a "big router company", and like other companies of similar size it has it's own publishing arm. After writing a number of books which were published either for free on the company's website or via their publishing arm. I decided that I had enough of the Editor's, and self proclaimed techwriters. Now my co-author and I wrote all the material and we handpicked our technical reviewers. We have close ties to the techwriters who author manuals/users guides etc. So finding a reviewer of grammar/style wasn't that hard.
In the end we decided to give away soft copies via download, but if the customer wanted a printed copy then we charged them market value for the book. We decided upon lulu because honestly it was an easy to use interface, they were responsive via email, though I don't believe you can call them up and speak with them. In the end we basically shipped them a .pdf, and then ordered a proof copy to make sure all the graphics/fonts came out as we expected.
We purchased an ISBN from them, and now you can find it on amazon/barnes and noble etc. Our audience is pretty specific, so getting word of our book is pretty easy. No need to pay for marketing, and "big router company" doesn't really help us. Just word of mouth of sales, tech support folks and visiting clients/customers.
I definitely like how I can create multiple versions, review copies etc. I'm sure that there are many other lulu.com type companies.
I would recommend Lulu.