Challenges & Opportunities for OSPOs in Asia-Pacific
summary
Survey-backed status: 50% of respondents have an OSPO (the highest level in five years) and 65% of organizations contributing code upstream report formal OSPOs. Asia‑Pacific shows both opportunity and gap: APAC orgs are twice as likely to want a program but lack time or resources, with hiring/talent and small org size seen as top barriers. Practical steps that worked: appoint an OSPO leader, prioritize 1–3 core responsibilities, set simple approval and compliance processes, invest in developer education and metrics to prove continuity.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:49Agenda
- 6:50Engaging with Open Source
- 8:34Strategic Open Source
- 10:48What is an OSPO
- 14:17Hospital Survey
- 16:18Opportunities
- 19:08Talent requirements
- 20:33Primary responsibilities
- 21:53One size does not fit all
- 25:13Minimum Viable Hospital
- 26:58Hospital Structure
- 28:25Hospital Responsibilities
- 30:45Internal Policies
- 31:48Sustainability
- 33:10TODO Model
- 37:00Recommendations
- 38:28TODO Group
- 40:50Resources
- 41:05Questions
- 44:52Survey data
related talks
36mThe State of OSPOs in the Asia-Pacific Region in 2023
31mThe State of OSPOs in Asia 2023
25mThe State of OSPOs and OSS Management 2025 Research Findings by TODO Group
30mDemystifying OSPOs
50mSo What is Next for OSPOs in 2023 and Beyond?
32mOSPOs: Key Lever for Open Source Sustainability
46mOSS Management & OSPO Ask Anything
41mThe OSPO Panel of JAPAN 2023: How to Accelerate OSPO?