Login

r/gsoc_2027

▲ 55 r/gsoc_2027+6 crossposts

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:

  1. Contributor picks a random issue filed by some user. It never gets reviewed.

  2. Contributor skips CONTRIBUTING.md. PR gets rejected for process, not code.

  3. Contributor uses AI to write the fix. Can't answer a single question during review. PR dies.

  4. 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.

u/Junior_Bake5120 — 2 days ago
▲ 2 r/gsoc_2027+1 crossposts

Need Guidance Regarding Best Roadmap for GSoC 2027 (DSA + Full Stack + Open Source Confusion)

Hello senior, I am Mahesh.

I needed some genuine guidance regarding my roadmap for GSoC 2027 because currently I’m confused between two paths and don’t want to waste time in the wrong direction.

Right now DSA is going on in my batch and I’ve completed around 40%. Most probably by June end, DSA will be completed.

After that, from July to around November, our Full Stack/Web Development course will run, where the complete MERN stack along with major projects, mini projects, and assignments will be covered.

My main confusion is between these 2 paths:

OPTION 1:
Continue DSA till June while simultaneously learning some additional skill outside normal MERN which is useful for GSoC/open source, like:

  • Linux
  • Git/GitHub
  • Docker
  • DevOps
  • CI/CD
  • TypeScript
  • Testing etc.

Then from July–November complete Full Stack properly, and after November start serious open-source contributions.

OR

OPTION 2:
Continue DSA and directly start contributing to C++ based organizations from now itself since my DSA language is C++ and many GSoC orgs also use C/C++ heavily.

Then alongside contributions, complete Full Stack from July–November and later decide whether to continue more in C++ or shift towards Full Stack contributions.

Another reason for confusion is:
sometimes I feel maybe I should start Full Stack from now itself because I fear getting late. But if I already study MERN now, then again the same things will repeat in the course from July–November, which may waste a lot of time unnecessarily.

So instead of repeating Full Stack twice, I was thinking whether it’s smarter to:

  • either learn additional skills outside MERN, OR
  • start real C++ open-source contributions from now.

So I wanted your honest guidance on which path is strategically better for GSoC 2027, gives better long-term value, avoids unnecessary time waste, and realistically increases my chances more.

reddit.com
u/mahesh_roy22 — 4 days ago
▲ 4 r/gsoc_2027

Next choice for open source orgs

Hi, I prepared for gsoc'26 with OpenAstronomy over the last months & did my best, yet got rejected for unknown reasons, mostly as my proposal

I'm going to be completely free starting from this July this year. I'm about to decide soon whether to get back on track and keep contributing to OpenAstronomy, or totally ditch it to explore another org and decide to delve into its projects (kubeflow, blender, KDE, etc ...), for GSoC 2027

What's your advice ?!

reddit.com
u/Omar0xPy — 4 days ago
▲ 88 r/gsoc_2027+1 crossposts

If you’re starting with open source, read the CI config before you trust the README

I mentor for Jenkins under GSoC. Every cycle I watch contributors go through the same sequence: find an issue, fork the repo, spend 3 hours trying to build it locally, give up.

The README says “run npm install.” Actual build needs three system deps nobody documented. Or the project switched from yarn to pnpm six months ago and the docs never caught up.

One thing that saves a lot of time: read the CI config first. Look at the GitHub Actions workflow or the Jenkinsfile. CI has to work (nothing merges otherwise), so it’s the real source of truth. You’ll find the right Node version, the system packages, the env vars, everything.

A few other things I wish contributors knew before their first PR:

  • Pick issues filed by maintainers or org members, not random users. Issues from outside users often get closed without review.
  • Read CONTRIBUTING.md before writing a single line of code. Half of rejected PRs fail on process (wrong branch, missing sign-off), not code quality.
  • Writing tests is a great first contribution. Lower risk than a bug fix, teaches you the codebase, and maintainers appreciate it.
  • After your PR merges, don’t disappear. Your second contribution is what turns you from “random contributor” into someone maintainers recognize.

I also built a set of open source tools that automate the research side of this (reading docs, tracing code, checking repo eligibility). Free, works with most AI coding tools: https://github.com/chiruu12/OSS-Skills?ref=devindia

But even without any tools, the CI config trick alone will save you hours.

u/Junior_Bake5120 — 6 days ago
▲ 5 r/gsoc_2027

Advice needed complete beginner!

I’ll be starting college this fall and recently went down a rabbit hole reading about open source, GSoC, people getting internships/jobs through OSS contributions, etc. It genuinely feels like something I’d love doing.

The thing is, I’m starting from almost zero. The only proper thing I’ve done till now is Harvard’s CS50P course, so I know basic Python and programming fundamentals, but that’s about it. No web dev, no DSA, no projects, nothing else yet.

My main goal right now is to crack GSoC in the first year itself. I know it’s ambitious and maybe unrealistic, but that’s what I want to work towards. If it doesn’t happen, I’ll try again in the second year, but the first year is the primary target.

What I’m confused about is the direction. There’s too much advice online and everyone says different things.

In the college I am probably headed towards they will teach C in sem 1 and C++ in sem 2.

What should I actually learn first?

Should I go deeper into Python or start learning a stack like web dev?

Which tech stacks are most useful for beginners trying to get into open source/GSoC?

How do people even start contributing when most repos look impossible to understand?

Should I focus on DSA too or mostly projects + OSS?

Any beginner-friendly orgs/projects you’d recommend?

Would appreciate honest advice, especially from people who started from scratch like this. I don’t mind grinding hard, I just don’t want to waste months learning random stuff without a roadmap.

reddit.com
u/Weak-Name-2067 — 8 days ago
▲ 14 r/gsoc_2027

How should I prepare from now for Google Summer of Code (GSoC) in 2nd year?

​

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!

reddit.com
u/codingbouy — 12 days ago
▲ 8 r/gsoc_2027

Not sure to participate in GSoC 2027

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.

reddit.com
u/RustyLegend01 — 10 days ago
▲ 3 r/gsoc_2027

Need advice and tips regarding gsoc 2027

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

reddit.com
u/Pristine_Respond_558 — 14 days ago