Open Source Software License Reading Listrecommended program of reading, comparison, and analysis
A number of people have asked me for hints on which open source licenses to read, in order to develop a working understanding of the field. The following list suggests a number of licenses, in a specific order, designed to help develop understanding.
Send suggestions, corrections, and feedback via GitHub.
Notes to Readers
When this program says read, read very carefully, at least twice. Take notes as you go. Don’t skip any terms. Get as much out of each license as possible.
When this program says compare, run a machine text-to-text comparison, using a word processor’s compare-documents feature. Then read the comparison very carefully, at least twice. Ask yourself: Why do these licenses differ? Get as much out of each comparison as possible.
When this program does not explicitly tell you to compare, compare anyway. Don’t take any license on its own. Ask how it differs from other forms, in style and in substance. Ask yourself why it differs.
This list might seem long, but each license is fairly short, as legal reading goes. In the end, there is not that much source material.
Be a legal vampire. Suck every last drop of meaning from every last license section and comparison. That effort, not finishing this list, will determine what you get out of this program.
Group 1: Permissive Licenses
Series 1: Academic Licenses
-
Read The MIT License, a very popular open source license.
-
Read The ISC License, a fairly popular open source license.
Compare to The MIT License.
-
Read The Two-Clause BSD License, a very popular open source license.
-
Read The Three-Clause BSD License, a fairly popular open source license.
Compare to The Two-Clause BSD License.
-
Read The Four-Clause BSD License, a historically significant, now discouraged, open source license.
Compare to The Three-Clause BSD License.
-
Read The BSD-2-Clause Plus Patent License, an relatively new open source license.
Compare to The Two-Clause BSD License.
Series 2: Agreement-Style Licenses
-
Read The Artistic License 2.0, a popular open source license among Perl developers.
-
Read The Apache License, Version 2.0, a very popular open source license.
-
Read The Educational Community License, Version 2.0, a niche open source license.
Compare to The Apache License, Version 2.0.
-
Read The Academic Free License v. 3.0, a niche open source license.
Group 2: Copyleft Licenses
Series 1: OSLs and GPLs
-
Read The Open Software License v. 3.0, a niche open source license.
Compare to The Academic Free License v. 3.0.
-
Read The Non-Profit Open Software License v. 3.0, an even more niche open source license.
Compare to The Open Software License v. 3.0.
-
Read The GNU General Public License, version 3, a popular open source license.
-
Read The GNU Affero General Public License, version 3, a popular open source license.
Compare to The GNU General Public License, version 3.
-
Read The GNU General Public License, version 2, a very popular open source license.
Series 2: Copyleft Background
-
Read Why you should use a BSD style license for your open source project.
-
Read Unhappy Coincidences.
Series 3: Weak Copyleft
-
Read The GNU Lesser General Public License, version 2.1, a niche open source license.
Compare to The GNU General Public License, version 2.
-
Read The Mozilla Public License, version 2.0, a niche open source license.
-
Read The IBM Public License v1.0, a historically significant, now superseded, open source license.
-
Read The Common Public License 1.0, a historically significant, now superseded, open source license.
Compare to The IBM Public License v1.0.
-
Read The Eclipse Public License 1.0, a historically significant, now superseded, open source license.
Compare to The Common Public License 1.0.
Series 3: License Compatibility
-
Read The Eclipse Public License 2.0, a niche open source license.
Compare to The Eclipse Public License 1.0.
-
Read The Common Development and Distribution License 1.0, a historically significant, now discouraged, open source license.
Compare to The Mozilla Public License, version 2.0.
Series 4: Reciprocal Licenses
-
Read The Sleepycat License, a historically significant, now discouraged, open source license.
Compare to The Two-Clause BSD License.
-
Read The Q Public License Version 1.0, a historically significant, controversial open source license.
-
Read The Reciprocal Public License 1.5, a historically significant, controversial open source license.
Group 3: Antilicenses
-
Read WTFPL, a popular open source license.
-
Read The Unlicense, a popular open source license.
-
Read The Zero-Clause BSD License, a niche open source license.
Compare to The Two-Clause BSD License.
-
Read The Fair License, niche open source license.
Review
-
Read The MIT License.
-
Reread The Apache License, Version 2.0.
Bonus Group
Series 1: Third-Wave Copyleft Licenses
Note: As of early 2019, whether these licenses count as open source software licenses remains controversial.
-
Read copyleft-next.
-
Read Parity.
-
Read The Server Side Public License, Version 2.
Compare to The GNU Affero General Public License, version 3.
Series 2: Ethical Licenses
Note: As of early 2019, these are not broadly considered open source software licenses.
Further Reading
Free Online
-
Larry Rosen’s Open Source Licensing
-
Andrew M. St. Laurent’s Understanding Open Source & Free Software Licensing
-
Richard Stallman’s Copyleft: Pragmatic Idealism
-
Google’s Open Source Policy Docs
In Print
-
Heather Meeker’s Open (Source) for Business
-
Van Lindberg’s Intellectual Property and Open Source
Teaching Notes
This program makes crucial use of Lawrence Rosen’s AFL and OSL. Those are not particularly popular licenses. But the textual comparison directly emphasizes the basic difference between permissive/academic and copyleft/reciprocal. I don’t think there’s a better license pair—BSD and Sleepycat?—to drive that difference home.
The licenses under Review will be the most relevant and popular for most practitioners. If I really, really had to cut this course down, I’d assign just those licenses. If I had to cut the course down substantially, but not that far, I would likely skip the reciprocal licenses and antilicenses, or cull them down to RPL 1.5 and WTFPL or Unlicense, respectively.
Your thoughts and feedback are always welcome by e-mail.