Culture Change: Building an OSPO in a Proprietary Software Company
summary
A blueprint for starting an OSPO at a proprietary company: show that 10–15% have an OSPO yet nearly all products embed OSS; map motivation and placement (legal, marketing, engineering, R&D/strategy), set low-friction contribution and origin policies (licenses, approvals, CLA/DCO), run inner-sourcing to teach practices, track outbound and inbound metrics (PRs, commits, LFX/GitHub tagging), budget foundation memberships carefully, and accept that 3–7 years to change culture is typical.
AI-written summary · about
chapters (20)
- 0:00Building an OSPO at SAS
- 2:48Proprietary companies need OSPOs
- 5:38Culture change and open source
- 7:49SAS’s open source journey
- 9:16OSPO team and strategy
- 12:00Educating teams on open source
- 15:31Consuming vs. contributing
- 17:59Contribution policies
- 20:24License compliance
- 22:27Budgeting OSPO activities
- 25:21Measuring OSPO success
- 28:30Culture change in open source
- 30:53Q&A: Open source models
- 31:56Q&A: Tracking contributions
- 33:20Q&A: Impact on maintainers
- 34:26Q&A: Developer events
- 37:14Q&A: OSPO team size
- 38:25Q&A: Influence without authority
- 39:21Q&A: Foundations and collaboration
- 41:07Q&A: Costs and value
related talks
30mDemystifying OSPOs
32mOSPOs: Key Lever for Open Source Sustainability
01h 39mWorkshop: Building and Managing an Open Source Program Office
26mNavigating Open Source: Establishing an OSPO for Organizational Success
40mThree Cs to an Open Source Program Office- 01h 39mWorkshop: Building and Managing an Open Source Program Office
26mOpen Source Program Offices
40mHow Can Your OSPO Drive Open Source Business Value for Your Organization?