Talking tech to legal: part 2
summary
Explains how legal teams translate engineering terms into enforceable rules, using examples like 72,000 components Ericsson ingests per year, debates over GPL/AGPL vs CC0, and real-world questions about linking, invoking binaries, embedded Linux and bash in products. Argues TLDRLegal five‑point summaries fail because license analysis behaves like a decision tree not bullets, notes Getty v Stability AI as an illustrative case for AI‑trained code and flags contract indemnity and jurisdictional uncertainty.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:05Engineer to legal counsel in open source
- 6:37Engineers and lawyers: mutual understanding
- 12:32GPL and legal policies
- 15:44CC0 and public domain misconceptions
- 17:09Why licenses can't be simplified
- 18:56Standard licenses and negotiation limits
- 21:25Legal jurisdictions and licenses
- 23:52AI-generated code copyright
- 26:40Q&A
related talks
19mHow To Talk To Your Lawyer About Open Source
30mHow To Talk To Your Lawyer about Open Source
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
50mHow to talk your lawyer about FOSS
26mPanel Discussion: Open Source Licensing
32mOpen Source Contributions in Today’s World
25mPatents and Copyright and Trademarks… Oh, why!?
33mResponsibility in Depth: Layering Licensing, Regulation, and More