Scaling Community, Code, Contributors
summary
Vivid, tactical playbook: awareness → investigation → contribution, with the concrete claim that projects must distill their message to 140 characters and give a concrete path forward (signup flows, newsletter/drip, forum links). Practical tools named: Telegram, Medium, YouTube, Discord, Twitter, GitHub and email tracking beyond Google Analytics. Examples: a hack team spent six hours researching Steam and hit a two‑week signup delay unless buying access via Ethereum, and Decred’s stepped tour directs newcomers into a working forum. Open dialogue and explicit “why” keep contributors.
AI-written summary · about
chapters (5)
related talks
40mPanel Discussion: Build a Community, Not a Framework
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why
15mThe Open Source Community Core
28mBuilding Open Source Communities
49mCommunities Over Code: How to Build a Successful Project
18mOpen communication for open development
20mOpen up to Open Source
39mKeynote Speakers