You have been using a small library for months. You found a confusing sentence in its documentation, or a missing check, and you know exactly how to fix it. The fix would take twenty minutes.
You have not opened the pull request, and it has been three weeks.
The fear is specific. Strangers will read your code in public, under your real name, and some of them maintain software used by millions of people. What if the change is naive? What if the reply is curt?
Here is what it actually looks like from the other side. Most maintainers are a handful of tired volunteers who would be delighted if somebody else fixed the confusing sentence. A small, careful contribution is a gift to them, not an imposition.
Make it easy to say yes. Read the contributing guide before you touch anything. Look at five recently merged pull requests to learn how the project likes changes to look, how they write commit messages, whether they want tests. If your change is bigger than a few lines, open an issue first and ask whether it is wanted. That one step saves you from the most painful outcome, which is a week of work on something the maintainers had already decided against.
Start smaller than you think you need to. Documentation fixes, a clearer error message, a missing test. These are real contributions, and they teach you the project's habits without any pressure on the hard parts.
Then expect the review to be brief. A maintainer who writes please rename this and add a test is not annoyed with you. They are being efficient because they have forty other things open. Make the change, say thanks, push again.
Some contributions will be closed. Sometimes the project is going a different direction, sometimes nobody has time. A closed pull request is a decision about the project, not a verdict on you.
What you get from the first merged change is out of all proportion to its size. You will have shipped code into a codebase you do not work for, past reviewers who owed you nothing. That quietly changes how you see every other codebase you touch.
Monday: pick the smallest thing that has annoyed you in a tool you use, and read its contributing guide.
– Asael Shinder
