Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: The Cathedral and the Bazaar


Related Topics

In the News (Thu 26 Nov 09)

  
  The Cathedral and the Bazaar - Wikipedia, the free encyclopedia
The Cathedral and the Bazaar (abbreviated CatB) is an essay 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.
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 developers.
The Bazaar model, in which the code is developed over the Internet in view of the public.
en.wikipedia.org /wiki/The_Cathedral_and_the_Bazaar   (550 words)

  
 cathedral - Hutchinson encyclopedia article about cathedral   (Site not responding. Last check: 2007-11-06)
Many cathedrals also house the relics of the saints, and so in the Middle Ages were centres of pilgrimage.
Some British cathedrals are referred to as ‘minsters’, such as Southwell and York, the term originating in the name given to the bishop and cathedral clergy, who were often referred to as a monasterium.
Most cathedrals were built during the Middle Ages and reflect the two main styles of medieval architecture (see English architecture: medieval): Romanesque architecture, or Norman architecture, and Gothic architecture.
encyclopedia.farlex.com /cathedral   (810 words)

  
 Linux-Kongress - The Cathedral an the Bazaar   (Site not responding. Last check: 2007-11-06)
I argue that the successes of Linux and fetchmail demonstrate the superiority of the bazaar style (when objective conditions are such that it can be made to work at all).
I then argue that the fundamental difference between cathedral and bazaar styles is their opposed assumptions about the nature of the debugging task.
The cathedral style is implied by the assumption that software bugs are deep, tricky, insidious phenomena that require the full-time attention of experts; the bazaar style is dependent on the assumption that bugs are shallow phenomena, readily found and fixed.
www.linux-kongress.org /1997/raymond.html   (592 words)

  
 the iCite net - The cathedral and the bazaar of user interface design   (Site not responding. Last check: 2007-11-06)
Commercial software maybe has better UIs because, within its "cathedral" process, it is probably more often possible for someone in charge to coordinate the positioning of IA / HCI / UE / UI designers as senior to software developers when it comes to making decisions about certain types of design issues.
Cathedrals seem to be all about guiding the "user" to specific results.
Note: for those that might not know, Eric Raymond wrote the excellent essay and book-to-be, The Cathedral and the Bazaar, about how and why open source development is different and great.
icite.net /blog/200403/cathedral_bazaar.html   (554 words)

  
 Kclug -- Book review: The Cathedral and the Bazaar
Cathedral style is used by projects like Emacs, NetBSD and many of the GNU tools.
Bazaar style is used by Linux, fetchmail and apache.
In bazaar style, if a project stagnates or the developer loses interest, he is likely to hand off the project to a competent, dedicated co-developer.
www.kclug.org /book-review.php?i=0596001088   (368 words)

  
 books   (Site not responding. Last check: 2007-11-06)
In the bazaar view, on the other hand, you assume that bugs are generally shallow phenomena—or, at least, that they turn shallow pretty quickly when exposed to a thousand eager co-developers pounding on every single new release.
Some claim that, lacking strong leadership, the bazaar can only handle the cloning and improvement of ideas already present at the engineering state of the art, but is unable to push the state of the art.
Cathedrals and bazaars and other social structures can catch that lightning and refine it, but they cannot make it on demand.
theopencd.sunsite.dk /Books/Cathedral.html   (15657 words)

  
 The Cathedral and the Bazaar at opensource encyclopedia   (Site not responding. Last check: 2007-11-06)
The Cathedral and the Bazaar is an essay by Eric S. Raymond on open-source software engineering methods, based on his experience managing a successful open source project, fetchmail.
The Cathedral model, in which access to software source code is restricted to members of the development team.
Eric S. Raymond: The Cathedral and the Bazaar (O'Reilly, January 2001; paperback ISBN 0596001088) — includes "The Cathedral and the Bazaar", "Homesteading the Noosphere", "The Magic Cauldron" and "Revenge of the Hackers"
www.wiki.tatet.com /The_Cathedral_and_the_Bazaar.html   (468 words)

  
 The Bazaar Method of Software Development
Eric Raymond’s seminal essay, "The Cathedral and The Bazaar," is credited with influencing Netscape to open up its source code.
However, in the bazaar mode, new versions are released as soon as they are patched together (during peak activity sometimes several times a day), with less concern for the presence of bugs.
In the bazaar view … you assume that bugs are generally shallow phenomena -- or, at least, that they turn shallow pretty quickly when exposed to a thousand eager co-developers pounding on every single new release.
www.slais.ubc.ca /courses/libr500/01-02-wt1/www/R_Tagami/Bazaar.htm   (584 words)

  
 BBC - h2g2 - The Cathedral and the Bazaar
After The Cathedral and the Bazaar he started the Jargon File, or The New Hackers Dictionary.
The Cathedral and The Bazaar looked at two different Open Source projects - Fetchmail and Linux - and their two differeing systems of development.
It was The Cathedral and The Bazaar where Linus' Law was first proposed - Given anough eyeballs all bugs are shallow.
www.bbc.co.uk /dna/ww2/A2568873   (457 words)

  
 oreilly.com -- Online Catalog: The Cathedral & the Bazaar
In 1997, Eric S. Raymond outlined the core principles of this movement in a manifesto called "The Cathedral and the Bazaar," which was published and freely redistributed over the Internet.
The Cathedral and the Bazaar is a must for anyone who cares about the computer industry or the dynamics of the information economy.
I had a chance to read Eric Raymond's essay, "The Cathedral and the Bazaar" about a year ago and was fascinated by it.
www.oreilly.com /catalog/cb   (1235 words)

  
 IST Problem #3   (Site not responding. Last check: 2007-11-06)
According to Jonathan Eunice, "The Bazaar is a market, a collection of individuals and organizations simultaneously cooperating and competing to meet their own goals" (Source).
The bazaar method uses open source distribution of its code which is released early and often to the numerous volunteers who collaborate together on the internet.
To construct such a foundation, the Cathedral's structured and planned problem-solving process would best layout the primary project "blueprint." Once this "blueprint" is established and the prototype system is developed, the Bazaar, open-source approach would eliminate the disadvantages that the Cathedral approach possesses.
www.personal.psu.edu /users/m/s/msr186/problem4.htm   (1141 words)

  
 Webliography of the early critique of The Cathedral and the Bazaar
In my experience, the "cathedral" and the "bazaar" are endpoints on a continuum, and neither really works well in its pure form.
Both the cathedral and the bazaar are approaches for developing free software; choosing between them is a technical matter.
Perhaps the theocratic overtones in the choice of the term Cathedral was Eric Raymond's allusion to what many see as the doctrinaire and sanctimonious rumblings from RMS the Pope, versus the more freewheeling and (in strict GNU terms) easily-corrupted style of Linux development.
www.softpanorama.org /OSS/early_catb_critique.shtml   (6772 words)

  
 DJzone Articles Prespectives
It was not about music, but about software; how the "Bazaar" model (i.e., thousands of developers spread over the Internet writing software because of inherent factors, such as love for solving problems and/or coolness) is superior to a "Cathedral" model (where a small group of developers control the development of a piece of software).
The crux of Raymond's points lies not in whether the Cathedral or the Bazaar model is the better choice, but how the Bazaar model is in accordance with the theory of complex adaptive systems, and how, this approach, in general, is a long-term model for tremendous progress in terms of innovation and creativity.
Creativity in the Bazaar occurs in a bottom-up environment (there are no restrictions; it doesn't even have to "work") as opposed to a top-down environment in the Cathedral (the major labels impose "rules" such as "has to sell well" on any creative output).
www.djzone.net /pg/archives/1199/did.shtml   (772 words)

  
 license-discuss@opensource.org: 3919: The Cathedral and the Bazaar
You must have a square table if you are to trade your wares here!" "Where does it say I must do such a thing?" The man reached in his pocket and angrily waved the paper in front of her.
Tent's are not allowed in the bazaar!" "But on days it is windy, a tent is much more comfortable.
We can't just have a bazaar of vendors, selling and trading their wares any way they feel like it.
www.crynwr.com /cgi-bin/ezmlm-cgi/3/3919   (640 words)

  
 The Cathedral and the Bazaar - Andamooka Reader   (Site not responding. Last check: 2007-11-06)
Added the endnotes on the Snafu Principle, (pre)historical examples of bazaar development, and originality in the bazaar.
I believed that the most important software (operating systems and really large tools like the Emacs programming editor) needed to be built like cathedrals, carefully crafted by individual wizards or small bands of mages working in splendid isolation, with no beta to be released before its time.
The fact that this bazaar style seemed to work, and work well, came as a distinct shock.
www.andamooka.org /reader.pl?pgid=catbcathedral_bazaar   (755 words)

  
 Preview: The Cathedral and the Bazaar | Linux Journal   (Site not responding. Last check: 2007-11-06)
Since 1996, several of his essays (most notably "The Cathedral and the Bazaar") have become required reading.
The volume contains "A Brief History of Hackerdom," "The Cathedral and the Bazaar," "Homesteading the Noosphere," "The Magic Cauldron," "The Revenge of the Hackers," an "Afterword," and two appendices.
They are the testimony of just why the BSDs and Linux, Perl and Python, Tcl and (even) Java are successful: these systems and languages have tens of thousands of programmers all over the world contributing to their excellence, instead of an encapsulated proprietary system that no one can debug.
www.linuxjournal.com /article/5238   (232 words)

  
 The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary (O'Reilly Linux)   (Site not responding. Last check: 2007-11-06)
It may be foolish to consider Eric Raymond's recent collection of essays, The Cathedral and the Bazaar, the most important computer programming thinking to follow the Internet revolution.
But it would be more unfortunate to overlook the implications and long-term benefits of his fastidious description of open-source software development considering the growing dependence businesses and economies have on emerging computer technologies.
Raymond engagingly narrates the fetchmail development process while elaborating on the ongoing bazaar development method he uses with the help of volunteer programmers.
www.megacity.org /BookCollection/Books/TheCathedralandtheBazaar.html   (355 words)

  
 Amazon.co.uk: The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary: Books   (Site not responding. Last check: 2007-11-06)
The Cathedral and the Bazaar takes its title from an essay of the same name which Raymond read at the 1997 Linux Congress and that was previously available only online.
A bazaar is an open market where everyone is free to evaluate software and decide to use or improve it.
A cathedral refers to closed, proprietary programming where the software is kept pure of outside influences and is developed in a small team, usually with a hierarchical organizational structure.
www.amazon.co.uk /exec/obidos/ASIN/1565927249   (1988 words)

  
 CommUnity of Minds : Working Together
In the bazaar view, on the other hand, you assume that bugs are generally shallow phenomena - or, at least, that they turn shallow pretty quick when exposed to a thousand eager co-developers pounding on every single new release.
Many people thinking about the bazaar model as I have presented it have correctly considered this critical, then jumped from it to the conclusion that a high degree of design intuition and cleverness in the project leader is indispensable.
Paul Eggert noticed the conflict between GPL and the bazaar model.
solutions.synearth.net /2004/01/30   (9537 words)

  
 The Cathedral and the Bazaar
When a Bazaar is Not a Bazaar, was thought-provoking but (IMO) basically wrongheaded.
Linux: A Bazaar at the Edge of Chaos comments perceptively on both CatB and HtN, and further develops some analysis from a point of view rooted in evolutionary biology and chaos theory.
The Cathedral and the Bazaar) from an anti-IPR point of view.
www.catb.org /~esr/writings/cathedral-bazaar   (916 words)

  
 [No title]
And I'll go on record as saying that finding it is the bigger challenge." But the point is that both things tend to happen quickly.
Here, I think, is the core difference underlying the cathedral-builder and bazaar styles.
In the bazaar view, on the other hand, you assume that bugs are generally shallow phenomena -- or, at least, that they turn shallow pretty quick when exposed to a thousand eager co-developers pounding on every single new release.
www.redhat.com /support/wpapers/community/cathedral/whitepaper_cathedral-4.html   (1323 words)

  
 Oakland.pm: Review of "The Cathedral and the Bazaar"
His main focus is on Bazaar style development, which we'll get to in a moment.
See "Some Bazaar Insights" for some (duh) insights related to this style of development.
Raymond claims that the Bazaar method of development is the most effective ever developed and provides theories and evidence to support that claim.
oakland.pm.org /reviews/bazaar.html   (2323 words)

  
 The cathedral and the bazaar
In any case, nowadays it is clear that open source development models are interesting case studies, where new methods for producing programs are being successfully tested.
One of them, which he calls ``cathedral-like development'' (as an analogy with how Middle Age cathedrals were built), is characterized by a relatively strong control on design and implementation.
The other one, which he calls ``bazaar-like development'', is based on informal communication between the coders, and several small and medium coding efforts that can be chosen at will by the volunteers (as in a bazaar, where everyone can choose what he wants).
eu.conecta.it /paper/cathedral_bazaar.html   (671 words)

  
 The Cathedral versus the Bazaar   (Site not responding. Last check: 2007-11-06)
The cathedral model of software was not the first way in which software was developed and distributed.
The developers of software in a cathedral model may be more familiar with the entirety of the code than others.
This should happen when the scope of the project is limited and specialized knowledge is required of the programmers, when the target market is small enough that a "critical mass" of hackers is not attracted to the effort, and when the users are not hackers.
www.ite.poly.edu /htmls/chapel_printable.htm   (3920 words)

  
 The future of music (v1.0)
The Bazaar is thriving and the Cathedral is dying
Also, it's possible that Cathedrals today will also adopt the Bazaar model and find other means of generating revenue besides basing it on the control of the spread of creativity.
The Bazaar model will enable creative endeavours between musicians who have the time and the inclination to pursue a full-time career and those who do not wish to dedicate their life to music exclusively.
www.ram.org /ramblings/philosophy/fmp/music_future.html   (2911 words)

  
 The Cathedral and the Bazaar   (Site not responding. Last check: 2007-11-06)
Eric Raymond compares two styles of software development using his own experience as illustration -- the traditional top-down (Cathedral) approach and the bottom-up (Bazaar) approach -- and points out how Internet-enabled cooperation makes the Bazaar approach highly efficient for the right tasks.
The Cathedral refers to a top-down command-and-control approach, whereas the Bazaar refers to a decentralized cooperative approach.
The success of the bazaar-made operating system Linux led Raymond to investigate why that approach succeeded when the accepted norm was that only a Cathedral approach could successfully create good software.
www.rheingold.com /CoopProto/application/entry.php?id=38   (833 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.