Tuesday 21st June, 2011
10:00am to 10:45am
Your open source project is "revolutionary", but no one knows how to install your software and new users are complaining about documentation. What you need is a book, and you need it fast! If your project catches their attention, you'll quickly be approached by one or more publishers.
*What do you do?*
The first half of this talk delves into this particular decision point. Should you publish with a publisher, or should you just write an open source book? We'll explore the advantages and disadvantages of open source books and provide attendees with one model for making such a decision.
The second half of this talk explores the technical infrastructure, tools, and cultural mechanisms that best support an ongoing documentation effort.
Attendees will explore the infrastructure behind two publishing pipelines and explore the various options that are available to a project that has decided to take responsibility for production.
I write and I code. Not always in that order. Allergic to most things, and often kidding. bio from Twitter
Sign in to add slides, notes or videos to this session