Community and Contributors Panel
summary
Covers concrete community practices: asking active users to file an issue or make a PR reliably converts helpers into contributors; docs teams grow to ~650 contributors while the whole project exceeds ~3,100 contributors; a month‑long hackathon yields 200+ submissions that are triaged via a shared spreadsheet and graded by 10–15 reviewers. Shows operational tools—Discord, GitHub labels like needs confirmation, PR templates, reviewer co‑author credit, badges—and policies—code of conduct, moderation, meetups, and support squads—that actually scale contribution and retention.
AI-written summary · about
chapters (8)
- 0:00Welcome and introductions
- 2:50Panelist backgrounds and fun facts
- 6:05Encouraging community contributions
- 15:45Hackathons and contributor events
- 18:54Building inclusive communities
- 26:11Accessible learning resources
- 32:16Support roles beyond coding
- 37:56Closing and call to action
related talks
32mDeep Dive: Contributor Experience SIG
45mOpen Source Contribution Panel
25mPanel – The Headless OpenSource Stack
34mHow to get them to Commit?
14mBeyond the First PR: Why Contributors Stay in Open Source Communities
18mOpen communication for open development
27mNo Code Needed: From Emojis To Glory on the Contribution Ladder
33mIncluding People