Open Source Compliance Management - Removing the Thorn from...
summary
Companies adopt the OpenChain Specification 2.1 (ISO/IEC 5230) as a practical blueprint: create a written open source policy, train staff, automate scanning of inbound dependencies, and document inbound/outbound processes so IP risk is addressed at intake and at product shipping. Example outcomes: Ericsson cites 60,000 granted patents and describes moving legacy project licensing to Apache; Nokia declares Nokia conformant with OpenChain after building policy, training, and supply‑chain checks. The result is measurable process control, not just advocacy.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:25Talk disclaimer
- 2:29Lawyers in open source compliance
- 5:17Telecom open source compliance
- 8:27Rising open source automation
- 10:14IP and open source in telecom
- 11:38IP department’s open source journey
- 14:07Open source as third-party IP
- 16:57Open source licenses and limits
- 18:01Nokia’s OpenChain announcement
- 19:06OpenChain for compliance processes
- 21:33IP concerns with open source
- 23:01Managing open source copyrights
- 24:47Cultural gaps IP vs open source
- 28:16Aligning IP and open source
- 30:00OpenChain for IP management
- 31:45IP and open source collaboration
- 33:08IP department maturity model
- 34:51Why systematic compliance matters
- 36:59OpenChain benefits and standards
- 38:47Q&A
related talks
36mUsing OpenChain for IP Management
16mOpen Source Consumption/ Adoption Manifesto
38mPanel: Open Source Management Based on Open Source
33mHow OpenChain Became The International Standard for Compliance
39mComplex Made Simple
17mUnderstanding How OpenChain ISO/IEC 5230 and ISO/IEC 18974 Support InnerSource
29mTrusted Supply Chains - How OpenChain Makes a Difference in a...
30mHow To Talk To Your Lawyer about Open Source