Communities Over Code: How to Build a Successful Project
summary
Building a successful open source project requires concrete practices not platitudes: require public decision records — if it didn't happen on the mailing list it didn't happen — use a 72-hour lazy-consensus window for noncritical changes, document governance and earned-rights paths, and measure success with concrete goals like “twice as many downloads in 12 months” or “three new company contributors.” Provide infrastructure (mailing lists, CI and bug tracker, docs, translation), mentor new contributors, and track real user-driven use cases (Project Atomic discovered rpm-ostree for IoT updates).
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:46What Well Cover
- 8:25Core Principles
- 16:02Who Does Success Look Like?
- 22:44Governance Suggestions
- 30:02Face to Face
- 33:48Audience & Goals
- 36:00Project Voice and Messaging
- 40:27Blogging and Social Media
- 43:16Summary
related talks
27mHow to Grow and Mentor an Open Source Community
28mBuilding Open Source Communities
40mBoF: Positioning Your Next Open Source or Standard Project for Success
21mLeading and Growing an Open Source Comunity
01h 00mGrow and manage your open source project with a proven way - The Apache Way
23mGrowing A Successful and Sustainable Project
30mHow to Drive Consensus & Transparency in OpenSource Communities
50mRunning a Successful Open Source Project