Does Your OSPO Help or Hinder Contributions?
Talkat Open Source Summit North America 2022 · on Tuesday, 2022-06-21· at 14:05· Room 301/302 (Level 3), JW Marriott Austin, 110 E 2nd Street Austin, TX 78701·
summary
Practical checklist for an OSPO that helps rather than blocks: align contributions to business goals and pick strategic projects (currently 18 VMware-originated projects plus 14 third-party get focused attention), enforce strict license compliance for shipped code but keep contribution approvals lightweight (often a one-day approval), push patches upstream to avoid maintenance debt, measure project health with Augur/CHAOSS and Grimoire Lab or GitHub API dashboards, provide contributor onboarding, mentoring, conference support, and prefer small iterative PRs over surprise large dumps.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:21Project Health Metrics
- 8:16Creating Ospo Policies and Procedures
- 14:01Creating New Open Source Projects
- 18:25Open Source Communities
- 22:31Start with Something Small as a First Contribution
- 29:19Upstreaming Your Patches
- 30:27Maintenance Expectations
- 31:25Resources
- 37:11Is There Anything Unique to an Ispo
- 38:17Value Statements
related talks
32mOSPOs: Key Lever for Open Source Sustainability
37mYour OSPO’s Role in Ensuring Long-Term Business Viability
42mAlignment of Community Contributions and Business Goals - How Can Your OSPO Help?
20mManaging In The Open, Managing Contributions: The challenges of OSPO developers management
39mHow Can Your OSPO Maximize Open Source Business Value for the Organization?
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
39mOSPOs in Energy, Transport, Automotive & Public Sector
21mHow Can Your OSPO Ensure Viability of the Open Source Projects That Your Product Reli...