What Roleplaying Games Can Teach Us About Open Source Communities
summary
Claim: roleplaying classes map to concrete open source roles and that projects fail without those roles. The talk names specific mappings—mage = coder, rogue = tester/security/creative user, bards = docs and outreach, artisan = designer/front end, healer = community manager/support—and calls out GitHub contributor graphs as a misleading metric. It argues for recruiting non-coders with concrete roles, valuing documentation, QA, ops and community work, and using empathy as a practical, repeatable way to onboard contributors.
AI-written summary · about
chapters (7)
- 0:00Intro
- 4:05Open Source Contributors
- 5:23Magic Users
- 6:05Rogues
- 7:40Fighters
- 9:22Healers
- 10:38Conclusion
related talks
44mIt takes a Village - Role Diversity in Open Source
16mThere's More to Open Source than Code
13mOpen Web, Open Source, Open Communities
45mPanel Discussion: Open Source as a Second Language
30mTokenism in Open Source: Diversity or Decoration?
23mKeeping Your Open Source Project Accessible to All
26mAre we being inclusive with our community recognitions?
15mDesigning Game Communities for Kindness