Our Journey to Open Source - from “Conservative” Japanese Company
summary
A VS Code extension called Editor for SBOM implements SPDX v2.2 editing with syntax highlighting, hover info, completion, go-to-declaration and basic syntax checks, built with Node.js and a Language Server Protocol layer and published under MIT license. Releasing it forces a 10-step company review (patent, export control, IP, QA, PR, OSS compliance) that took five months to complete; the company now hosts three OSS projects and plans process automation.
AI-written summary · about
chapters (14)
- 0:00Our open source journey
- 1:05Speaker and company background
- 2:32Why release open source
- 6:14Developer’s motivation
- 8:03Conservative company culture
- 13:48Open source release challenges
- 15:33Manager’s perspective
- 17:20Ten-step code prep process
- 22:45Open source compliance checks
- 26:18Final approvals and support
- 29:17Timeline and lessons learned
- 32:59Future open source improvements
- 35:32Conclusion and next steps
- 36:22Q&A
related talks
29mAuto Generate SBOMs for Your Open Source Project Written in Any Language Running on Any Platform
39mSOS: Sustainable Open Source
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
25mEnsuring OSS License Compliance the Easy Way
33mORT Automate compliance using Open Source & InnerSource
45mOpen Source on Purpose; Strategy, Process and Tools to Succeed
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
26mThe FOSSology Project – Open Source Software for Open Source License Compliance