InstitutionClaim Cited
The Linux ecosystem coordinates contributors and competing companies around a shared kernel through reciprocal licensing, public patch review, delegated maintainership, and a narrow point of final integration. Reuse and forking are broadly available, while practical influence still depends on expertise, maintainer attention, and sustained organizational investment.
How can a technical commons accept plural contributions without surrendering compatibility, quality, or coherent releases?
InstitutionClaim Cited
Netscape made the young web legible through a fast commercial browser, then discovered that the implementation layer could become both a path into an open protocol and a strategic chokepoint contested by a platform owner.
How can a commercial product make an open protocol useful at mass scale without turning implementation advantage into control of the commons?
InstitutionClaim Cited
The World Wide Web Consortium coordinates competing companies, experts, public participants, and implementers around open web standards. Its authority comes less from coercion than from credible process and adoption: consensus, implementation experience, review, formal objections, and patent commitments can keep the web larger than one vendor, while procedural complexity and unequal participation can still concentrate practical power.
How can rivals create shared technical rules without allowing any one implementation or institution to become the web's private governor?