Becoming a Contributor
summary
Claim: anyone can help and contribution means anything that improves a project, not just code. Example: a one-word docs fix gets merged into Rust and proves access. Practical routes: file issues on GitHub/GitLab, write API docs with rustdoc and mdBook, translate, improve visual design with simple CSS or bootstrap, record podcasts or screencasts, write tutorials, or mentor. Many projects carry lots of open issues and need those concrete, fixable contributions.
AI-written summary · about
chapters (11)
- 0:00Introduction and goals
- 4:30Why you should contribute
- 6:11Defining a contributor
- 9:35Contributing through code
- 12:27Documentation contributions
- 17:36Translation efforts
- 19:14Design and usability
- 22:19Blogging and sharing
- 25:28Audio and video content
- 27:16Community engagement
- 28:33When and where to contribute
related talks
15mMaking Meaningful Contributions to Open Source Contributions
18mNavigating the Rust OSS Community
27mNo Code Needed: From Emojis To Glory on the Contribution Ladder
10mBecoming an awesome open source contributor
31mGetting Started with Open Source Contributions
35mYour First Open-Source Contribution
10mCalling all non-code contributors!
11mContributing to Open Source