The corporate market is now embracing free, "open source" software like never before, as evidenced by the recent success of the technologies underlying LAMP (Linux, Apache, MySQL, and PHP). Each is the result of a publicly collaborative process among numerous developers who volunteer their time and energy to create better software.

The truth is, however, that the overwhelming majority of free software projects fail. To help you beat the odds, O'Reilly has put together Producing Open Source Software, a guide that recommends tried and true steps to help free software developers work together toward a common goal. Not just for developers who are considering starting their own free software project, this book will also help those who want to participate in the process at any level.

The book tackles this very complex topic by distilling it down into easily understandable parts. Starting with the basics of project management, it details specific tools used in free software projects, including version control, IRC, bug tracking, and Wikis. Author Karl Fogel, known for his work on CVS and Subversion, offers practical advice on how to set up and use a range of tools in combination with open mailing lists and archives. He also provides several chapters on the essentials of recruiting and motivating developers, as well as how to gain much-needed publicity for your project.

While managing a team of enthusiastic developers -- most of whom you've never even met -- can be challenging, it can also be fun. Producing Open Source Software takes this into account, too, as it speaks of the sheer pleasure to be had from working with a motivated team of free software developers.

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 15 Ratings

A developer's perspective that works for both developers and managers - 2009-03-25
Reviewer Rating:
Karl Fogel has the right credentials for the subject of producing open source software. His technical background and entrepreneurial experience help provide informed insight about the very real trade-offs that every developer must face in order to write the best code, appeal to the most users/customers, keep a project on track, and build enough credibility and capital to be able to do it again better the next time.

I would rate this book a *must read* for open source project leaders and product/project managers who have a substantial interest in succeeding with open source software. I would rate this book a *good to read* for developers who want to better understand what their project managers and leaders are trying to manage.

One of the best aspects of this book is the fact that it was developed and published by folks who really understand open source software, and who will, when the time is right, issue a revised and updated edition when sufficient constructive feedback/learning experiences have been received. This continuous community relationship is why this book is a *must read* for managers: it is the best of its class, and even if you disagree with some aspect of it, you can hash that out in public and expect your criticism to be dealt with in future editions. If you don't read it, you can't criticize it, and it won't be better for you the next time around.

Excellent logistical guide for any software project - 2008-06-03
Reviewer Rating:
Issues specific to Open Source are well-covered in this book. I found the section titled "Handling Difficult People" especially useful; his advice in this dodgy area is to act eloquent and keep feedback directed at the problem, not the person. If the person *is* the problem, nip in-public issues in the bud and contact the person directly to resolve the personal issue(s).

Fogel presents lots of down and dirty day-to-day details on how to create excellent software. Not just Open Source, either... the transparency built into the processes he describes are also useful within a company firewall.

Fogel places a huge emphasis on development by random unsalaried people, but I feel that most important and rapid development is due to corporate sponsorship.

Overall: excellent. Read it cover to cover, refer back to it often.

Step-by-Step for a Open-Source Project Manager - 2008-01-13
Reviewer Rating:
If you are thinking of starting/managing a project in an "open-source" model, this is the book you MUST read.

The book is very well written and goes over lessons learned of others that created their own open-source projects. Believe me... every step so you don't have to guess anything!

How to start, how to document, where to deploy the project, what people to invite, whether or not coding standards are necessary, democracy versus dictatorship, all of these questions are answered inside.

A friend of mine has told me that much of the information in this book can be seen for free in video in Google. It's worth looking for.

I read the book in 5 hours and i think my time was very well invested. I now believe that this model is not only suitable for small projects but to larger projects. The complexity of the system will not the an issue if you apply the rules in the book. I still have to try it though... ;-)

Good! - 2009-02-06
Reviewer Rating:
This book is really good for those who want to make their projects open source, or just want to know how to deal with their already done project. There are a lot of advices, examples, practical stuff, etc.
But if you already now a lot about open source, this book will teach you new things. But still good for reading and learn deep things about management.

In my case, five stars is an understatement - 2007-07-26
Reviewer Rating:
Just yesterday I was talking to a friend about this book and we discovered each other very glad with it. First of all, the author has a lot of experience with the theme in question. Furthermore, Karl Fogel is very compelling with words. He knows how to write down his experience in a way that is pleasant, certainly due to a lot of writes he had made through plenties of open source projects.

With this book you will be in touch with topics like the needed infra-structure to setup open source projects, the dinamics of the open source community, strategies for packaging and releasing software, common issues that arise in open source daily development and how to workaround then, a brief about licenses (with properly links for more information on this topic); just to highlight some aspects.

This book was the first hand someone land me into the open source world. It's helping me in three ways: to extract more from open source softwares that already exist, to start my own open source project, and to look at software development through a new, different, and till now better perspective.

Hope this review helps you!

Browse Similar Topics

Top Level Categories:
Business
Software Engineering

Sub-Categories:
Business > Project Management
Software Engineering > Management
Software Engineering > Open Source Development