Stories From the Trenches: Effective Collaboration Between OSPOs and R&...
summary
Ericsson describes a central four-person OSPO in the CTO office working with an engineering center of excellence to push upstream contributions: two-year effort to resume Linux engagement, membership in Yocto, and active work on the Valky Redis fork. Success relies on developer presence and the power of the internal trio (OSPO, R&D, developers) forming fast task teams to win management buy-in. Practical outputs include OpenSSF best-practice guides (Python, C++ compiler, MLsec), applying Scorecard to Ericsson GitHub, and faster dependency-vulnerability fixes.
AI-written summary · about
chapters (10)
- 0:00OSPO and R&D collaboration intro
- 1:03OSPO models and structures
- 6:09Ericsson’s centralized OSPO
- 9:00Strategic shifts in large organizations through open source
- 11:06Linux upstream engagement case
- 14:16Valkyrie and dev-driven success
- 18:51Scaling cultural change
- 23:52Open source security challenges
- 30:34Key takeaways
- 32:23Q&A on value and contribution
related talks
31mScaling Open Source Software in a Large Telco R&D Environment
34mThe Role of OSPO Manager for the Organization’s Success
39mOSPOs in Energy, Transport, Automotive & Public Sector
40mThree Cs to an Open Source Program Office
45mPanel Discussion: Bring Your Product Manager to the Open Source Party
32mOSPOs: Key Lever for Open Source Sustainability
24mThe Challenge to Build a Distributed OSPO
01h 39mWorkshop: Building and Managing an Open Source Program Office