The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary (abbreviated CatB ) is an essay, and later a book, by Eric S. Raymond is software engineering methods, based On His observations of the Linux kernel development process and His experience managing an open source project,fetchmail . It examines the struggle between top-down and bottom-up design . The attempt was first presented by the author at the Linux University in May 1999, inWürzburg and was published as part of the book in 1999.

The illustration on the cover of the book is a 1913 painting by Liubov Popova titled “Composition with Figures” and belongs to the State Tretyakov Gallery collection . [1] The book was released under the Open Publication License v2.0 around 1999. [2]

“The Cathedral and the Bazaar”

The essay 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 were presented as examples.
  • The Bazaar model, in which the code is developed over the Internet in view of the public. Raymond credits Linus Torvalds , 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 proposal that “given enough eyeballs, all bugs are shallow” (which he states Linus’s 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 code is available only to a few developers.

Lessons for creating good open source software

Raymond points to 19 “lessons” [3]

  1. Every good work of software starts by scratching a developer’s personal itch.
  2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
  3. Plan to throw one; You will, anyhow. (Copied from Frederick Brooks’ The Mythical Man-Month )
  4. If you have the right attitude, interesting problems will find you.
  5. When you are in a program, your last duty is to take a decision.
  6. Treating your users as co-developers is your least-hassle road to rapid code improvement and effective debugging.
  7. Release early. Release often. And listen to your customers.
  8. Given has large enough beta-tester and co-developer base, almost every problem will be quickly named and the fix obvious to someone.
  9. Smart data structures and dumb code works a lot better than the other way around.
  10. If you treat your beta-testers as if they are your most valuable resource, they will respond by becoming your valuable resource.
  11. The next best thing is good ideas from your users. Sometimes the latter is better.
  12. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.
  13. Perfection (in design) is not no more to take away. (Attributed to Antoine de Saint-Exupéry )
  14. Any tool should be useful in the expected way, but a truly great tool lends itself to you.
  15. When writing a booklet, you can use it as a booklet.
  16. When your language is nowhere near Turing-complete , syntactic sugar can be your friend.
  17. A security system is only as secure as its secret. Beware of pseudo-secrets.
  18. To solve an interesting problem, start by finding a problem that is interesting to you.
  19. Provided the development co-ordinator has a communication as much as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.

Legacy and reception

In 1998 the essay Helped the final push for Netscape Communications Corporation to release the source code for Netscape Communicator and start the Mozilla project; It was cited by Frank Hecker and other employees as an outside independent validation of his arguments. [4] [5] [6] Netscape’s public recognition of this influence brought Raymond renown in hacker culture. [7]

When O’Reilly Media published the book in 1999, it became one of the first (if not the first) complete and commercially distributed book published under the Open Publication License . [2]

Marshall Poe , in his essay “The Hive”, likens Wikipedia to the Bazaar model that Raymond defines. [8] Jimmy Wales himself Was in fact inspired by the work (as well as the arguments put forward in works prior to the Internet age, Such As Friedrich Hayek ‘s article ” The Use of Knowledge in Society “), arguing That “It ouvert My eyes to the possibility of mass collaboration “. [9]

In 1999 Nikolai Bezroukov published two Cited critical essays on Eric Raymond’s views on open source software, the second one called “A second look at The Cathedral and the Bazaar .” [10] [11] [12] [13] They produced a sharp response from Eric Raymond. [14]

See also

  • GNU Bazaar , a distributed version control system named to highlight its relationship with the “bazaar” model
  • ” Homesteading the Noosphere “


  1. Jump up^ “Colophon” . The Cathedral & the Bazaar . O’Reily Media . Retrieved 20 December 2011 .
  2. ^ Jump up to:b cathedral-bazaar
  3. Jump up^ Raymond, Eric Steven. “The Cathedral and the Bazaar” . Retrieved 18 April 2012 .
  4. Jump up^ “Epilog: Netscape Embraces the Bazaar” .
  5. Jump up^ Jim Hamerly and Tom Paquin with Susan Walton (January 1999). “Freeing the Source: The Story of Mozilla”. Open Sources: Voices from the Open Source Revolution (1st ed.). ISBN  1-56592-582-3 . Frank had done his homework, citing Eric Raymond’s paper, “The Cathedral and the Bazaar,” and talking to people throughout the organization – from engineering to marketing to management.
  6. Jump up^ Louis Suárez-Potts (1 May 2001), Interview: Frank Hecker ,, (Since it always gets in relation to Netscape’s Mozilla decision, I should also note that Eric Raymond’s paper “The Cathedral and the Bazaar” Was referenced by me and others who were lobbying Netscape’s management. “In my opinion the paper’s importance in the context of Netscape’s decision was mainly that it was already actively discussed and promoted within Netscape. I have to say that it is a good idea to make a decision on what to do next.
  7. Jump up^ Sam Williams (30 November 2011). Free as in Freedom [Paperback] Richard Stallman’s Crusade for Free Software . “O’Reilly Media, Inc.”. p. 161. ISBN  978-1-4493-2464-3 . When Netscape CEO Jim Barksdale cited Raymond’s ‘Cathedral and the Bazaar’ as a major influence on the company’s decision, the company instantly elevated Raymond to the level of hacker celebrity. Determined not to squander the opportunity, Raymond traveled to give interviews, advise Netscape executives, and take part in the eventual party celebrating the publication of Netscape Navigator’s source code.
  8. Jump up^ Poe, Marshall (September 2006). “The Hive” . The Atlantic . Retrieved 2012-07-05 .
  9. Jump up^ Schiff, Stacy. “Annals of Information” . The New Yorker . Retrieved 4 July 2014 .
  10. Jump up^ Karl Eugen Kurbel (23 June 2008). The Making of Information Systems: Software Engineering and Management in a Globalized World . Springer. pp. 222-. ISBN  978-3-540-79260-4 . Retrieved 15 October 2012 .
  11. Jump up^ Bezroukov,Open source software development as a specialty of academic research: Critique of vulgar Raymondism”Accessed 23 September 2010.
  12. Jump up^ Bezroukov,A second look at The Cathedral and the BazaarAccessed 23 September 2010.
  13. Jump up^ Jan Bergstra; Mark Burgess (19 December 2007). Handbook of Network and System Administration . Elsevier. pp. 202-. ISBN  978-0-444-52198-9 . Retrieved 15 October 2012 .
  14. Jump up^ Eric S. Raymond, “Response to Nikolai Bezroukov”


  • Raymond, Eric S. (1999). The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary . O’Reilly Media. ISBN  1-56592-724-9 .

Leave a Reply

Your email address will not be published. Required fields are marked *