Your first Open-Source Contribution

Is open-source intimidating? Are you nervous about your code being rejected by the maintainers? Or maybe you just don’t know where to start. Let’s talk about it. Let’s talk about the feelings. Let’s talk about the practices. Let’s get you that first open-source PR.

Is open-source intimidating? Are you nervous about your code being rejected by the maintainers? Or maybe you just don’t know where to start. I’ve contributed to Rails, Forem, Ruby for Good, and Hacktoberfest. I’ve had PRs wait, be rejected, and merge before the tests passed. I know those nerves well. Let’s talk about it. Let’s talk about the feelings. Let’s talk about the practices. Let’s get you that first open-source PR.

There have been many talks by many people about making your first open-source contribution. They usually cover the same topics: find something tagged “good first issue”, read the README.md, read the CONTRIBUTING.md, open the forked repo, and submit a PR against the main repo. None of this information is new or novel, but if we gain 2 new open-source devs every time this talk is given, then it’s worth it. Many RubyConf attendees leave with a new passion for open-source, but don’t have the knowledge and confidence to act on it. The next core maintainer is in your audience waiting to be inspired, and I want to give them the push they need to enter the water.

As a maintainer, I want to reassure early developers that their PRs are welcome and coach them on being as impactful as possible. I’ve contributed to Rails, Forem, Ruby for Good, Hacktoberfest, and maintain several open-source projects of my own. I’ve had PRs wait, be rejected, and merge before the tests passed. I’ve coached others through their first PRs, both individually and on my livestream. I want to share all that experience with new developers and make open-source a place for everyone.