Your First Open-Source Contribution
summary
A clear playbook: find a repo you care about, read CONTRIBUTING.md, fork, reproduce the issue, then make a tiny, single-purpose change with tests and passing CI. Examples: add a three lines street_address method to Geocoder so Google Street Maps and Nominatim behave consistently, extend Rails validators, add Twitch clips to 4M, or Dockerize projects and build a Jekyll Twitch gem. Projects show scale—383 contributors on Geocoder and 97 merged PRs in one month for Ruby Events—so small wins compound.
AI-written summary · about
chapters (18)
- 0:00Open source intro
- 1:16Why contribute
- 3:26Benefits beyond money
- 5:30Learning from experts
- 6:33Portfolio with examples
- 7:59Right to repair tools
- 10:05Overcoming intimidation
- 11:27Finding first repo
- 14:15Issue types explained
- 20:06Maintainers vs contributors roles
- 21:51Why maintainers care
- 22:54Understanding contributing.md
- 23:56Working with forks
- 25:21Creating a mergeable PR
- 27:05Step-by-step first PR
- 28:48PR not merging reasons
- 30:56Small steps big growth
- 32:23Hack Day call to action
related talks
32mYour First Open-Source Contribution
13mHow to Make Your First Open Source Contribution
22mA beginner's guide to Open Source
32mContributing to Open Source: A Guide
19mMaking your voice heard: Open Source Needs You
10mDemystifying Contributing to Open Source
10mBecoming an awesome open source contributor
31mGetting Started with Open Source Contributions
