Centralized Approach To Implement OSS Compliance Program for Various Software Products
summary
Sony SSS creates a dedicated six-member centralized team inside its OSPO, builds an infra using FOSSology and FossID plus in-house tools, and records conclusions as SPDX SBOM artifacts. The team supports ~17–19 product teams and completes about 236 clearance requests over three years, reports ~60% reuse via differential analysis, applies smart sorting and a structured intake template to avoid bottlenecks, and claims consistent, repeatable license conclusions that shorten product release cycles.
AI-written summary · about
chapters (7)
- 0:00Centralized OSS compliance intro
- 4:37Compliance model options
- 13:23Centralized clearance in practice
- 17:13Challenges and mitigations
- 24:52Three years of key learnings
- 27:40Benefits of centralized approach
- 28:02Q&A on KPIs and details
related talks
45mOSS License Compliance for Software Developers, NOT for Legal Experts
38mHow We Navigate an Open Source Compliance and Contribution in a S...
36mOSPO Issues in a Conglomerate Company
34mSupply Chain Security, SBOMs and How OSPOs Can Play An Important Role Going Forward - An Ecosystem and Compliance Update
34mThe Role of OSPO Manager for the Organization’s Success
51mA Roadmap for Your OSS Security Lifecyle Journey to Protect Customers
26mNavigating Open Source: Establishing an OSPO for Organizational Success
26mOpen Source Program Offices