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.
Producing Open Source Software
und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
| ||||||||||||||||||
Kurzbeschreibung
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Synopsis
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.
Über den Autor
Karl Fogel co-founded Cyclic Software in 1995, 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. He has also written Producing Open Source Software, due to release in October 2005, from O'Reilly Media. 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 module maintainer, patch contributor, and documentation writer.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
4.4 von 5 Sternen
19 Rezensionen
21 von 22 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Great for getting off on the right foot...
9. November 2005
Von Thomas Duff
- Veröffentlicht auf Amazon.com
Format:Taschenbuch
Seems 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...
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...
11 von 11 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Excellent guide for anyone interested in contributing to or running an open source project
4. November 2005
Von Andrew Stellman
- Veröffentlicht auf Amazon.com
Format:Taschenbuch
Karl Fogel does a fantastic job of covering everything you need to know about open source projects. It contains everything you need to know about contributing to an open source projects: how to interact with other contributors, working with version control, contributing code, etc. He also provides an excellent guide for running an open source project. The book covers a great deal of ground, giving excellent advice on a wide range of topics: selecting a license; maintaining a mailing list, defect tracking system and version control repository; providing a website; interacting with committers; dealing with technical people; gathering consensus; and understanding important project management concepts. Karl is a veteran of several highly visible and widely used open source projects, and clearly draws on his extensive experiences (both positive and negative). The style is pleasantly conversational, and it's clear that he really knows what he's talking about and is speaking from a position of authority.
(Full Disclosure: I was a technical reviewer for this book, and was thoroughly impressed with it while reviewing it.)
(Full Disclosure: I was a technical reviewer for this book, and was thoroughly impressed with it while reviewing it.)
10 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Tons of insight and practical advice
23. Januar 2006
Von Eric Jain
- Veröffentlicht auf Amazon.com
Format:Taschenbuch
Didn't expect much useful information. But somehow this guy manages to talk about soft issues such as communication and politics without getting lost in the clouds. The book is more of a field guide than an anthropological study, so instead of speculation about what keeps participants motivated, you'll find practical advice how to keep people motivated and how to deal with specific problems. Should be read not only by people running open source projects, but by anyone who is somehow involved in an open source projects, and perhaps by everyone doing software development, too!
›
Gehen Sie zu Amazon.com, um alle 19 Rezensionen zu sehen
4.4 von 5 Sternen
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
Ähnliche Artikel finden
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
