Most Helpful Customer Reviews
Producing Open Source Software: How to Run a Successful Free Software Project based on 0 ratings. 2 reviews.
Many of the ideas in the book can be used for internal company IT projects as well.
Producing Open Source Software : How to Run a Successful Free Software Project (Paperback) Are you a software developer or manager who is considering starting an open source project, or has started one and is wondering what to do now? Well, you're in luck! Author Karl Fogel, has done an outstanding job of writing a book that will be helpful to people who just want to participate in an open source project, but have never done so before. Fogel, begins with a brief history of free software, and an overview of the open source world today. Next, the author shows you how to get an open source project off on the right foot, including gathering developers, choosing a license, and announcing the project. Then, he takes an in-depth look at the tools a project needs to function smoothly, including communications, version control, and bug tracking software. The author continues by showing you how to set up formal and informal political structures to enable project members to work together and achieve consensus on important issues. In addition, the author next explains the why and how to have a commercial relationship with an open source project. He also provides a guide to productive conduct in project forums, covering both the social and technical aspects of communications. Next, the author shows you how to manage regular releases of open source software, without disrupting the development cycles of the volunteer participants. Then, he helps you understand why volunteer developers do what they do, and how to treat them in such a way that they keep doing it. Finally, he shows you how to evaluate and choose free software licenses, including an in-depth examination of license compatibility issues. The good thing about this excellent book, is that prior experience with open source software, as either a user or developer, is not necessary. Furthermore, the author has made an extra effort to label sections clearly, because of the wide range of user experience.