Things Your Mother Didn't Teach You About....
summary
Concrete takeaways: put a LICENSE file in the repo, use a contributor license agreement or a developer certificate of origin (use the Signed‑off‑by line with git -s), don’t invent or append clauses to standard licenses, register and license trademarks (logos require permission; plain name is nominative use), plan exits and term limits to prevent burnout, and prefer known licenses so companies and distributors can safely consume the project.
AI-written summary · about
chapters (6)
- 0:00Introduction and philosophy
- 2:47Understanding copyright
- 6:00Managing contributions
- 9:28Licensing best practices
- 16:07Trademark and legal identity
- 21:28Sustainability and burnout
related talks
50mRunning a Successful Open Source Project
29mHey Kid! Don't Copy That Floppy!
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
49mLicense to Kill One's Code
23mGrowing A Successful and Sustainable Project
25mWhat Makes Open Source Work: Licensing and Beyond
45mOpen Source distributions in a cloud-native world: from a technical to a legal point of view
