Per Ploug Krogslund on "Has Open Source outgrown the OSPO?"
summary
Claim: open source is now business-critical and can no longer live inside a tiny centralized team. Evidence: many organizations discover that a two- or three-person OSPO cannot cover license risk, supply-chain monitoring, contributor relations and product integration simultaneously. Proposal: move responsibilities into primary functions — engineering, legal, security and procurement — or reinvent the OSPO model into federated roles. Conclusion: current OSPO definitions are outdated and require concrete redefinition or redistribution to scale.
AI-written summary · about
related talks
26mNavigating Open Source: Establishing an OSPO for Organizational Success
26mOpen Source Program Offices
15mFrom Code to Market: Strategic Business Models and OSPO Implementation
40mThree Cs to an Open Source Program Office
30mDemystifying OSPOs
21mScaling Internal Collaboration with Open Source Operating Models
32mOSPOs: Key Lever for Open Source Sustainability
39mHow Can Your OSPO Maximize Open Source Business Value for the Organization?