Linus’s Law

E210070

Linus’s Law is the open-source software development principle that “given enough eyeballs, all bugs are shallow,” emphasizing the power of many reviewers to quickly find and fix defects.

All labels observed (2)

How this entity was disambiguated

Statements (45)

Predicate Object
instanceOf adage ⓘ
aphorism ⓘ
open-source software development principle ⓘ
software development principle ⓘ
appliesTo collaborative software development ⓘ
open-source software projects ⓘ
associatedWithDevelopmentModel bazaar model of software development ⓘ
associatedWithMovement open-source software movement ⓘ
assumes availability of source code ⓘ
large and active developer community ⓘ
many users acting as co-developers ⓘ
coinedBy Eric S. Raymond ⓘ
linked to: Eric Raymond
contextOfOrigin discussion of open-source vs proprietary development models ⓘ
contrastedWith cathedral model of software development ⓘ
emphasizes importance of many reviewers ⓘ
peer review of source code ⓘ
rapid bug discovery ⓘ
rapid bug fixing ⓘ
firstDescribedInMedium essay ⓘ
firstDescribedInWork The Cathedral and the Bazaar ⓘ
hasAlternativeFormulation Given enough eyeballs, all bugs are shallow. ⓘ
hasCriticism coordination and communication overhead can increase with many contributors ⓘ
eyeballs must be skilled to be effective ⓘ
not all projects have enough qualified reviewers ⓘ
some bugs remain hard even with many reviewers ⓘ
hasFullName Given enough eyeballs, all bugs are shallow ⓘ
linked to: Linus’s Law
hasShortDescription Principle that many reviewers make software bugs easier to find and fix ⓘ
influencedBy Linux kernel development practices ⓘ
influences advocacy for public code review ⓘ
arguments for open-source development ⓘ
software engineering best practices ⓘ
namedAfter Linus Torvalds ⓘ
relatedNamedEntity Eric S. Raymond ⓘ
linked to: Eric Raymond

Linus Torvalds ⓘ
Linux kernel ⓘ
The Cathedral and the Bazaar ⓘ
relatesToConcept bug detection ⓘ
code transparency ⓘ
crowdsourced debugging ⓘ
peer review ⓘ
quality assurance in software ⓘ
software reliability ⓘ
usedAsArgumentFor large-scale community involvement in debugging ⓘ
releasing source code to the public ⓘ
transparent development processes ⓘ

How these facts were elicited

Referenced by (2)

Full triples — surface form annotated when it differs from this entity's canonical label.

Linus’s Law → hasFullName → Given enough eyeballs, all bugs are shallow ⓘ
linked to: Linus’s Law