Lightning Talk: Strategies for Inclusivity as an Open Source Project Maintainer
summary
Advocates lowering the barrier to entry for Hyperledger Cactus by adding tiny how‑to clues and linking beginner docs, claiming that clearer onboarding increases contributions and code quality. Recommends first-in-first-out PR review and first-in-first-out responses on chat/issues as default policies so merge conflicts land on later submitters, not unaware first contributors, and suggests merging out of order only for concrete technical reasons; shows a two‑PR timeline and urges basing new branches on open PRs.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:25Why inclusivity
- 1:05Barrier to entry
- 1:45Documentation
- 2:29Requests
- 3:29Why is it important
- 4:12Example
- 5:20Communication channels
- 5:40Conclusion
related talks
39mCreating an Inclusive Community
44mBuilding On-Ramps for Non-Code Contributors in Open Source
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..
23mKeeping Your Open Source Project Accessible to All
26mOpen Source Inclusivity: Empowering Newcomers
13mOpen Web, Open Source, Open Communities
42mBuilding On-Ramps for Non-Code Contributors in Open Source
05mLightning talk from Devon Lindsey