abhishek

Menu

Close

How I Cracked Google Summer of Code 2024 in 3 Months (My Story + Advice)

A personal journey on how I cracked Google Summer of Code in 3 months, along with tips and advice for aspiring participants.

Back

#How I Cracked Google Summer of Code 2024 in 3 Months (My Story + Advice)

This article shares my journey of cracking Google Summer of Code (GSoC) in 2024. I'll walk you through the various steps that led to my success.

#About Google Summer of Code

Google Summer of Code is an annual program sponsored by Google, allowing students to work on open-source projects. Google provides a stipend, which varies based on project size and country of residence. Project options include:

  1. Small (~90 hours)
  2. Medium (~175 hours)
  3. Large (~350 hours)

#My Story

I began contributing to SymPy in January. SymPy is a Python library for symbolic mathematics. The initial phase was challenging as I learned about new technologies and repository management tools. Although I knew Python, I had to familiarize myself with Object-Oriented Programming (OOP) in Python and the PEP8 style guide.

#GSoC and SymPy

#The Contribution Phase

The contribution phase is crucial in GSoC. During this period, I not only improved my Python skills but also became more comfortable with Git and GitHub. I worked on several issues, and by the end, I had 8 Pull Requests (PRs) merged. This phase helped me connect with other passionate contributors who were equally eager to make an impact.

#Writing the Proposal

Once I felt confident about my contributions, I started drafting my proposal. I chose to work on the Control module from the SymPy Ideas page. Writing a solid proposal is key to selection. Here’s what worked for me:

  1. Engage with Project Admins: Discuss your ideas and get feedback. Their insights are invaluable.
  2. Early Reviews: Get your proposal reviewed at least 1–2 weeks before the final submission deadline. This allows time for revisions.

#The Waiting Period

After submitting my proposal, there was a waiting period of about 1.5 months before results were announced. During this time, I stayed active by contributing and engaging with the community, demonstrating my commitment.

#The Result Day

On result day, I received an email confirming my selection. Seeing my name on the GSoC official website was surreal. All my hard work had paid off!

#Reflections and Tips

Reflecting on my journey, I realized that GSoC isn’t as daunting as it initially seemed. It requires dedication, a willingness to learn, and consistent contributions. Here are some final tips:

  1. Start Early: Begin contributing as soon as possible to get a feel for the project and its community.
  2. Engage with Mentors: Build rapport with your mentors and project admins; their guidance is essential.
  3. Be Consistent: Regular contributions show commitment.
  4. Stay Curious: Always be eager to learn and improve.

I hope my story inspires you to pursue GSoC. Remember, with dedication and passion, you can achieve anything. Good luck! 👍


If you found this article helpful, please share it with others who might benefit. Don’t forget to clap and follow for more insights on coding and open-source contributions.

#Tags

  • Google Summer of Code
  • GSoC2024
  • Open Source

Written by

Abhishek Kumar

At

Thu Jul 11 2024