Creating an Inclusive Community
summary
Hyperledger community practices that actually change retention: keep docs current with step-by-step install and developer workflows, provide Docker/dev scripts and Makefile targets, and maintain a clear contributing guide with PR templates, labels, CI checks and good first issues 100-400. Rotate maintainers to monitor chats and mailings, acknowledge questions quickly or reply “seen will follow up,” and use a chatbot to point to docs. Run open agendas and co‑created events (open space), call new attendees to introduce themselves, and merge or rebase promptly so contributors don’t disappear.
AI-written summary · about
chapters (17)
- 0:00Inclusive communities welcome
- 3:57Retention and inclusion
- 4:18Documentation for inclusion
- 7:10Reducing unanswered questions
- 10:22User journeys tailored
- 11:04Encouraging meeting participation
- 14:12Broader contribution opening
- 16:01Contribution paths clarified
- 17:24Developer workflows simplified
- 18:06Transparent architecture design
- 19:52Maintainer etiquette
- 23:02Handling conflicts honestly
- 24:51Good first issues
- 26:36Inclusive practices tips
- 31:02Recognizing all contributions
- 33:36Inclusive events and unconferences
- 37:33Closing remarks
related talks
07mLightning Talk: Strategies for Inclusivity as an Open Source Project Maintainer
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..
18mScaling Communities to be more Inclusive
45mHow to Create a Sustainable Community
26mUnlocking Open Source Communities Potential: Community Handbook Best Practices to Foster Inclusivity
33mExpanding the Contributor Pipeline Through Inclusion
17mScaling Communities to be more Inclusive
17mScaling Communities to Be More Inclusive