Building Open Source Communities with Tierney Cyren
summary
Lessons from Node.js, io.js, Tent and MyBB condense into concrete rules: a single small PR to fix markdown links grows into a long‑term contributor and a job; io.js forks and then Node.js/io.js merge shows governance scaling; Tent’s insistence on owning the protocol kills community; MyBB’s dozens of empty forums prove too much structure looks dead. Use GitHub as the reliable canonical channel, keep processes minimal, create clear contribution paths, empower contributors and avoid ownership that burns out stewards.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:38OPEN SOURCE COMMUNITY IS EVERYTHING BEYOND THE CODE.
- 1:31SO, HOW DOES ONE BUILD AN OPEN SOURCE COMMUNITY?
- 2:02LESSONS LEARNED FROM BUILDING OPEN SOURCE COMMUNITIES
- 5:42TOO MUCH RED TAPE LIMITS GROWTH
- 7:16EMPOWERING CONTRIBUTORS TO DO THE WORK THEY WANT TO DO ENABLES NATURAL GROWTH
- 8:53COMMUNITIES CAN OUTGROW THEIR LEADERS.
- 10:47TAKE MULTIPLE APPROACHES TO COMMUNICATION
- 14:10BE A ENABLER, NOT A DRIVER.
related talks
26mBuilding Open Source Communities
28mBuilding Open Source Communities
36mThe Feedback Loop: Growing healthy open source projects
25mLessons Learned from Cultivating Open Source Projects and Communities
15mLessons Learned from Cultivating Open Source Projects and Communities
25mLessons Learned from Cultivating Open Source Projects and Communities
40mPanel Discussion: Build a Community, Not a Framework
28mGrowing Open Source Seeds