Hacktoberfest Recap

What is Hacktoberfest?

Hacktoberfest is an annual event that encourages open-source contributions on platforms like GitHub by submitting four pull requests. It's a valuable opportunity for collaborative coding and gaining experience.

How to contribute to Hacktoberfest?

Finding the right project can be challenging, but there are several approaches:

1. Hacktoberfest Topic and Tag: Explore GitHub's Hacktoberfest topic to find repositories tagged with Hacktoberfest. Also to narrow down your search, combine filtering issues tagged with hacktoberfest label along with targeting specific programming languages like this. Bear in mind, repos and issues tagged with hacktoberfest are highly competitive.

2. Good First Issue: Look for issues labelled good first issue. A good first issue is a label in open-source projects, on GitHub, highlighting beginner-friendly tasks. These issues are simple, well-documented, and ideal for newcomers to gain experience and contribute positively to the project.

3. Documentation: Consider projects labelled documentation for tasks like improving comments and README files.

Additional tips include checking for actively maintained repositories, focusing on issues with few comments and not assigned to anyone, by adding sorting filters like least commented and no assignees during an issue search and starting with small tasks. When you find an issue, request the owner's approval and, if granted, follow these steps:

• Fork the repository.
• Clone it to your local machine.
• Create a branch for the issue.
• Complete the work and push it.
• Submit a pull request.

While the review process often goes smoothly, be prepared for potential adjustments or requests to revert changes.

Shoutout to @yousefmajidi for inspiring me to write this content, based on his blog post.

My experience

As the last autumn leaves fall and the final days of October approach, I find myself reflecting on a transformative journey I embarked on this past month – my inaugural experience with Hacktoberfest. It's a tale of discovery, collaboration, and the profound benefits of contributing to open source.

I kicked off my Hacktoberfest adventure with the enthusiasm of a newcomer, much like the way a child approaches a new playground, full of curiosity and wonder. The premise was simple yet intriguing: contribute a minimum of four valid pull requests to open-source repositories during the month of October. What would this journey teach me? How would it impact my perspective on the open-source world?

What unfolded was an eye-opening revelation of the beauty that lies within the open-source community. My first PR felt like dipping my toes into the waters of a vast and welcoming ocean. I had joined a global community of developers, united by a shared love for coding and collaboration. It was more than just submitting code; it was a collective effort to enhance and improve software used by individuals, organizations, and even other developers like me.

Each blog I wrote for my four PRs became a chronicle of growth, a testament to the progress I made in the open-source realm. But it wasn't just about writing code; it was about grasping the open-source philosophy. You can find my blogs for those 4 PRs here:

• PR 1
• PR 2
• PR 3
• PR 4

The Benefits of Contributing to Open Source

Contributing to open source is akin to planting seeds of knowledge, which, in turn, bloom into a garden of wisdom. Here are some reflections on the benefits:

1. A Global Network of Learners and Mentors: Open source welcomes both the novice and the expert. It's a space where learners become mentors and mentors continue learning. The community nurtures an environment where knowledge is shared freely.

2. Building a Strong Portfolio: Each contribution is a testament to your skills and dedication. It's a dynamic portfolio that speaks volumes about your expertise.

3. Collaboration and Problem Solving: Open source is a training ground for collaboration and problem-solving. It's a real-world application of coding skills, where you work with diverse minds to tackle real issues.

4. Giving Back: Contributing is a way to give back to the community that has empowered us. It's a conscious effort to make the digital world better for everyone.

5. Building Confidence: Stepping into the open-source arena and successfully addressing issues boosts your confidence. You realize you're part of something bigger than yourself.

Embracing the Open-Source Philosophy

What sets Hacktoberfest and open source apart is not just the technical contributions but the philosophical shift it encourages. It's about being part of a community that believes in sharing, learning, and making the digital world more accessible and robust for all. It's about being a part of something greater than ourselves.

So, as my first Hacktoberfest draws to a close, I encourage you to take a leap of faith and dive into the open-source world. Embrace the philosophy that every line of code is a drop in the vast ocean of collaboration and innovation. The journey may start with a simple pull request, but it could lead to a lifetime of growth, connection, and making a difference. Join me in celebrating the open-source spirit and see where your own journey takes you. It's a path worth exploring and sharing with the world.

Comments

[Jo]

Soham, did you find that it was easy to find first-issues? Cause it actually was relatively hard for me, as a lot of people had already been through and picked a lot of the problems I could actually solve to the bone. I am going to work on some docs for my last two, but it was sort of sad that I couldn't find myself contributing more.

Just gave me a better milestone to try and reach in the future =)

[Soham Thaker]

@jodoesgit It worked for me for a couple of PRs but not so much for rest 2. What I’d suggest is adding a filter for “good first issue” along with filtering based on recently updated, least commented and assigned to none issues. This is a perfect combination to find good first issue to work on!

Besides, don’t solely rely on good-first-issue! This label could be misleading at times. Try different labels and sometimes just play with the project itself if it’s a project you’re super interested in and you might find a bug which you can file and get it assigned to yourself. Another good label you can try is “bug” since the work is already done, you’re just fixing a bug instead of implementing entire feature.

Good Luck!

[Jo]

Oh those are good tips. I'll use the to route around like a truffle pig and try to find some diamonds. I really appreciate these articles, because I'm still a beginner and this really helps decode some of the process. Likewise, it helps when you see people functioning at all levels. Versus just info-dumping you hard. It's actually tough for me to decode things like that.

Following you on git, happy to see what else you do on your journey =)!