The art of building and sustaining successful OSS tools and infrastructure
summary
Argues that project success depends on concrete buyable outcomes not lofty topics: 15 years of experience, concrete examples with package tools like pip, conda, pipx show fragmentation in the packaging ecosystem and real user pain. Emphasizes measurable design claims — first aha moment, small composable APIs that follow do one thing and do it well — and concrete maintainer tradeoffs: maintain, extend, or sunset features, plus governance and discoverability decisions that either enable or block actual user workflows.
AI-written summary · about
chapters (8)
- 0:00Open source success intro
- 1:50Defining OSS success
- 7:51Traits of successful tools
- 17:12Ecosystem complexity
- 23:00Design decisions
- 30:33Usability and discoverability
- 40:12Sustainable OSS infra
- 45:19Q&A
related talks
32m"Making an open source package - lessons learned"
30mBringing Continuous Delivery to Open Source
24mAchieving the Tipping Point for Open-source Software: Making the Business Value Obvi...
28mMaking a Splash with your Open Source Project
49mCommunities Over Code: How to Build a Successful Project
15mLessons Learned from Cultivating Open Source Projects and Communities
27mDesign Your Open Source Project
36mThe Feedback Loop: Growing healthy open source projects