Panel Discussion: Build a Community, Not a Framework
summary
Shows a pragmatic playbook: create a chat (Discord) and open office hours to turn lurkers into contributors, use Orbit plus npm download stats to track engagement, and push clear, actionable next steps (exact file path, required unit test, ask for a PR). Examples: Fastify’s community-first funnel, WebDriver’s Discord support, shipping fetch to Node over a few years, and jump‑starting translations via Crowdin and Fiverr (~$800 to seed three languages).
AI-written summary · about
chapters (21)
- 0:00Panelists and roles
- 1:29Defining community and its importance
- 3:58Open governance goals
- 5:46Security and sustainability
- 6:51Cross-project collaboration
- 8:41Community building strategies
- 11:11Expectations for contributors
- 14:25Incentives beyond code
- 15:08Contribution stages
- 18:43Measuring engagement
- 20:07Chat systems for support
- 21:31Corporate vs open projects
- 23:21Growth versus product balance
- 25:27Joining open source
- 26:52Self-selection in engagement
- 27:57Diverse contributions
- 28:42Mental health in maintenance
- 31:55Prioritizing features
- 34:24Engaging quiet voices
- 38:44Connecting groups
- 39:26Ways to get involved
related talks
26mBuilding Open Source Communities
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why
17mScaling Community, Code, Contributors
28mBuilding Open Source Communities
24mCommunity - catch them all
15mThe Open Source Community Core
49mCommunities Over Code: How to Build a Successful Project
17mBuilding Open Source Communities with Tierney Cyren