Hi! I am Jessica Patel, a Bachelor of Technology student passionate about open source, technology, and writing. I love exploring new frameworks and documenting my journey, and I also enjoy travel and lifestyle experiences. This is my very first blog, and I hope it will be helpful to students like me who want to contribute to open source.

I wanted to start contributing to open-source but was unsure where to begin. Documentation seemed like the easiest way to make an impact! My tech stack includes various languages like Java, C, Python, and web development as well. Although I know Data Structures and Algorithms in Java, I initially thought contributing to code issues would be straightforward — but that’s not always the case with open-source projects. I soon realised that open-source code contributions can be much tougher than expected — different codebases, unfamiliar frameworks, and diverse coding styles make it challenging for beginners. That’s why I decided to start with documentation first.

Why Documentation Matters.

Contributing to open source is not only about coding, it also involves a lot of documentation tasks as well.

Let’s discuss a few points about it:

Improving tutorials and guides:Documentation often includes examples, usage instructions, and explanations that save time for everyone.

Maintains project quality: Small fixes like typos or formatting improvements, makes projects looks more professional.

Lowers the barriers for beginners:Lowers the barriers for beginners: Many contributors like me hesitate and get confused about where to start. Documentation makes it easier!

Starting with documentation allows you to make a meaningful contribution quickly while learning the project structure and workflow. It’s a perfect first step for beginners who want to get involved in open-source.

How I Found My First Issue

Honestly, finding my first issue was the hardest part of the journey. I remember opening GitHub repeatedly, staring at issues that either seemed too advanced or were already assigned. Every time I thought, “Okay, this one looks simple,” I would open it and realize I had no idea what they were talking about.

For days, it felt like I was just jumping between organizations, checking labels like good first issue, documentation, and beginner, yet still ending up confused. Some projects were inactive, some issues were closed, and some required knowledge I didn’t have at that time.

But I didn’t give up.

I slowly started to understand that documentation issues are the safest starting point. They don’t require advanced coding, but they teach you how the project is structured — and they let you make a real contribution without feeling overwhelmed.

After many dead ends, closed issues, inactive organizations, confusing labels, and self-doubt, finding that one simple documentation issue felt like a big victory. It wasn’t just about fixing a typo or updating a line — it was the moment I finally entered open-source.

How did I make my first PR?

Making my first pull request was a big step. After finding a simple documentation issue, I took the time to understand the project's structure. It was a small contribution, but it felt like a huge achievement. This experience taught me that even small steps can lead to meaningful contributions in open-source.

I opened the repository in VS Code and started making the changes. At first, I was very aware of every little detail — spaces, formatting, even punctuation. You don’t realize how nervous you can get over something so small until it’s going to someone else’s repo!

Once I saved the changes, I committed them with a message like:
“Fixed typo in Maven documentation”. Then came the part that really made my heart race — creating the pull request.

I remember hesitating before clicking the button. “What if I did it wrong? What if they reject it? What if it breaks something?” But I took a deep breath and finally clicked Create Pull Request.

The PR page loaded, and I saw my tiny change in front of me, highlighted in green. It was my work, on a real project, in front of real contributors. That simple moment made all the earlier struggles worth it.

Waiting for My First PR to Be Merged

After creating my first PR, I thought the hardest part was over. But then came the waiting game — and honestly, it was tougher than making the changes.

I kept checking the PR page every few hours, wondering: “Did they see it? Did I do something wrong? Should I comment?” The PR hadn't been merged yet, and I started overthinking every little detail.

But then I reminded myself: waiting is normal. Open-source contributors are busy, maintainers have many things to handle, and a small documentation fix doesn’t always get immediate attention. What matters is that my contribution is out there, visible to everyone, and that I did it correctly.

Even though it hasn’t been merged yet, this PR is still a huge milestone. It’s proof that I’ve taken my first real step into open-source, that I know how to find an issue, fix it, and submit it properly. The merge will come eventually, and when it does, it’ll feel even more satisfying because I already know the journey it took to get here.

Waiting is part of the learning — and honestly, I’m already proud.

Ending my first contribution journey!

This whole experience—from searching endlessly for a beginner-friendly issue to finally creating my first PR—has been a mix of confusion, excitement, doubt, and small victories. Even though my PR hasn’t been merged yet, I’m still proud of myself for getting this far.

Open source isn’t about how big your contribution is. It’s about showing up, learning how things work, taking small steps, and believing that you can add value, even if it’s just one line in a README.

And the best part?
I know this is just the beginning.

There will be more issues, more PRs, more waiting, and hopefully soon, more merges. But this first contribution taught me something important—I can do this. I’m capable of understanding, contributing, and being a part of the open-source world.

So I’m ending this blog here, but not my journey. The next PR, the next project, and maybe even GSoC… they’re all waiting ahead.

And I’m ready.