EVOPEDIA

← 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.

aliasesFree and open-source software
born at1983 (GNU announced 27 September 1983); named 'open source' in 1998; sharing culture from the 1950s
born precisiondecades; contested (C-3220)
boundaryInside: 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 levelA 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.
scalesocial

Measures (24) published science

characteristic clock: Linux kernel release cycle2-3 months
Linux kernel merge-window rateapproaching 1,000 changes per day
Linux kernel changesets per releaseabout 13,000 changesets
Linux kernel developers per yearsome 2,000 developers
share of code on the market of open-source origin (2022 estimate)80-96 %
supply-side value of widely used OSS4.15 billion USD
demand-side value of widely used OSS8.8 trillion USD
firms' software spending without OSS3.5 times current
share of demand-side value from 5% of developers96 %
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 undetectedtwo years
useful code reviewers (maximum)2-4 reviewers
companies running some or all operations on FOSS78 %
women among OSS developers, 20021.5 %
women among OSS contributors, 2005-20219.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, 201142.5 (GPLv2); 6.5 (GPLv3) %
failed projects: usurped by competitor27 of 104 projects
France: OSS contributions per year after a procurement policynearly 600,000 contributions per year

Open contentions (7) open contention

Where sources or readings disagree. Both stay on the map.

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.

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.

Partners and parts published science

Built from / builds (12)

Sits inside / holds (2)

expressed by (19)

floor filled by (20)

Kinds (6)

Notes published science

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)

  1. L1: Source code as public text: programs in readable form, published in repositories anyone can reach
  2. 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)
  3. L3: Tools and records: version control (Git), issue trackers, mailing lists, continuous integration
  4. L4: Contribution and review: patches and pull requests reviewed by peers and merged by maintainers (the kernel's lieutenants)
  5. L5: Community and governance: leadership, core and peripheral contributors, voting, foundations, forks
  6. L6: Motives and economics: why people and firms contribute (personal need, fun, learning, peer recognition, career signals, business models) and the public-good problem
  7. 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)

  1. L4: Review and merge: peers test and review; maintainers and the kernel's lieutenants decide what enters
  2. L5: Community and governance: leadership at the centre, core and peripheral contributors, voting, foundations; forking as the exit
  3. L6: Motives and economics: signalling, intrinsic motives, business models, the public-good problem
  4. 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

  1. L1: Users running released software on their own machines (many co-developers and testers)
  2. L2: Requirements elicitation: bug reports and requests through trackers and mailing lists
  3. L3: Issue trackers (Bugzilla, Redmine) hold the reports

way in: Contributions: patches and pull requests from contributors

  1. L1: A change written by a contributor (anyone may propose; most leave soon)
  2. L2: The change offered under the project's licence (inbound terms; CLA where used)
  3. L3: Patch on a mailing list or pull request in Git

way in: Emotion and motive: fun, recognition, duty, burnout

  1. L1: Felt states of contributors: enjoyment, stimulation by visible progress, burnout
  2. L2: Peer recognition sought
  3. L3: Motivations held and shifting over a contributor's career
  4. L4: Continuing from duty despite burnout (small volunteer teams)
  5. L5: Belonging: caring about the community and its philosophy

way in: Law: copyright and licence enforcement

  1. L1: Copyright law: computer programs as literary works (US since 1980)
  2. L2: Licences written on copyright: the authors keep copyright and grant rights
  3. L3: Court precedent enforcing licence terms (Jacobson v Katzer, 2008)
  4. L4: The project's copyright arrangement: shared among contributors, or gathered by CLA for relicensing

way in: Money and paid time: donations, firms, governments

  1. L1: Money and paid developer time offered by individuals, firms and governments
  2. L2: Funding bodies: foundations, the Sovereign Tech Agency, the Core Infrastructure Initiative
  3. L3: The project's foundation or fiscal host receives it (OpenSSL's: donations never over $2,000 a year)
  4. L4: Spent on paid maintenance and testing (OpenSSL: much went to security testing)

way in: Thought: the developer's own idea or need

  1. L1: An idea or need arises in a developer's mind (origin contested, C-413)
  2. L3: The idea framed as a task: add a feature or fix a bug

way in: Upstream code: other projects' published code and dependencies

  1. L1: Code and ideas from other projects (Minix for Linux, SSLeay for OpenSSL)
  2. L2: Licence terms of the reused code decide whether it can be combined (copyleft vs permissive)
  3. 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

  1. L1: Government policy adopts them (US 2016: at least 20% of custom federal code released)
  2. L2: Approved licence lists and definitions (OSD, FSF definition)
  3. 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

  1. L1: The code lives on outside the owner: 'Even if the company fails, the code continues'
  2. L5: The community splits from a project's owner (Oracle's MySQL)

way out: Hand-off: a maintainer passes the project on

  1. L1: A new maintainer holds the project (or none does: truck factor)
  2. L5: Losing interest, the maintainer hands the project to a successor

way out: Release: frozen, tagged and published versions

  1. L1: Released early and often to the public
  2. L3: Two lines: a development version with more features and a stable one with fewer
  3. L4: Merged changes collected, tested and staged
  4. L5: Release decision: freeze with only serious fixes

Sources (26) published science

Software (encyclopedia)
Open-source software (Wikipedia, Wikimedia Enterprise snapshot 2026-11-01 via tools/wme)
Raymond ES (1998) The cathedral and the bazaar. First Monday 3(3). doi:10.5210/fm.v3i2.578 (behind its links)
Sornette D, Maillart T, Ghezzi G (2014) How much is the whole really more than the sum of its parts? 1+1=2.5: superlinear productivity in collective group actions. PLoS ONE 9(8):e103023, doi:10.1371/journal.pone.0103023 (behind its links)
Lerner J, Tirole J (2002) Some simple economics of open source. Journal of Industrial Economics 50:197-234 (NBER Working Paper 7600, 2000) (behind its links)
Copyleft (Wikipedia, WME snapshot) (behind its links)
Eghbal N (2016) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure. Ford Foundation (behind its links)
Free and open-source software (Wikipedia, WME snapshot) (behind its links)
Business models for open-source software (Wikipedia, WME snapshot) (behind its links)
The Linux Kernel documentation: How the development process works (behind its links)
Hoffmann M, Nagle F, Zhou Y (2024) The Value of Open Source Software. Harvard Business School Working Paper 24-038 (behind its links)
Mockus A, Fielding RT, Herbsleb JD (2002) Two case studies of open source software development: Apache and Mozilla. ACM TOSEM 11(3):309-346. doi:10.1145/567793.567795 (author copy) (behind its links)
Avelino G, Passos L, Hora A, Valente MT (2016) A Novel Approach for Estimating Truck Factors. ICPC 2016 (arXiv:1604.06766) (behind its links)
Maillart T, Sornette D. 2016. Aristotle vs. Ringelmann: on superlinear production in open source software. arXiv:1608.03608 (behind its links)
Linus's law (Wikipedia, WME snapshot) (behind its links)
Linux (Wikipedia, WME snapshot) (behind its links)
Przymus, Durieux 2025. Wolves in the Repository: A Software Engineering Analysis of the XZ Utils Supply Chain Attack. arXiv:2504.17473 (behind its links)
GNU General Public License (Wikipedia, WME snapshot) (behind its links)
Coelho J, Valente MT (2017) Why Modern Open Source Projects Fail. ESEC/FSE 2017 (arXiv:1707.02327) (behind its links)
Benkler Y (2002) Coase's Penguin, or, Linux and The Nature of the Firm. Yale Law Journal 112:369-446 (behind its links)
Gerosa M et al. (2021) The Shifting Sands of Motivation: Revisiting What Drives Contributors in Open Source. ICSE 2021 (arXiv:2101.10291) (behind its links)
Open Source Initiative: The Open Source Definition (behind its links)
Meyerovich LA, Rabkin AS 2013. Empirical analysis of programming language adoption. OOPSLA 2013 (author copy) (behind its links)
MacCormack A, Rusnak J, Baldwin C (2012) Exploring the Duality between Product and Organizational Architectures: A Test of the 'Mirroring' Hypothesis. Research Policy 41:1309-1324 (HBS Working Paper 08-039) (behind its links)
Decan, Mens & Grosjean 2019, An empirical comparison of dependency network evolution in seven software packaging ecosystems, Empirical Software Engineering (arXiv:1710.04936) (behind its links)
Stallman R (1985) The GNU Manifesto (gnu.org) (behind its links)