People have made gsoc into another filthy rat race like jee neet and earn bad reputation for real indian open source devs..gsoc is for those who are interested in contributing without expecting anything back(open source) not the most ai pr submissions contest
​
Hi seniors,
I’m currently in 2nd year(CSE). My end sem exams are going on right now, and my 3rd semester will start from July.
I want to start preparing seriously for Google Summer of Code (GSoC), but I’m confused about the proper roadmap and how people actually get selected.
I wanted to ask seniors who cracked GSoC or contributed to open source:
How should a beginner start preparing for GSoC?
What skills are most important for selection?
Which tech stacks/projects are beginner friendly?
How much Git and GitHub knowledge is required?
When should I start contributing to open source projects?
How do I choose organizations for GSoC?
What type of projects or resume helped you?
How difficult is it for a 2nd year student to get selected?
What mistakes should beginners avoid?
I really want to use my upcoming semester properly and build a strong profile in open source and development.
Any roadmap, resources, or personal experiences would help a lot.
Thanks in advance!
Hello everyone! I'm totally new to coding and I am genuinely interested in learning it. I came accross gsoc during my curious searches across Google and since it only has restrictions regarding age and not degree, I feel like I should try my hands on it. So any suggestions regarding whether I should learn python or javascript first to create my pr or contributions with is highly appreciated. Any other advice is also accepted. Thanks
I tried for GSoC 2026, but didn’t get selected. It honestly stung a bit, but it also made me realize what I was missing.
This time I’m doing things differently. I’ll be contributing regularly, making consistent PRs, staying in touch with mentors, and actually being part of the community instead of just showing up during applications.
I’m writing this so I can come back to this exact post one year from now, no matter what happens.
If I get selected, I’ll share it here.
If I don’t, I’ll still come back and talk about what I learned and how I improved.
Either way, I’m committing to the process from today.
I am an upcoming 3rd year student (with no internships), my semester will start in July. I have heard that the placements in our college start from next year in August. I am confused about whether to participate in GSoC or prepare for my placements. I do have strong knowledge in programming and started doing leetcode everyday from last month.
Can anyone suggest to me what choice to make.
Thank you.
Hey everyone, first off, congratulations & same pinch to everyone who got accepted into Google Summer of Code this year!
When I was writing my own proposal, one of the most helpful things I did was read through past accepted (and rejected) proposals to get a feel for the expected structure, timeline, and level of detail. To keep paying this forward, I have set up a central repository to archive GSoC 2026 proposals:
https://github.com/satwiksps/GSoC_archive_2026
If you applied this year, whether you were accepted or rejected, it would be a huge help to the open-source community if you could contribute your proposal.
There are also links in the README to the 2025 and 2024 archives if you are a future applicant looking for inspiration right now.
If you are planning to apply next year, feel free to star the repo so you have it bookmarked for when you need it. Let me know if you run into any issues with the PR process!
Guys my target is gsoc im going to start from the months of June
What tip will u guys give me?
Also tell me what to choose javascript or python for the gsoc org selection??
Hey everyone! I'm u/Frosty_Throat_7019, a founding moderator of r/gsoc_2027.
This is our new home for all things related to Gsoc 2027 , this subreddit will target the people who genuinely care for open-source project and don't run for money. We're excited to have you join us!
What to Post
Post anything that you think the community would find interesting, helpful, or inspiring. Feel free to share your thoughts, photos, or questions about organization coming in gsoc 2027, how can you start contributing, path for 2027.
Community Vibe
We're all about being friendly, constructive, and inclusive. Let's build a space where everyone feels comfortable sharing and connecting.
How to Get Started
Thanks for being part of the very first wave. Together, let's make r/gsoc_2027 amazing.
Hey iam a 2nd year btech student(will be in 3rd year in 2 months).my goal is gsoc 27 and all I know Is node js,express, basic html css , some basic dsa.
Made a basic API performing crud operations etc
Iam not understanding if I have to continue in this tech stack or learn completely new one and then start contributing .
Few months i had built https://github.com/S3DFX-CYBER/GSoC-Org-Finder- which runs on https://findmygsoc.vercel.app/
a free tool that helps students find GSoC orgs by language, domain, and competition level. It's been used by 244+ students
Now that 2026 results are out, I want to build features specifically for people planning their 2027 application
A few ideas I'm considering:
- Proposal analyzer — upload your draft proposal, get AI feedback comparing it against accepted 2026 proposals from the same org
- Org match quiz — answer a few questions about your skills and goals, get a ranked list of orgs that fit you
- Contribution tracker — log your pre-GSoC contributions per org as you build your profile over the year
- Mentor finder — surfaces mentor contact info and communication channels from org idea pages in one place
My questions for you'll:
Which of these would you actually use?
What's the #1 thing that made (or would make) your GSoC application process harder?
Is there something you wished existed that none of the above covers?
i know vulkan opengl and c++ ffmpeg and webdev stuff and am also familier with blender codebase
GSoC results just came out. Whether you got selected or not, if you're contributing to open source, this might help.
As a mentor and a past contributor, I see the same patterns over and over:
Contributor picks a random issue filed by some user. It never gets reviewed.
Contributor skips CONTRIBUTING.md. PR gets rejected for process, not code.
Contributor uses AI to write the fix. Can't answer a single question during review. PR dies.
Contributor doesn't understand the codebase. Patches the symptom, not the root cause.
I built [OSS-Skills](https://github.com/chiruu12/OSS-Skills) - 8 Claude Code skills that walk you through the contribution process step by step. The key difference: the AI researches, you think.
What it does:
Finds unclaimed issues filed by actual maintainers (not random users)
Checks if the repo even accepts outside contributions before you waste time
Reads CONTRIBUTING.md so you don't skip the thing that gets your PR rejected
Walks you through the codebase architecture before you touch anything
Teaches you unfamiliar tech using examples from the actual repo (not generic docs)
Won't let you submit code until you can explain what it does and why
What it doesn't do:
Write your code for you
Generate PR descriptions
Let you skip understanding the codebase
Every skill has "thinking gates" where you have to explain your understanding before moving forward. The AI gives you hints about where to look, but you have to articulate the answer.
Requires Claude Code and the GitHub CLI.
If you try it, I'd genuinely like to hear what worked and what didn't. Open an issue or drop a comment here.
For GSoC candidates who didn't get selected this round: these skills are specifically designed to help you build the kind of deep project understanding that makes GSoC proposals stand out. Contributing well > contributing fast.
I am planning to deep dive into web dev for gsoc' 27.
what's your plan?