- Atlas
- Computer Science
- Open Source Software
Open Source Software
Open source software is software whose source code—the human-readable instructions a programmer writes—is made available for anyone to inspect, modify, and redistribute.
9 frameworks, from 1983 to today · Software Engineering · Computer Science
- Free Software Movement 1983-Present
- Permissive software license 1988-Present
- Copyleft 1989-Present
- Open Source Commercialization 1993-Present
- The Bazaar Model 1997-Present
- The Open Source Definition 1998-Present
- Meritocratic Foundation Governance 1999-Present
- Distributed Version Control and Forge Workflow 2005-Present
- Open Source Sustainability 2014-Present
Overview
Open source software is software whose source code—the human-readable instructions a programmer writes—is made available for anyone to inspect, modify, and redistribute1. That sounds like a narrow technical arrangement, but it turned out to be a social and economic invention as much as a legal one. It made possible a way of building large, long-lived systems in which thousands of strangers, most of whom never meet and many of whom are unpaid, cooperate on code that businesses and governments then depend on. The history of open source is the history of how that cooperation was made legal, technically practical, and economically sustainable—and of the arguments people had about whether it was a moral cause, an engineering method, or a business strategy.
Free software and the moral argument
In the 1970s and early 1980s, most software shipped with its source code. Academic and corporate programmers routinely shared and modified each other's programs, and the culture of the MIT Artificial Intelligence Laboratory, where Richard Stallman worked, treated access to source as normal. That changed as the commercial software industry grew: companies began distributing programs as opaque binaries, and licensing terms restricted copying and modification123. Stallman found that he could no longer fix a malfunctioning printer because the driver's source was withheld4.
His response, in 1983, was to announce the GNU Project: a plan to build a complete, Unix-compatible operating system whose source would always be free5243. In 1985 he founded the Free Software Foundation and published the GNU Manifesto, framing the work as an ethical campaign1536. "Free" here meant freedom, not price—the freedom to run, study, change, and redistribute the software12. The project produced foundational tools: the GNU C Compiler (GCC), the GNU Emacs editor, and the Bash shell, among many others. By the early 1990s GNU had everything needed for an operating system except a working kernel17.
The kernel came from Linus Torvalds, a Finnish student who in 1991 released a hobby kernel called Linux and, crucially, invited others to contribute1387. Combined with GNU tools, Linux became the free operating system the GNU Project had aimed at147. The Free Software Movement thus established the core idea of the field: that source availability is a political and practical commitment, and that a community of contributors can build software of professional quality.
Copyleft: using copyright against restriction
Free software needed a legal mechanism, because copyright law by default forbids copying and modification9. Stallman's invention was copyleft: a license that uses the copyright holder's powers to grant everyone permission to copy, modify, and redistribute—on the condition that derivative works carry the same permissions110. The GNU General Public License (GPL), first released in 1989, is the canonical example11011. If you distribute a modified version of GPL code, you must make your modified source available under the GPL too11. This "viral" property was deliberate: it kept improvements to the commons.
Copyleft was contested. Some developers preferred permissive licenses, which allow modification and redistribution with few conditions and permit the code to be incorporated into proprietary products112. The best known are the MIT License and the BSD licenses, both predating the GPL in spirit and widely used1121314. The choice between copyleft and permissive licensing became one of the field's enduring debates, and it maps onto a deeper disagreement about whether freedom should be defended or merely offered.
The "open source" rebrand and the business question
By the late 1990s, free software was technically strong but commercially suspect: the word "free" and the movement's rhetoric alarmed businesses. In 1998, in response to Netscape's decision to release the source of its browser (which became Mozilla), a group including Eric Raymond and Bruce Perens coined "open source" as a marketing-friendly term emphasizing practical benefits—better quality, faster development, lower cost—rather than ethics. The Open Source Initiative (OSI) was founded that year to certify licenses that meet a definition of open source: free redistribution, source availability, permission for derived works, and no discrimination against persons or fields of use11516.
The rebrand worked commercially. Companies began building businesses around open source: selling support and services (Red Hat), offering open-core products where a free version seeds demand for a paid one, and using open source components to build proprietary systems11718. This commercialization was not universally welcomed; some free-software advocates saw it as diluting the movement's principles. But it established that open source could coexist with profit, and it pushed open source into the mainstream of corporate software engineering.
The bazaar: how distributed development actually worked
The methodological breakthrough was described by Eric Raymond in his 1997 essay The Cathedral and the Bazaar11920. He contrasted two models: the "cathedral," in which a small closed group designs and releases software in careful stages, and the "bazaar," in which development is opened to anyone and proceeds through many small, public contributions119. Raymond's famous formulation—"given enough eyeballs, all bugs are shallow"—captured the claim that wide review finds defects faster than any small team can1.
The essay was influential because it explained, in engineering terms, why the Linux approach worked. The practices it described became standard: public mailing lists and bug trackers, maintainers who review patches, releases made often, and a norm that contributions are judged on their merits rather than the contributor's credentials. This is the bazaar model of development, and it is the ancestor of the pull-request workflow used across the industry today.
Foundations and meritocratic governance
As projects grew, they needed neutral homes. A company owning a project could favor its own interests; a single leader could become a bottleneck. The response was the nonprofit foundation. The Apache Software Foundation, incorporated in 1999, formalized a model in which contributors earn rights through demonstrated work—a meritocracy in the project's own sense—and decisions are made by committers and a project management committee rather than by an owner. The Linux Foundation (founded 2000 as the Open Source Development Labs) and later the Mozilla Foundation took on similar roles: holding trademarks, managing legal and financial matters, and providing a neutral venue where competing companies could collaborate.
This governance model mattered because it solved a coordination problem: firms that were rivals in the market could jointly fund infrastructure they all depended on, trusting that no single one controlled it. The foundation model is now standard for large infrastructure projects, from the Apache web server to the Linux kernel itself.
Version control and the forge
The technical infrastructure of collaboration evolved alongside the social model. Early projects coordinated through mailing lists and patch files. The first widely used version control system for open source was Concurrent Versions System (CVS), which let many developers work on a shared repository; it was later largely displaced by Subversion. These were centralized systems: one server held the history, and developers checked out and committed to it.
The decisive change was distributed version control, in which every developer holds a full copy of the repository and its history121. Git, created by Linus Torvalds in 2005 to manage the Linux kernel after a licensing dispute ended the project's use of a commercial tool, made branching and merging cheap and fast2221. Distributed version control changed the workflow: contributors could work independently, then propose changes for review. Platforms built around it—GitHub, launched in 2008, and GitLab, among others—turned the patch-and-mailing-list process into the pull request, a web-based review and discussion of a proposed change. The "forge" (a hosting platform for repositories, issues, and review) became the everyday environment of open source work, and its conventions—forks, branches, continuous integration on every pull request—shaped how software is built far beyond open source.
Sustainability and the maintenance problem
The successes exposed a structural weakness. Much of the world's critical infrastructure came to rest on small projects maintained by a handful of volunteers, often unpaid. The 2014 Heartbleed bug in OpenSSL, a library used to secure a large share of internet traffic, revealed that a project of enormous importance had minimal dedicated funding. The 2018 incident in which a developer removed a small package called left-pad from the npm registry, breaking builds across the JavaScript ecosystem, showed how fragile dependency chains had become. The 2021 Log4Shell vulnerability in the widely used Log4j logging library made the same point again.
These events turned sustainability into a recognized problem: how to fund maintenance, how to share responsibility among the companies that depend on a project, and how to keep a project alive when its original maintainer steps away. Responses have included corporate sponsorship, foundation-funded maintainers, and the recognition that "free" software is not costless to produce. The question remains open, and it is the field's central unresolved tension: the commons works, but someone must tend it.
Where the field stands
Open source is now the default substrate of software engineering1. Most modern applications are assembled largely from open source components, and the practices it pioneered—public review, distributed version control, continuous integration, transparent issue tracking—have been absorbed into proprietary development as well. The original debates persist in new forms: copyleft versus permissive licensing, corporate influence versus community governance, and the ethics of the free-software tradition versus the pragmatism of the open source label. The live questions are about money and power—who pays for maintenance, who controls the platforms where collaboration happens, and whether the openness that made the field successful can survive its own scale.
References
- Open-source software (introduction, Free software, History, Key projects, Licensing, Definitions and controversies, Value, Development model, Development tools), Wikipedia
- Free software (History, introduction), Wikipedia
- Free and open-source software (History), Wikipedia
- GNU Project (Origins, introduction), Wikipedia
- Free software movement, Wikipedia
- Free Software Foundation, Wikipedia
- Linux kernel (History, introduction), Wikipedia
- Linux, Wikipedia
- Open-source license (introduction, Background), Wikipedia
- Copyleft, Wikipedia
- GNU General Public License (History, introduction), Wikipedia
- Permissive software license, Wikipedia
- MIT License, Wikipedia
- BSD licenses, Wikipedia
- Open Source Initiative (introduction, History), Wikipedia
- The Open Source Definition, Wikipedia
- Open-core model, Wikipedia
- Business models for open-source software, Wikipedia
- Open-source software development (History), Wikipedia
- The Cathedral and the Bazaar, Wikipedia
- Distributed version control (introduction, History), Wikipedia
- Git (introduction, History), Wikipedia
The frameworks of Open Source Software
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1983-Present
- 1988-Present
- 1989-Present
- 1993-Present
- 1997-Present
- 1998-Present
- 1999-Present
- 2005-Present
- 2014-Present

Open Source Software is a planet in Nousfarer
Its city has a tower for each of these 9 frameworks. Land, walk in, and climb one concept at a time.
Land on Open Source SoftwareRelated fields
More in Software Engineering
- Computing Education
- Design Patterns
- Devops And Sre
- Formal Methods
- Requirements Engineering
- Software Architecture
- Software Engineering
- Software Evolution
- Software Process Models
- Software Testing
See where Open Source Software sits on the Map of Human Knowledge