Conducting Your Open Source Project
summary
Compares open-source governance to community music with concrete takeaways: use Postgres‑style strict documentation and house rules, appoint librarians/stage managers to free contributors for core work, and use a flip the commit bit policy after private back‑channel engagement for poisonous members; cites a 37‑year band and a staged production of Stravinsky and Walton done two years ago by volunteers as proof that big technical projects can be funded by pick two: money experience prestige and succeed when leaders make quick decisions and enforce a code of conduct.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:19Self-Governing Organizations
- 18:01How To Get Rid of Poisonous Members
- 23:45How Do You Get People To Do Things
- 25:08Art of Asking
- 33:00Be Willing To Be Wrong
- 39:32Be Connected
- 41:04Questions
related talks
49mCommunities Over Code: How to Build a Successful Project
23mGood Governance Practices for Healthy Open Source Projects
30mHow to Drive Consensus & Transparency in OpenSource Communities
28mBuilding Open Source Communities
15mLessons Learned from Cultivating Open Source Projects and Communities
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
25mLessons Learned from Cultivating Open Source Projects and Communities
51mBuilding Strong and Sustainable Open Source Projects