← all systems · see it in The System
Open-source software
Open-source software is computer software released under a licence allowing users to use, study, modify and distribute it to anyone for any purpose, in contrast to proprietary software; commonly defined by the Open Source Initiative's Open Source Definition. Whether 'open source' and 'free software' name the same thing is contested (C-3200).
Properties published scienceour proposal
Sourced fields, and our own readings.
| aliases | Free and open-source software |
| born at | 1983 (GNU announced 27 September 1983); named 'open source' in 1998; sharing culture from the 1950s |
| born precision | decades; contested (C-3220) |
| boundary | Inside: published source code under open licences, the communities, maintainers, tools, foundations and practices that build and keep it. Outside: proprietary and source-available software, copyright law itself, the firms, governments and users who take the software in, and the machines it runs on. |
| nested level | A kind of software by licence (sys:software) and a mode of production (commons-based peer production); it runs on people, the Internet and copyright law. |
| scale | social |
Measures (24) published science
| characteristic clock: Linux kernel release cycle | 2-3 months |
| Linux kernel merge-window rate | approaching 1,000 changes per day |
| Linux kernel changesets per release | about 13,000 changesets |
| Linux kernel developers per year | some 2,000 developers |
| share of code on the market of open-source origin (2022 estimate) | 80-96 % |
| supply-side value of widely used OSS | 4.15 billion USD |
| demand-side value of widely used OSS | 8.8 trillion USD |
| firms' software spending without OSS | 3.5 times current |
| share of demand-side value from 5% of developers | 96 % |
| Apache: share of changes by the top 15 developers | >83 (MRs and deltas); 88 (added lines); 91 (deleted lines) % |
| truck factor ≤ 2 (share of 133 popular GitHub projects) | 65 % |
| truck factor = 1 (share of 133 popular GitHub projects) | 34 % |
| superlinear production exponent (mean) | about 4/3 (range 1 to 3) dimensionless |
| OpenSSL Software Foundation donations per year (ceiling) | 2,000 USD per year |
| Heartbleed time undetected | two years |
| useful code reviewers (maximum) | 2-4 reviewers |
| companies running some or all operations on FOSS | 78 % |
| women among OSS developers, 2002 | 1.5 % |
| women among OSS contributors, 2005-2021 | 9.8 % |
| Linux share of top one million web servers | >96.4 % |
| modern applications containing OSS components (estimate) | 90 % |
| GPL share of open-source licence projects, 2011 | 42.5 (GPLv2); 6.5 (GPLv3) % |
| failed projects: usurped by competitor | 27 of 104 projects |
| France: OSS contributions per year after a procurement policy | nearly 600,000 contributions per year |
Open contentions (7) open contention
Where sources or readings disagree. Both stay on the map.
- C-413 Where do thoughts come from?
booked: No theory is proven, so the map lists the main ones side by side and doesn't pick one. It shows where thinking is handled in the brain, not where thoughts start.
the other reading: see C-413 - C-3200 Free software or open source: one idea or two?
booked: The map keeps the competing readings; none is ruled.
the other reading: FSF/Stallman: free software is about users' freedom; 'open source' misses the point and is a different, pragmatic aim; OSI: same software, a term to appeal to business - C-3215 Do many eyes really make bugs shallow?
booked: The map keeps the competing readings; none is ruled.
the other reading: Glass: a fallacy; useful reviewers top out at two to four; Heartbleed's two years and xz read as refutations; popular Google projects show 27% higher bug-fix rates (support) - C-3220 When did open-source software begin?
booked: The map keeps the competing readings; none is ruled.
the other reading: the 1950s-60s sharing culture as the start; 1998, the term and the OSI; 1983-85, GNU and the FSF - C-3221 Is open-source software a commons headed for tragedy?
booked: The map keeps the competing readings; none is ruled.
the other reading: tragedy of the commons if left unchecked (Eghbal 2016); non-rival: it 'becomes more valuable as it is used and contributed to' (encyclopedia) - C-3222 Do bigger open-source teams produce more per person or less?
booked: The map keeps the competing readings; none is ruled.
the other reading: Sornette et al.: superlinear, exponent about 4/3; Scholtes et al.: productivity per developer falls with team size - C-3224 Is public-domain software open source?
booked: The map keeps the competing readings; none is ruled.
the other reading: OSI: effectively open source for most practical purposes; OSI declines to certify it, since rights vary by jurisdiction
Cross-scale patterns seen here (25) our proposal
Shapes that recur when the same kind of problem is solved at different scales, and how each shows in Open-source software. Each links to every other system that shows it.
- borrowed-then-held (structural)
Linux began by reusing Minix's code and ideas (borrowed) and 'Eventually all the Minix code went away or was completely rewritten' (held); OpenSSL used SSLeay as its blueprint. More widely: the 1950s-60s sharing culture (a norm of the surroundings) was later held inside each work by its licence. - holding / entrainment (structural)
The mainline kernel sets the clock of its parts: subsystem trees deliver into a merge window that opens once per two-to-three-month cycle, where changes 'have been collected, tested, and staged ahead of time'. - same role, different builds (structural)
The job of paying for maintenance is done by unrelated builds: individual donations (Open Collective), state agencies (Sovereign Tech Agency), firms' paid developers and dual licences, foundations (Core Infrastructure Initiative). - same shape, opposite sign (structural)
Copyleft runs the one mechanism of a copyright licence grant with its sign reversed: the author's exclusive right is used to require sharing ('any modifications ... must be released under similar terms') instead of to forbid copying. - templating (structural)
Standard licence texts (GPL, MIT, BSD, Apache) are reused unchanged across thousands of projects; the Open Source Definition was itself adapted from the Debian Free Software Guidelines. - The carry (structural)
Overflow passed on: a core of 10-15 developers can write only so much; beyond it, code ownership separates additional groups into related projects (Mockus Hypothesis 2), and the kernel passes patch review down a lieutenant system because 'no single developer could possibly inspect and select every p - trade one property for another (structural)
Features traded for stability: 'a buggier version with more features and a more stable version with fewer features'; licences spread along a second dial, reciprocity (strong copyleft) against freedom to relicense (permissive). - who opens the door (structural)
The receiver opens the door ahead of time: the author's licence grants the rights before anyone arrives, and the project's maintainers are the port contributions enter through (review, CLA). - barrier-gates-complexity (partial)
The licence is the seal that lets a commons accumulate: when proprietary terms closed sharing (1970s-80s), the MIT lab's sharing culture was 'stifled'; under open licences 80-96% of code on the market is now of open-source origin. The without-the-licence case is shown historically, not as a test. - coordination-before-mapping (partial)
The bazaar coordinates many developers with 'roles ... not clearly defined' and no central design, read by Raymond as a self-correcting system of selfish agents; projects do keep roadmaps, so the without-map case is partial. - lightning (partial)
Sudden discharges that reshaped the field: the removal of the small left-pad package 'caused thousands of direct and indirect dependent projects to break'; Heartbleed and the xz backdoor drew funding and scrutiny after the event. - namespace completeness (the map predicts its gaps) (partial)
GNU's plan of a complete Unix-compatible system left one named empty slot: by 1992 it had 'all of the major operating system utilities' but no kernel; Linux filled the slot with the predicted property (Unix-like). - nested ladder (partial)
Licence strength as a ladder of conditions: permissive (keep notices) ⊂ weak copyleft (same licence under certain conditions) ⊂ strong copyleft (all derivatives same licence); also the contributor ladder new → non-core → core → leadership. - partner-becomes-part (partial)
GNU and Linus Torvalds's kernel, separate projects in a gain/gain fit, became one operating system 'now usually referred to as Linux'; the projects keep separate maintainers and histories, so inheritance stays separate (dark twin watched). - same toolkit, independent builds (partial)
Free Unix-like systems built from the same toolkit (Unix's design, C) by separate lineages: GNU with Linux, and the BSDs; BSD descends from Unix code, so independence is partial. - seed (partial)
The Linux kernel completed GNU and unpacked 'many thousands of Linux distributions'; licences that permit recombination let one release seed many derivatives. - symmetry breaking (name the cut) (partial)
One movement split at a named cut in 1998: free software (a social stance) and open source (development), 'almost the same category of software' read two ways. - The Payment to Entropy (partial)
Form: knowledge. Each hand-off of a project loses what only its few main authors knew (65% of 133 projects have truck factor ≤ 2); newcomers to newly open-sourced projects mostly leave; projects die when the main contributor's time or interest runs out. No per-hand-off efficiency is sourced. - Umwelt: each system carves its own slice of one shared medium (partial)
The system takes in only what arrives as written, public text: code, reports, licences and money routed through foundations; what users feel but do not report never enters. - causal ceiling (surface)
No single kernel developer can inspect every patch; this is a practical limit of attention, not a structural one. - not-diluting wins (surface)
Open code 'does not decrease in value for others when downloaded' while proprietary value is divided among buyers, and it now makes up 80-96% of code on the market; no dilution law is involved. - outside-to-inside (surface)
Organisations bring the outside commons in-house through Open Source Program Offices; the outside phase came first, but no source reads it as a partition moving inward. - red-queen (surface)
Attackers and maintainers both improve (xz's years-long trust building; supply-chain scrutiny), but no stalemate is sourced. - runaway from an unstable balance (surface)
Use and contribution feed each other ('becomes more valuable as it is used and contributed to'); no balance point is shown. - the whole sets the local reference (surface)
Upstream (the mainline) is the reference each downstream distribution and fork measures its patches against; read from the kernel's process, not tested.
Valence: what it trades, and with whom (14) published science
Each exchange with a neighbour, read from both sides: who gains, who pays, and what carries it.
- Operating system via sys:written-record · Open-source software gain
- Programming language via sys:written-record · Open-source software gain
- Software engineering via sys:written-record · Open-source software gain
- Human (Homo sapiens) via sys:sensory-environment · Open-source software gain
- Government via sys:human-society · Open-source software gain
- Software via sys:written-record · Open-source software gain
- Internet via sys:electromagnetic-field · Open-source software gain
- Labour market via sys:human-society · Open-source software gain
- Firm (the economic unit) via sys:market · Open-source software mixed
- Threat actor via sys:written-record · Open-source software loss
- Copyright via sys:written-record · Open-source software gain
- Cloud computing via sys:written-record · Open-source software mixed
- Supply chain security via sys:software-supply-chain · Open-source software mixed
- Public good (gains of collective action) via sys:written-record · Open-source software mixed
Partners and parts published science
Built from / builds (12)
- Programmers and language communities
- Code review
- Version control
- Open-source licences
- Issue trackers
- Foundations and fiscal hosts
- DBMS vendors competing (IBM, Oracle, open source, cloud providers)
- Typosquatters vs legitimate packages over names
- Proprietary and open-source software competing for users and developers
- Users who take without contributing against the maintainers of the commons
- MySQL under Oracle and its community forks
- Open-source projects displaced by stronger competitors
Sits inside / holds (2)
expressed by (19)
- Generation/Synthesis
- Recombination/Composition
- Scaffolding/Enablement (Meta-Tooling)
- Templating / Standardization
- Encapsulation & Modularity (Abstraction)
- Amplification/Scale-Up (Manufacture & Distribution)
- Symbiosis/Co-Creation (Collaborative Specialization)
- Distributed Autonomy/Decentralized Execution (Subsidiarity)
- Internal Coordination/Regulation
- Sensing/Scanning
- Intrinsic Motivation / Curiosity-Driven Sampling
- Trail-Marking / Externalized Memory (Stigmergy)
- Social Learning / Public Information Use
- Proactive Defense
- Self-Monitoring
- Validation of Identity/Intention
- Resilience & Repair
- Redundancy & Diversity
- Quality Control & Error Correction
floor filled by (20)
- Operating system
- Programming language
- Human (Homo sapiens)
- Written record (durable external marks: texts, archives, canon)
- Software
- Internet
- Labour market
- Firm (the economic unit)
- Package ecosystems (dependency networks)
- Copyright
- Organization
- Programmers and language communities
- Code review
- Public good (gains of collective action)
- Version control
- Issue trackers
- Free software movement
- Open Source Definition
- GNU General Public License
- Supply chain security
Kinds (6)
- Software
- Free software
- Copyleft software
- Permissively licensed software
- Public-domain software
- Open core / dual-licensed software
Notes published science
- Hoffmann, Nagle and Zhou put the cost of rewriting the most widely used open-source code once at $4.15 billion, but its value to the firms that use it at $8.8 trillion: without it, firms would spend 3.5 times more on software, and 96% of that value comes from just 5% of the developers (src:hoffmann-nagle-zhou-2024).
- Linux did not start from scratch: Torvalds began with code and ideas from Minix, and 'eventually all the Minix code went away or was completely rewritten' (src:raymond-1998-catb). Meanwhile OpenSSL, which secured much of the web, never received more than $2,000 a year in donations before Heartbleed (src:eghbal-2016-roads-bridges).
- Two big studies disagree about whether open-source teams grow more or less productive per head as they grow: Sornette's group found output rising as about the 4/3 power of active developers, while Scholtes's team found the Ringelmann effect, each person doing less; Maillart and Sornette argue they may not contradict each other as much as claimed (src:maillart-sornette-2016-aristotle-ringelmann).
Layers
The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.
open-source software as computer scientists and economists describe it: public source code under an open licence, up to a shared commons in use (reader's view)
- L1: Source code as public text: programs in readable form, published in repositories anyone can reach
- L2: The licence: rights to use, study, modify and share granted under copyright (the Open Source Definition's ten criteria; the four freedoms; permissive or copyleft)
- L3: Tools and records: version control (Git), issue trackers, mailing lists, continuous integration
- L4: Contribution and review: patches and pull requests reviewed by peers and merged by maintainers (the kernel's lieutenants)
- L5: Community and governance: leadership, core and peripheral contributors, voting, foundations, forks
- L6: Motives and economics: why people and firms contribute (personal need, fun, learning, peer recognition, career signals, business models) and the public-good problem
- L7: The commons in use: released software as shared digital infrastructure (80-96% of code on the market) and the movements' purposes (software freedom; open development)
the boardroom (shared floors)
- L4: Review and merge: peers test and review; maintainers and the kernel's lieutenants decide what enters
- L5: Community and governance: leadership at the centre, core and peripheral contributors, voting, foundations; forking as the exit
- L6: Motives and economics: signalling, intrinsic motives, business models, the public-good problem
- L7: The commons in use and the movements' purposes: free software's ethic (share with those who like it) and open source's pragmatism
way in: Bug reports and feature requests from users
- L1: Users running released software on their own machines (many co-developers and testers)
- L2: Requirements elicitation: bug reports and requests through trackers and mailing lists
- L3: Issue trackers (Bugzilla, Redmine) hold the reports
way in: Contributions: patches and pull requests from contributors
- L1: A change written by a contributor (anyone may propose; most leave soon)
- L2: The change offered under the project's licence (inbound terms; CLA where used)
- L3: Patch on a mailing list or pull request in Git
way in: Emotion and motive: fun, recognition, duty, burnout
- L1: Felt states of contributors: enjoyment, stimulation by visible progress, burnout
- L2: Peer recognition sought
- L3: Motivations held and shifting over a contributor's career
- L4: Continuing from duty despite burnout (small volunteer teams)
- L5: Belonging: caring about the community and its philosophy
way in: Law: copyright and licence enforcement
- L1: Copyright law: computer programs as literary works (US since 1980)
- L2: Licences written on copyright: the authors keep copyright and grant rights
- L3: Court precedent enforcing licence terms (Jacobson v Katzer, 2008)
- L4: The project's copyright arrangement: shared among contributors, or gathered by CLA for relicensing
way in: Money and paid time: donations, firms, governments
- L1: Money and paid developer time offered by individuals, firms and governments
- L2: Funding bodies: foundations, the Sovereign Tech Agency, the Core Infrastructure Initiative
- L3: The project's foundation or fiscal host receives it (OpenSSL's: donations never over $2,000 a year)
- L4: Spent on paid maintenance and testing (OpenSSL: much went to security testing)
way in: Thought: the developer's own idea or need
- L1: An idea or need arises in a developer's mind (origin contested, C-413)
- L3: The idea framed as a task: add a feature or fix a bug
way in: Upstream code: other projects' published code and dependencies
- L1: Code and ideas from other projects (Minix for Linux, SSLeay for OpenSSL)
- L2: Licence terms of the reused code decide whether it can be combined (copyleft vs permissive)
- L3: Package managers and dependency networks (npm, CRAN, Cargo...) deliver dependencies, transitively
way out: Definitions and policy: licences and definitions pushed into law and procurement
- L1: Government policy adopts them (US 2016: at least 20% of custom federal code released)
- L2: Approved licence lists and definitions (OSD, FSF definition)
- L7: The movements' aims: free software's ethics, open source's business case
way out: Fork: the code copied under a new name and governance
- L1: The code lives on outside the owner: 'Even if the company fails, the code continues'
- L5: The community splits from a project's owner (Oracle's MySQL)
way out: Hand-off: a maintainer passes the project on
- L1: A new maintainer holds the project (or none does: truck factor)
- L5: Losing interest, the maintainer hands the project to a successor
way out: Release: frozen, tagged and published versions
- L1: Released early and often to the public
- L3: Two lines: a development version with more features and a stable one with fewer
- L4: Merged changes collected, tested and staged
- L5: Release decision: freeze with only serious fixes