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/
Perhaps the new model could be something like what Cory Doctorow has done, in that textbook authors publish at physical book and, at the same time, release a free digital download of the textbook. That way, professors and students who felt like they needed the full versions could buy it, while those who don't need the printed version and/or can't afford it could simply download it. Of course, there might have to be incentives to buy the physical book, but, in my opinion, they should be limited to what is absolutely necessary to ensure that the publisher and author can actually make money; the free version should still be substantive.
...I suspect many professors still feel a textbook lacks legitimacy unless it's hard cover, thick and there is a substantial price tag connected to it. I say this so as to suggest that "free" might mean it won't be as widely adopted as the authors first one.
Do you want to write a free textbook, manage an open source textbook project or host/start a wiki textbook?
If you want to write a free textbook, go for it. There are several examples you can find, some by pretty big names.
If you want to manage an open source textbook project be warned that if you want a professor to use it you're going to have to assume the role of editor and put up your reputation to vouch for whatever goes into it.
If you want to start a wiki textbook project, there's no shortage of wiki sites, but nobody is going to use it in an official capacity. Just like Wikipedia doesn't fly in academia, wiki texts don't either.
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.
1) The book itself
2) A front / spine/ Back images for the cover.
You upload it to Amazons servers and set a price (Think Amazon charges a fee for inital setup).
Then list it on Amazon and they are printed as required.
Laters Sol "Have you found the secrets of the universe? Asked Zebade "I'm sure I left them here somewhere"
With help from Alex Clarke and Philippe Mougin I wrote a tutorial on programming in Object-C, aimed at absolute newbies. It was released as a PDF and a great success. Over 200k copies were downloaded by people interested in programming for the Apple Macintosh (or perhaps iPhone). You can find it here:
http://www.cocoalab.com/?q=becomeanxcoder
It was translated by volunteers in several other languages, amongst which Chinese and Arabic. Cool!
Bert
Speaking as a professor, I absolutely detest the practice of issuing new editions every year to screw the students. It is (a) never clear what has changed, (b) there is no reason students shouldn't be able pass on their used textbooks if they no longer want them, and (c) if you need translations, they are always a year or so behind, meaning that editions do not match across languages.
So, as a potential customer of textbooks, what is important?
For what it's worth, I would not be a fan of a purely electronic textbook. Electronic resources are great, but having a written reference on the side is still very useful - if only because you may need to see the reference while looking at stuff on your screen.
Enjoy life! This is not a dress rehearsal.