The encyclopedia · Engineering & Operations · Technical decision · 1991–1998
Linux was built by a bazaar of volunteers, not a cathedral team.
Eric Raymond's essay showed that releasing code early and often to a large crowd finds more bugs than a closed team does.
Linux · Red Hat
the move
Software bugs are hard to find, and the conventional approach was to build a product behind closed doors with a small team and release it when it was finished.
Linux grew differently: its kernel source was open, development was constant, and anyone could contribute. Raymond generalised this into a theory that 'given enough eyeballs, all bugs are shallow.'
The model worked because parallel debugging from a large, self-selected crowd found and fixed problems faster than a tightly controlled group.
why it works
- More contributors mean more independent attempts to break the same code
- Frequent releases keep the feedback loop short and the latest build testable
- Contributors self-select for the tasks they are best fitted to, so expertise finds the work
- Reputation, not salary, motivates contributions, so the effort scales without a bigger payroll
what transfers
If judgement is distributed, let the task be distributed too: open participation can out-debug an elite team because the bottleneck stops being the number of people on the payroll.
what came after
The Cathedral and the Bazaar became a foundational text of the open-source movement, and Linux matured into an operating system that powers much of the internet and the cloud. Companies later commercialised it, most prominently Red Hat, turning a volunteer bazaar into a large business.
references
spotted an error? The archive wants to know.