What You Need to Know About Open Source—Trust Me, I'm a Lawyer
summary
Clear definitions: open source means code distributed under an open-source license, not public domain, so rights hinge on license terms. Covers source availability, the right to make derived works, and when distribution triggers obligations (client-side assets count; server-side code usually does not). Contrast licenses: MIT/BSD are permissive, Apache 2 adds a patent grant and patent termination clause, GPL enforces copyleft (LGPL and AGPL address libraries and SaaS), and many real-world projects require CLAs or assignments. Practical advice: track components, assume “no license = no rights,” and adopt a team policy or scanning tool.
AI-written summary · about
chapters (27)
- 0:00Start
- 1:37Why does this matter?
- 2:39what is oss?
- 4:42free redistribution
- 5:13FREE SPEECH ZONE
- 6:21source code
- 7:56derived works
- 11:03SaaS
- 12:26non-interference
- 14:08non-discrimination
- 16:22intellectual property
- 17:43sale
- 20:35licenses
- 32:28permissive v. copyleft
- 35:13attribution
- 36:58bsd
- 37:27non-endorsement
- 38:51advertising
- 45:26apache
- 46:07patent license
- 50:22GPLZ Free Software
- 51:50most open
- 52:23versions
- 54:54compatibility
- 57:24license X license Y+
- 58:07key considerations
- 58:23cla & caa
related talks
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
01h 04mWhat You Need to Know About Open Source—Trust Me, I’m a Lawyer
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
28mLicence to Code: Understanding open source licenses for developers
51mThe Impact of Leveraging Open Source
37mIntro to Open Source Licensing
46mIntellectual Property Primer
41mHow to Choose an Open-Source License