Producing Open Source Software By Karl Fogel is the most important book in the Open Source Revolution.

On being a successful open source developer, not only does this book cover the technical aspects of Open Source Development but it also covers the most challenging topics like: working with and managing other developers, how to communicate, licensing, and concept of making money even a living writing open source. This view into the life and society of an Open Source Developer is dually qualified to be both lessons for the developer and for everyday life.

Generally, I hate one liners when taken out of context. Read the whole book. With that said, here are a couple good ones:

• "You Are What You Write"
• "At parties, people no longer give me a blank stare when I tell them I write free software."
• "One of the most common mistakes (of open source) is unrealistic expectations about the benefits of open source itself."
• "'It's free as in freedom? think free speech, not free beer.'"
• "Have a Clear Mission Statement"
• "sometimes silence is the best tactic"
• "Hire for the Long Term"
• "Don't Post Without a Purpose"
• "The price of success is heavy in the open source world"
• "Notice what people are interested in"
• "Treat Every User as a Potential Volunteer"
• "Software patents are the lightning rod issue of the moment in free software"

The book clearly identifies what it takes to create, maintain, and, at times, pass the torch on Open Source Projects. It cites a wide range a good sources ranging between the famous hacker, actual open source licenses, and mail-list archives. The actually Version Control Sections are as strong and clear, of course from one of the founders of Subversion, the next version control system. I have many good things to say about this book.

If I had to choose a flaw, I would only criticize there is little on Code Sprints, Parallel Programming or any Micro-Techniques. I believe this is due to the books focus on broader solutions and the entire production. This is not really a flaw, not a bug, yet another feature; so many computer books are unable to step back and show the big picture.

If I did want to comment on the book, there is a handy link to, not a contact from or email address, but to bugzilla. Figures =)

So, Karl should wear his suspenders proud, because this book is top shelve. Now, if we could get him and the Chicago CollaNet gang to stop back in to a ChiPy meeting. Book signing?