Inclusive contribution Guidelines for Open Source Projects
summary
Contribution guidelines often read as too technical, omit a clear step‑by‑step from clone to merged PR, and assume knowledge of frameworks and dependencies so a beginner spends two weeks stuck or gives up; recommended fixes include translate docs into multiple languages, add short screencasts showing setup and pull‑request flow, publish an explicit dependency list and a named contact for help, and add a code of conduct plus labels/repositories for designers and docs so projects like Layer5 and Chaos stay welcoming.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:30What are contribution guidelines
- 1:13Common mistakes in contribution guidelines
- 5:50My experience as a beginner
- 9:18Why should we improve contribution guidelines
- 16:47Building a bridge
- 21:32Conclusion
related talks
24mSo You Want to Contribute to Open Source: ...
23mKeeping Your Open Source Project Accessible to All
18mOpen Open Source
33mIncluding People
42mBuilding On-Ramps for Non-Code Contributors in Open Source
27mNo Code Needed: From Emojis To Glory on the Contribution Ladder
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..
30mHow you write matters in open source