How To Talk To Your Lawyer About Open Source
Talkat Open Source Summit Japan + AI_dev: Open Source GenAI & ML Summit + Automotive Linux Summit 2025 · 2025-12-08..12-10·
summary
Practical steps for reducing friction between legal and engineering: build an engineer-lawyer translation service (they prototype it as a glossary/dialogue map but only show PowerPoint), adopt OpenChain (ISO 5230) as a shared risk framework, run wargaming scenarios to calibrate IP choices, and train a small cohort of engineers in IP basics. Applies the OSPO maturity model to legal understanding so both functions level up; examples show process changes, not magic fixes.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:02Lawyers in open source compliance
- 3:52Engineer-lawyer language gap
- 9:38Translation demo
- 13:31Collaboration steps today
- 14:55Legal department maturity models
- 16:25Training engineers in legal terms
- 17:26Open source IP outcomes
- 18:28Conclusion and Q&A
related talks
30mHow To Talk To Your Lawyer about Open Source
50mHow to talk your lawyer about FOSS
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
28mForming Lasting Relationships Between OSPOs and Legal Departments.
48mWhat You Need to Know About Open Source - Trust Me, I'm a Lawyer
27mTalking tech to legal: part 2
01h 04mWhat You Need to Know About Open Source—Trust Me, I’m a Lawyer
39mAppropriate Use of OSS - The Key Persons are Software Engineers