Managing In The Open, Managing Contributions: The challenges of OSPO developers management
summary
Aiven’s OSPO runs about 15 full‑time upstream contributors, including five maintainers of core dependencies and two maintainers of unrelated projects, and manages work with six‑month roadmaps, a weekly sync with product, and a buffer for urgent bugs. Performance metrics combine PRs, PR reviews (goal: review >=2x submitted PRs), community support, internal support and public media. Team practices include chapter-based grouping, daily 30–45 minute social slots, regional meetups 2–3 times a year, and career goals tied to committer/PMC progression.
AI-written summary · about
chapters (11)
- 0:00Introduction to OSPO challenges
- 1:58OSPO team structure overview
- 3:22Upstream-focused OSPO at Ivan
- 4:44Distributed team management
- 6:51Team separation challenges
- 9:42Four pillars of OSPO management
- 10:24Building team culture
- 12:34Roadmapping and planning
- 14:43Measuring OSPO performance
- 17:34Career growth for OSPO developers
- 19:18Summary and Q&A
related talks
42mDoes Your OSPO Help or Hinder Contributions?
39mExtrospective OSPOs: Working on 3rd Party OSS
26mNavigating Open Source: Establishing an OSPO for Organizational Success
01h 39mWorkshop: Building and Managing an Open Source Program Office
32mOSPOs: Key Lever for Open Source Sustainability
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
45mPanel Discussion: Bring Your Product Manager to the Open Source Party