My Journey to Google Summer of Code (GSoC) 2026

Being selected for Google Summer of Code (GSoC) is a significant milestone, but it is only the beginning... and OSS culture is what matters the most.

In this guide, I'll share the some important resources links, philosophy, timeline, and actionable steps that helped me navigate my GSoC journey successfully.

A lot of content for this blog is taken from my utube video. (A 30 min long PPT of me yapping stuff).

The Core Philosophy

Before starting, it is important to understand why you want to participate in GSoC.

GSoC is fundamentally about contributing to open source, learning, and mentorship. It should not be treated as just a certificate, a resume tag, or a way to earn money.

Avoid AI Shortcuts

AI tools are incredibly powerful, but using them simply to bypass learning can hurt you in the long run.

If you use AI to generate code without understanding it, you may eventually get stuck when your mentors ask you to explain your implementation or when something breaks.

More importantly, mentors can usually tell when a contributor does not understand their own work.

Use AI as a learning and productivity tool, not as a replacement for understanding.

Stay Curious

You don't need to be an expert before contributing to open source.

One of the best parts of the process is that you learn while contributing.

Don't wait until you feel completely ready. Start exploring projects, reading code, fixing small issues, and asking questions. Your understanding will grow naturally as you work with the community.

Understanding Open Source and GSoC

A huge part of modern technology is built on open-source software.

Projects such as Linux, Kubernetes, and Docker are great examples of how open-source communities can build software used by millions of people.

GSoC provides a structured way for developers to get involved with these communities.

What is GSoC?

Google Summer of Code is a Google-sponsored program that connects developers with established open-source organizations.

Contributors work with mentors on real-world open-source projects over several months.

The program provides:

• Mentorship
• Real-world development experience
• Networking opportunities
• Exposure to open-source communities
• A stipend for accepted contributors

But the biggest benefit, in my opinion, is getting the opportunity to work on software that is actually used by other people.

The Roadmap (Kind of maybe ? , idk..)

If you're planning to apply for GSoC, I would recommend thinking about the process in phases.

Phase 1: Research

Start researching organizations well before the application period.

One useful resource is gsocorganizations.dev, where you can explore organizations that have participated in GSoC.

Look for organizations that have participated consistently over the last 2 to 3 years.

More importantly, don't just look at the organization name.

Look at:

• The technologies they use
• Their previous GSoC projects
• Their repositories
• Their contribution guidelines
• Their communication channels
• The kind of projects they usually accept

Try to find an organization where you are genuinely interested in the technology and problem space.

Phase 2: Community Engagement

Once you have identified an organization, join their communication channels.

This could be Discord, Slack, mailing lists, forums, or other community platforms.

And there is one extremely important rule:

READ FIRST.

Before asking a question, check:

• Documentation
• README files
• FAQs
• Contribution guidelines
• Code of conduct
• Existing discussions
• Previous issues and pull requests

You should make an effort to find the answer yourself before asking a mentor.

This is not about avoiding questions. Good questions are extremely valuable.

The difference is between:

"How do I set this up?"

and

"I tried X and Y based on the documentation, but I'm getting Z. I think the issue might be related to A. Am I missing something?"

The second question shows that you have already tried to solve the problem.

Also remember that your interactions with the community matter. Mentors are not only looking at your code. They also see how you communicate, solve problems, and help other contributors.

Phase 3: Deep Contribution

This is where you start becoming a real contributor rather than just an applicant.

Make actual contributions to the project.

This could mean:

• Fixing bugs
• Improving documentation
• Adding features
• Writing tests
• Reviewing code
• Helping other contributors

Don't focus on producing a huge number of pull requests.

Quality matters more than quantity.

At Liquid Galaxy, for example, the contribution process involved working through a series of tasks and gradually demonstrating my understanding of the project.

The goal is to show the community that you can:

1. Understand an existing codebase
2. Work with the project's development practices
3. Communicate effectively
4. Solve technical problems
5. Take ownership of your work

By the time applications open, you want the mentors to already know who you are and what you can contribute.

Phase 4: The Proposal

Once you reach the proposal stage, focus on making your proposal clear, realistic, and technically detailed.

Follow the organization's proposal template if they provide one.

A good proposal should make it easy for mentors to understand:

• What problem you are solving
• Why it matters
• How you plan to solve it
• What technologies you will use
• What milestones you plan to achieve
• How you will measure progress

Submit Early

This is one of the most important pieces of advice I can give.

Don't wait until the deadline to submit your proposal.

Prepare a draft early and share it with your mentors.

This gives you time to:

• Get feedback
• Fix technical mistakes
• Improve your project scope
• Clarify milestones
• Iterate on the proposal

Your first proposal probably won't be perfect.

That's completely fine.

The goal is to improve it through feedback.

What If You Aren't Ready for GSoC?

Missing GSoC does not mean you should stop contributing to open source.

There are plenty of other ways to get started.

Hacktoberfest

Hacktoberfest is a great opportunity to start contributing to open source, especially if you are completely new to the ecosystem.

October can be a good time to challenge yourself to make your first few meaningful contributions.

Other Programs

You can also explore other programs and communities, such as:

• European Summer of Code
• GirlScript Summer of Code

Don't restrict yourself to a single program.

Check this out https://github.com/deepanshu1422/List-Of-Open-Source-Internships-Programs

It has almost entire list of oss programs and mentorships. Credits to Deepanshu Udhwani for this <3

The real goal is to become a contributor.

Final Advice

If I had to summarize the entire GSoC journey in a few points, they would be:

Be consistent.

Be genuine.

Be curious.

Be kind to the community.

Help other people whenever you can.

And most importantly, don't focus only on getting selected.

Build your identity within the community.

Contribute even when there is no application deadline.

Learn even when nobody is evaluating you.

Help people even when there is nothing to gain from it.

Because at the end of the day, GSoC is not just about the result. It is about the journey and the work you do along the way.

As always , here's an ASCII art: meaowoo