Community - catch them all
summary
Practical playbook: start with unconferences and meetups before aiming for a larger CFP at a big conference (DevWorld draws 7,500 engineers), run hackathons for hands‑on mentoring, and use GitHub plus Mastodon/Slack/Discord for day‑to‑day coordination. Tactics that matter: pair on pull requests to split code/tests/docs, use ADR and RFC practices to capture decisions, prioritize searchable docs over ephemeral chat, apply moderation tools to protect maintainer mental health, and measure onboarding by merged first‑time contributors.
AI-written summary · about
chapters (15)
- 0:00Community building intro
- 1:40Open source contributors
- 3:07Growth and onboarding
- 5:14Small events and meetups
- 8:28Conference talk prep
- 9:10Joining via chat
- 10:12Blogs and forums
- 11:15Core code contributions
- 14:07Documentation as the backbone of open source
- 17:19Invisible users feedback
- 18:45Managing expectations
- 20:12Small project support
- 20:55Motivation behind community involvement
- 22:02Maintainer mental health
- 22:44Closing and resources
related talks
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why
40mPanel Discussion: Build a Community, Not a Framework
15mThe Open Source Community Core
17mScaling Community, Code, Contributors
15mBuilding Tech Communities: Lessons from a Decade of Experience
28mBuilding Open Source Communities
47mThe Great Adventure of Open Source Contribution
39mKeynote Speakers