Features
- Cover Type: Paperback with 302 pages
- Published by: O'Reilly Media, Inc. October 7, 2005
- Written in: English
- ISBN 10 Number: 0596007590
- ISBN 13 Number: 978-0596007591
-
Book Dimensions:
9.1 x 7 x 0.8 inches
- Weighs: 1.1 pounds
Product Description
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.
About The Author
In 1995, Karl Fogel co-founded Cyclic Software, a company offering commercial CVS support. In 1999 he added support for CVS anonymous read-only repository access, inaugurating a new standard for access to development sources in open source projects. That same year, he wrote "Open Source Development With CVS" (published by Coriolis), now in its third edition via Paraglyph Press. Since early 2000, he has worked for CollabNet, Inc, managing the creation and development of Subversion, a version control system written from scratch by CollabNet and a team of open source volunteers, and meant to replace CVS as the de facto standard among open source projects. He also participates in various other open source projects as a section maintainer, patch contributor, and documentation writer.
Reader ReviewsSeems like everyone wants to have a open source project these days. But it's not as easy to run a successful project as you might think. In order to get started on the right foot and increase your chance of success, I would recommend reading Karl Fogel's Producing Open Source Software - How To Run A Successful Free Software Project. Contents: Introduction; Getting Started; Technical Infrastructure; Social and Political Infrastructure; Money; Communications; Packaging, Releasing, and Daily Development; Managing Volunteers; Licenses, Copyrights, and Patents; Free Version Control Systems; Free Bug Trackers; Why Should I Care What Color the Bikeshed Is?; Example Instructions for Reporting Bugs; Index Fogel definitely has the "cred" to write this book. He's spent five years working on the Subversion open source version control system. While not (yet?) the default open source version control system out there, it's rapidly gaining traction. As a result, you figure that Fogel and company must have done a few things right along the way. He does a very nice job in explaining what makes for a successful open source project in terms of tools, structure, and most importantly, culture. He identifies open source projects that have successfully created a culture that encourages participation without dictatorial control. He even addresses how to deal with people issues like monopolizing discussion boards. Those are items that most techies aren't good at, and having a guide like this is priceless. At times the book seems to be rather dense, as in a lot of text with little to break it up. I think it's because there's no real use of graphics or code samples to a large degree. I wouldn't expect it in a book like this, either. But still, it's just one of those things that came to mind as I was reading it. If you have the same nagging feeling and can quickly identify it, then it's easy to deal with the problem. Very valuable information, all condensed into a single volume for easy reference. I'd maintain that anyone looking to start an open source project with hopes of long-term viability would do well to read and digest this book before starting. You'll make fewer false starts and raise your chances of success...
Search for books at
