From GSoC Contributor to Mentor: My Real Playbook for Open Source

Introduction

I’ve been on both sides of Google Summer of Code (GSoC) — first as a contributor (mentee), and now as a mentor at AnkiDroid.

This is not just a story.

This is the exact playbook I share with people who DM me about:

• GSoC
• Open source
• How to actually get started

What “Open Source” Really Means

Open source software is code that is publicly available.

Anyone can:

• use it
• modify it
• contribute to it

Some well-known examples:

• Android
• Linux
• VLC Media Player

For example, Android is open source. Companies like Xiaomi, Samsung, and others build their own UI and features on top of it.

That’s the power of open source — collaboration at scale.

What is GSoC?

Google Summer of Code (GSoC) is a global open-source program run by Google.

• Duration: ~3 months
• Organizations: ~180–200 selected each year
• Each org publishes 5–7 project ideas

Project sizes:

• Small (~90 hours)
• Medium (~175 hours)
• Large (~350 hours)

As a contributor, you:

1. Choose an organization
2. Pick a project idea
3. Write a proposal
4. Work with mentors if selected

My Story: From Zero to Mentor

My journey started in October 2022 with Hacktoberfest.

That’s where I:

• made my first PR
• learned Git workflows
• understood collaboration

I’m a mobile developer (Java/Kotlin/React Native), so I searched for Android-based projects.

That’s how I found AnkiDroid.

The Struggle Phase

Setting up the project locally took me almost 2 weeks.

That’s normal.

Big codebases are hard at first.

But I didn’t stop.

I kept:

• fixing issues
• sending PRs
• participating in discussions

Even when AnkiDroid didn’t participate in GSoC 2023, I continued contributing.

The Breakthrough

When AnkiDroid returned to GSoC, I proposed something I genuinely cared about:

Improving tablet & Chromebook experience

• mouse support
• keyboard shortcuts
• drag & drop

I got selected.

The next year, I became a mentor for the same area.

Lesson #1

Start early and stay consistent.

Months of real contributions > last-minute proposal.

How to Choose the Right Organization

Don’t overcomplicate it. Use this simple filter:

1. Tech + Interest

Pick something you actually enjoy.

2. Community Health

Look for:

• active issues
• responsive maintainers
• helpful discussions

3. GSoC History

• consistent orgs → stable mentorship
• new orgs → less competition

4. Try Two Orgs

• one primary
• one backup

First Contributions: Getting Started

Most people overthink this.

Do this instead:

1. Join community (Discord/Slack)
2. Introduce yourself
3. Build the project locally
4. Pick a small issue
5. Create a PR
6. Take feedback positively
7. Repeat

Important:
Don’t disappear to write a proposal. Talk to maintainers early.

Writing a Strong GSoC Proposal

Your proposal is everything.

Think of it as a detailed execution plan.

Must include:

1. Timeline

Break 3 months into weekly goals.

2. Clear Approach

Explain how you’ll solve the problem.

3. Why You?

Show:

• past PRs
• contributions
• relevant experience

4. Supporting Content

Add:

• diagrams
• screenshots
• code snippets

The Coding Period: How to Succeed

• Share weekly updates
• Break big tasks into small PRs
• Write tests and documentation
• Ask questions early
• Stay flexible

Pro Tips (Things I Wish I Knew Earlier)

• Start in Nov/Dec
• Use a 2-org strategy
• Hard problems = less competition (but plan carefully)
• Don’t chase stipend → focus on learning
• Use Hacktoberfest as practice

Closing Thoughts

Open source changed my career.

Not because of one program —
but because it taught me:

• how to learn in public
• how to accept feedback
• how to build for real users

GSoC is just the entry point.

If you stay consistent, you can go from: beginner → contributor → mentor

Just like I did.

Final Advice

If you're starting today:

• Join a community
• Introduce yourself
• Submit one small PR this week

That’s it.

Everything else will follow. 🚀

Originally published on Medium