"Installation Information" and GPLv3 & GPLv2 -- What Information Must you Provide, & What do you...
summary
GPLv3 requires delivering specific installation information — “methods, procedures, authorization keys or other information” — for sold or long‑term‑leased user products, with narrow exceptions (no ability to modify, warranty/network limits); a decision flowchart determines applicability. GPLv2 mandates source and build scripts but whether it also forces keys and reinstall methods is disputed: Software Freedom Conservancy says yes, other legal analysis says no. Automotive, telecom and IoT vendors face the practical risk; recent right‑to‑repair and enforcement debates could make this a live compliance issue.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:32Overview
- 1:37Installation Information
- 5:09Installation Information Requirements
- 6:28User Products
- 9:54Flowchart
- 10:42What is GPLv2
- 11:12GPLv2 Installation Information
- 11:37Source Code
- 13:01Free Software Foundation
- 14:34What is a Script
- 16:33Why does this all matter
- 17:01Industry Policies
- 18:49Is it correct
- 19:26Software Freedom Conservancy
- 22:29The Debate
- 23:35Counter Article
- 24:36Why is this important
- 25:55Linux Discussion
- 27:02Automotive Discussion
- 29:12Copyleft World
- 30:13Academic Debate
- 31:40Is this a precursor to something else
- 33:22Right to Repair
- 35:49Questions
- 42:22Regulatory Requirements
related talks
48mIntroduction to Linux's License
14mOpen Source Licensing in a Business World
43mSoftware Licensing and Compliance: It's All About Community
57mWhat You Need to Know About Open Source—Trust Me, I'm a Lawyer
01h 03mFree Software: It's not about the license
53mHow to Read a Software License and Not Die Trying
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
31mLicense Compliance 101