Software Licensing and Compliance: It's All About Community
summary
Explains license categories (permissive vs copyleft, strong vs weak copyleft), points out Apache’s patent clause, and focuses compliance on providing complete and corresponding source including dependencies and build instructions. Describes community enforcement principles: start private, assume good intentions, aim to get source, use lawsuits as last resort. Advises early dependency tracking and cross‑functional ownership (engineering legal business community). Gives resources (copyleft.org OSI GPL FAQ Apache FSF) and cites a Conservancy–VMware compliance outcome where code was removed rather than released.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:50Agenda
- 3:32Copyright History
- 7:51Permissive
- 13:06Compliance
- 16:19Complete Corresponding Source
- 17:39Who Does Compliance
- 23:26Community Enforcement Principles
- 25:40When to start thinking about compliance
- 31:17Resources
- 35:54Questions
related talks
42mOpen Source Licenses: Between Parish Wars and Radicalism
01h 38mOpen Source Licensing: Types, Strategies and Compliance
57mWhat 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
25mOpen Source Compliance
51mOpen Source License Compliance
01h 04mWhat You Need to Know About Open Source—Trust Me, I’m a Lawyer
51mThe Impact of Leveraging Open Source
