OSS License Compliance for Software Developers, NOT for Legal Experts
summary
Sony describes concrete steps for engineer-led license compliance: a company OSS committee of ~100 members plus an OSS Strategy Board, a public GPL source publication site and a newly open deep‑learning core on GitHub, and a training program that >500 engineers completed. Recommendations include using the OpenChain curriculum, read LGPL section 6 to decide linking vs. distribution, publish and upstream bug fixes, and keep internal guidelines permissive while enforcing “follow the license” compliance.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:57Satoru Ueda
- 2:56About each company
- 5:43Raise your hand
- 6:44What kind of world we can give you
- 12:06Risk risk risk
- 16:18GPL Contamination
- 22:59Collaboration
- 24:18Inhouse Community
- 25:41OSS Strategy Board
- 27:53Recommendation
- 30:46Why OSS
- 31:22OSS Boot Camp
- 31:39OSS Curriculum
- 32:01User User Community
- 34:34Abyssal Style
- 35:01Diversity
- 35:31Future
- 36:40LGPL
related talks
39mAppropriate Use of OSS - The Key Persons are Software Engineers
34mCentralized Approach To Implement OSS Compliance Program for Various Software Products
25mEnsuring OSS License Compliance the Easy Way
25mOpen Source Compliance
34mGrowing Open Source Culture Inside Sony
38mHow We Navigate an Open Source Compliance and Contribution in a S...
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
43mThe Automotive OSPO