Aligning wishes of multiple orgs into an OSS project
summary
A legal template called the Contributor Commitment Agreement and a lightweight collaboration marketplace prototype coordinate multi‑company requests for ClearlyDefined and OSS Review Toolkit, turning wishlists into funded, timeboxed commitments with procurement‑friendly language and exit penalties. The workflow matches overlapping top‑10 priorities from Bosch, Volkswagen, SAP and others, pools cash and engineer time, and lets maintainers schedule work onto a public roadmap instead of handling ad‑hoc big merges, addressing the 95% by 5% maintainer imbalance.
AI-written summary · about
chapters (13)
- 0:00Introduction and speakers
- 1:28ClearlyDefined mission
- 4:01Speaker background and projects
- 6:50Road maps in open source
- 9:57Tragedy of the commons
- 13:57Free rider problem
- 15:04Sustaining open source projects
- 17:37Contributing to features
- 20:29Contracting for open source
- 23:43Maintainer workflow challenges
- 25:06Collaboration marketplace idea
- 27:41Wish lists and road maps
- 30:30Building open source platforms
related talks
42mDoes Your OSPO Help or Hinder Contributions?
37mFund Projects and Change Company Culture with a FOSS Fund
42mAlignment of Community Contributions and Business Goals - How Can Your OSPO Help?
16mMaintaining an OSS Project (Babel)
29mLiving with Legacy: How Bosch Built an OSPO and How You Can Do It too
42mEat Your Own Dogfood - How Upstream Orientation Changed the Way We Work in Open Source Management
13mBeyond OSS
39mExtrospective OSPOs: Working on 3rd Party OSS