After years of mentoring, Kelvin has noticed that a first merged PR is not a reliable predictor of who becomes a long-term contributor. The difference, he says, is rarely about technical skill alone.
“Consistency, the ability to learn quickly from mistakes, and persistence make all the difference.”
He has watched contributors whose PRs were closed because the project changed direction. Others waited weeks for a review or had to rethink their approach entirely after detailed feedback. The ones who kept going, he says, learned to ask better questions and focused their energy on what the project actually needed.
Beyond writing code, Kelvin encourages new contributors to become active in the communities around their projects. Specifically, he points to joining Slack and Discord channels, attending project meetings, reading open pull requests, and engaging with maintainers as small actions that build trust over time.
Enigbe adds that reviewing other people’s pull requests is one of the most underrated growth tools available to new contributors. Code review lets developers explore unfamiliar parts of a codebase, see different engineering decisions, and offer feedback that moves the project forward. In short, meaningful contribution is not only about the PRs you merge yourself.