💬 My first open source fix was a typo, and that's fine

When I was a student in Hyderabad, everyone around me talked about open source like it was a club. I knew nobody. No senior, no mentor, no cousin working in a big company. Just a laptop and a lot of free evenings. I looked at React and a couple of famous projects and closed the tab in under a minute. Hundreds of people had already been there, and every easy issue was taken within minutes. So I picked a small library that I was already using in a college project. I found a typo in its readme, and it took me about 3 hours to figure out how to fix it. I had to fork the repo, make a branch, and send a pull request. I didn't know any of these words. The maintainer merged it in 2 days with a thumbs up. I told my roommate like it was a job offer. After that I did 3 more fixes in the documentation before touching any code at all. Those small fixes showed me how reviews work, what a good commit message looks like, and how to reply politely. Nobody told me to read the contributing file first, and I learned that the hard way. My second pull request was closed because I hadn't followed the format they asked for. One of my pull requests sat for almost 3 weeks with no reply and I thought I had failed. Then I left a short, polite comment and the maintainer answered the next day. He was just busy. I live in Houston now and work as a developer, and I still start with the docs on a new project. If anyone wants a few beginner friendly projects to try, tell me what language you know.

The waiting part is the hardest for me. I once sent a fix and heard nothing for a month. I assumed they hated it and almost deleted my fork out of embarrassment. Then a stranger left a short comment saying thanks and merged it, with no explanation. So your advice about not taking silence personally is right, people are just busy with jobs.

Reading the contributing file first is the best advice here, and most beginners skip it. My first pull request got closed in a day because I used the wrong branch name. The maintainer was kind about it and told me where the rules were written. After that I read the whole file before writing a single line, and it never happened again.

This sounds like my path too. I spent 4 months fixing docs and typos in a Python library. I didn't touch any code in that time, but the habits I built there mattered more. Writing a clear commit message and reading a whole review thread before replying are skills that stay. If you have beginner friendly Python or Rust projects to share, I'd love a short list.