Computing History · Cluster
Open Source History
Licensing, communities, and governance.
- 01 What a Software License Does to a Copyright Default Copyright reserves reproduction, modification and distribution from the moment code is fixed, so a license is a conditional permission that lifts specific rights; permissive and copyleft terms differ only in the conditions attached.
- 02 How Copyleft Travels Through Derivative Works The GPL binds works based on the original, not software on the same disk: how the license text draws the boundary, what conveying a binary obliges a distributor to supply, and where library and file-scope licenses shift the line.
- 03 License Compatibility and the Direction of Relicensing Combining two licensed works produces one distribution that must satisfy every condition in it; why permissive code can move into copyleft but not the reverse, and which patent and version clauses block a combination outright.
- 04 SPDX License Expressions and Machine-Readable Provenance How a single identifier grammar replaced prose license statements, what the operators and version suffixes encode, and why the declared license of a package and the licenses of its files routinely disagree.
- 05 Contribution Agreements: Certification, License Grants, and Assignment A project can only grant what its contributors gave it, so inbound terms are chosen from three mechanisms with different costs: a signed-off certification, a broad license grant to a steward, or a transfer of copyright.
- 06 Maintainer Authority and the Fork as an Exit Mechanism How merge rights, review conventions and ownership files concentrate control of a project that no license grants anyone, and why the license makes forking always possible while the trademarks and distribution channels make it expensive.
- 07 What a Neutral Foundation Holds and What It Cannot Change Foundations exist to hold the assets a project cannot own as a group: copyright title, trademarks, funds and release infrastructure; their legal form decides what they can do, and neutrality is a matter of procedure rather than of intent.
- 08 Complying With Source Obligations When Shipping Binaries What counts as conveying a copy, how corresponding source is defined for a compiled artifact including its build scripts, and how a build can archive the exact sources and licenses that a shipped binary implies.
- 09 Termination, Cure, and Enforcement of License Conditions A failed condition removes the permission rather than merely breaking a promise, so the GPLs terminate rights automatically and then offer defined windows to get them back; who can sue is decided by who holds copyright.
- 10 Relicensing a Mature Project: Consent, Forks, and Downstream Effects Changing a project license is a copyright transaction with every rightsholder in the tree, not a policy announcement; the routes that avoid consent, the audit that establishes who must be asked, and what a change cannot reach.