License to Kill One's Code
summary
Only the license makes software open source, and sloppy notices in real projects (example: BusyBox binaries with mixed GPL/MIT/BSD files) routinely make code unusable. The talk shows dozens of broken cases — missing links, contradictory copyrights, “shamelessly stolen” headers — and proposes pragmatic fixes: put a clear license notice in every source file, tag every file with an SPDX expression so tools can auto-generate high‑quality SPDX data, and avoid top‑level LIC files and external links.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 2:20Disclaimer
- 2:54Post Open Source Software
- 4:15The License
- 5:01The Open Source Movement
- 5:14Licenses
- 5:58Open Source
- 7:49Guess What
- 8:57Busybox
- 10:01Licensing
- 11:15Package License
- 11:52Atomic Unit
- 12:31Understanding Licensing
- 13:08SPSS Licenses
- 14:22Im Sorry
- 14:51Example
- 17:59Whodunit
- 18:31I agree
- 18:54Strong intentions
- 19:35Readme file
- 20:32Copyright file
- 21:07License information
- 21:48What could have been done
- 24:43Commonsense rules
- 29:10Consumers
- 29:56Quality discussion
- 31:42Humans vs Computers
- 32:14Automation
- 32:55Silver Bullet
- 33:21Standard Syntax
- 34:41Simple Solution
- 35:28Summary
- 37:22Ian Fleming
related talks
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
01h 38mOpen Source Licensing: Types, Strategies and Compliance
14mOpen Source Licensing in a Business World
28mLicence to Code: Understanding open source licenses for developers
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
14mOpen-source it right (and avoid calling your IP lawyer)!
01h 03mFree Software: It's not about the license
39mA decade of lessons in Open Source licensing