Hey Kid! Don't Copy That Floppy!
summary
GitHub mining shows 47.1% of projects lack a license, which creates real legal risk: forking plus modification is a derivative work and can be a copyright violation, DMCA takedowns are practical, and patents can silently taint contributions. Recommended actions are concrete: add a LICENSE file (MIT/BSD, GPLv3, Apache 2.0), require a contributor license agreement to reassign or license contributor rights, and use tools like license_generator gem and CLA Hub to enforce contribution terms.
AI-written summary · about
chapters (8)
- 0:00Introduction and disclaimer
- 2:40Brief history of copyrights
- 5:48Open source licenses overview
- 10:27Why licensing matters
- 16:42License deep dive
- 20:10Developer rights and contracts
- 25:04Recap and next steps
- 26:49Q&A and resources
related talks
49mLicense to Kill One's Code
26mThings Your Mother Didn't Teach You About....
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
14mOpen-source it right (and avoid calling your IP lawyer)!
50mRunning a Successful Open Source Project
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
42mMobiconf 2018: Jan Hudzik, Miquido
25mWhat Makes Open Source Work: Licensing and Beyond