How To Talk To Your Lawyer about Open Source
summary
Ericsson reports open source rising from ~5% in 1995 to >90% of lines in some products and a fast increase in unique components introduced each year, so legal and engineering must share concrete processes. It prescribes a lawyer‑engineer glossary, training and documented compliance processes for inbound internal and outbound code, and adoption of OpenChain (ISO/IEC 5230:2020) with template policies and evidence artifacts. The claim is legal teams convert from blockers to risk‑managing partners when organizations implement these steps and produce standard documentation of third‑party IP dependency.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:12Ericsson’s open source pillars
- 5:21Language gap between engineers and lawyers
- 7:50Engineer terms confusing lawyers
- 10:16Lawyers resist open source models
- 13:05Open source saves time and money
- 14:29Better legal-OSPO communication
- 16:33Legal-OSPO maturity models
- 18:20Legal must accept open source
- 20:50Open Chain compliance framework
- 24:04Translating OS concepts for legal
- 26:31Shared goals legal and OS teams
- 27:15Why Open Chain matters
- 29:15Q&A
related talks
50mHow to talk your lawyer about FOSS
19mHow To Talk To Your Lawyer About Open Source
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
42mOpen Source Compliance Management - Removing the Thorn from...
36mUsing OpenChain for IP Management
30mA Lawyer and an Engineer Walk Into a Bar and Talk Open Source
24mBuilding On Success: What’s the Future of Open Source?
01h 04mWhat You Need to Know About Open Source—Trust Me, I’m a Lawyer