The Cathedral and the Bazaar is a collection of essays originally meant for programmers and technical managers, written by Eric S. Raymond on software engineering methods, based on his observations of the Linux kernel development process and his experiences managing an open source project, fetchmail.

I you like a deeper work on Linux development, I can recommend the book "Rebel Code" by Glyn Moody.

fetchmail, is an open-source software utility to retrieve e-mail from a remote mail server. It was developed by Eric S. Raymond from the popclient program, written by Carl Harris. Its chief significance is perhaps that its author, Eric S. Raymond, used it as a model to discuss his theories of open source software development in this book. Some programmers, including Dan Bernstein, getmail creator Charles Cazabon and FreeBSD developer Terry Lambert, have criticized fetchmail's design], its number of security holes, and that it was prematurely put into "maintenance mode". In 2004, a new team of maintainers took over fetchmail development, and laid out development plans that in some cases broke with design decisions that Eric Raymond had made in earlier versions.

The essays in the book describe open-source software, the process of systematically harnessing open develplment and decentralized peer review to lower costs and improve software quality. contrasts two different free software development models:

- The Cathedral model, in which source code is available with each software release, but code developed between releases is restricted to an exclusive group of software developers. GNU Emacs and GCC are presented as examples.

- The Bazaar model, in which the code is developed over the Internet in view of the public. Raymond credits Linus Torvalds, leader of the Linux kernel project, as the inventor of this process. Raymond also provides anecdotal accounts of his own implementation of this model for the fetchmail project.

The essay's central thesis is Raymond's proposition that "given enough eyeballs, all bugs are shallow" (which he terms Linus' law): the more widely available the source code is for public testing, scrutiny, and experimentation, the more rapidly all forms of bugs will be discovered. In contrast, Raymond claims that an inordinate amount of time and energy must be spent hunting for bugs in the Cathedral model, since the working version of the code is available only to a few developers.

When O'Reilly Media published the book in 1999, it achieved another distinction by being the first complete and commercially distributed book published under the Open Publication License.

I felt the book had some good points and then other times I was struggling to get myself to pick it back up. Overall worth the read but not in my top 5 list by any means.

The title says it all,
however, the caveat is that if the "instigator" of the particular form of software does not have the "cache" or "credentials" in the open source community then the chances of a REALLY BIG item being developed is rather small. BUT, if the "item" can catch on, then it can be done better and faster than a "paid for development".

I like this book for many reasons. First of all, it uses lots of specific examples to prove a point. Two, the author was right at the front lines during the formative days of Linux and open source and he does not hide his biases. Three, he is a very insightful guy and he sure as heck knows how to turn a phrase.

That said, the book is not that far removed from a polemic. He has drawn his conclusions and moved on from contemplation to conviction. So if there is any point along the way you disagree, what follows is going to give you frustration.

I'd suggest reading this in conjunction with The Success of Open Source, which despite its title, is far more balanced and has the best history of the open source movement I have ever read. I've given that book 5 stars. The two balance each other out quite nicely.

This book is a great and very interesting read. While you can get the collection of essays online, for free. I prefer the book, easier on my eyes. ESR (author) tries to keep it straight foreward, however at times he drifts into a technical world, which somewhat flew over my head. If you are interested in the Open Source community, namely what makes it work, and what problems it has in store, this is a great book.
He Gives personal experience which I really value, and he doesn't try and hide the short comings of Open Source Development.