How to Choose an Open-Source License
summary
Explains that open-source requires an explicit license and gives concrete rules: GPL strong copyleft (Drupal uses GPL 2.0+ so modules/themes must carry GPL) forces derivatives and distributions to keep the same license, while permissive (MIT) lets others relicense or ship proprietary packages. Lays out four decision questions: what are dependency licenses, what do hosting Terms of Service require (GitHub forces forks), do derivatives/add-ons must reuse the same license, and do you forbid proprietary reuse. Cites tools TLDRLegal and choosealicense and the React relicensing episode.
AI-written summary · about
chapters (22)
- 0:00Intro
- 3:01WHAT WE'LL COVER
- 5:09WHAT IS COPYRIGHT?
- 6:19ONLY YOU CAN DEFINE USE
- 7:09ONLY YOU CAN CREATE IMPROVEMENTS
- 8:49OPENING SOFTWARE TO THE WORLD.
- 9:50OPEN SOURCE != FREE
- 10:51ALLOW FOR DERIVATIVES
- 11:39DRUPAL & BACKDROP
- 12:37INVITE IMPROVEMENTS
- 13:27DRUPAL CONTRIB
- 14:02THE UNLICENSE
- 14:42WHY USE AN OPEN-SOURCE LICENSE?
- 16:58SOME LICENSE CRITERIA
- 18:242 MAIN LICENSE TYPES
- 19:28PERMISSIVE
- 20:58COPYLEFT
- 22:53POPULAR (OSI-APPROVED) LICENSES
- 27:27LICENSE GUIDELINES
- 32:07RECAP
- 33:15RESOURCES & REFERENCES
- 34:27COME VISIT THE EAST COAST!
related talks
37mIntro to Open Source Licensing
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
01h 11mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
14mOpen Source Licensing in a Business World
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
05mWhy I Don’t Use the GPL
01h 04mWhat You Need to Know About Open Source—Trust Me, I’m a Lawyer
28mLicence to Code: Understanding open source licenses for developers