Open-source → GSoC 2027

GSoC 2027 Launch Plan

Your ~4.5-month runway to a Google Summer of Code proposal — two orgs picked, every step tracked. Tick tasks as you go; progress saves in this browser.

0% complete

0 of 0 steps done — start with Phase 0 this week.

The calendar

Today is 2 Nov 2026. GSoC 2027 dates aren't official yet — these are projected from the 2026 cycle (it barely shifts year to year).

Now · Nov ’26

You are here Build Git fluency, set up both projects, land your first PRs.

Dec–Jan

Build a track record Steady PRs on both orgs; become a name mentors recognise.

~Late Jan ’27

Orgs apply to GoogleNothing for you to do — keep contributing.

~Late Feb ’27

Accepted orgs announcedkeyConfirm OpenMRS & Talawa are in; read their project ideas.

~Mid–late Mar ’27

Proposal window your moveWrite, get mentor review, revise, submit early.

~Early May ’27

Results announcedAccepted contributors revealed.

May–Aug ’27

Coding + evaluationsBuild your project with your mentor; get paid.

Verify exact 2027 dates on the official timeline when published: developers.google.com/open-source/gsoc/timeline

Your two orgs

Go deep on these two — no more. Each link opens in a new tab.

OWASP

Web-security foundation. An umbrella in GSoC — you pick one project. Your JS/TS lane is Juice Shop; your Java lane is ZAP.

Tech you'll use

Node.jsTypeScriptAngular ExpressJava (ZAP)

Projects for your stack

juice-shop (Node/TS) zap (Java · needs a prior PR)

Start here

juice-shop repo (clone this) Free book: Pwning OWASP Juice Shop OWASP GSoC ideas Join OWASP Slack

First move: clone juice-shop, npm install && npm start, read the book, join OWASP Slack #project-juice-shop, then propose a small fix/feature before opening a PR. (No labeled issue backlog — you propose.)

Apache · Software Foundation

300+ project umbrella, very Java-heavy. Pick ONE project and go deep. Runs on dev mailing lists — no assign-bot wall. Your fastest first PR.

Tech you'll use

JavaMavenJiradev@ lists

Java projects w/ live beginner issues

apache/dubbo (~5) apache/seatunnel (~12)

Start here

700+ good-first-issues (org:apache) Apache GSoC hub Good First Issues guide Starter: dubbo #12637

First move: pick ONE Java project (Dubbo or SeaTunnel), build it locally, dev-subscribe@<project>.apache.org, grab a good-first-issue, comment to claim, then PR + discuss on the list.

Your step-by-step plan

Tap a phase to expand. Check things off — your progress is saved on this device.

What actually gets you selected

#1 factor

Be a recognised contributor

A mentor who knows your name from 5 merged PRs picks you over a stronger stranger. Familiarity beats raw skill.

Proposal

Talk to the mentor first

Ask questions, share a draft, revise it. Accepted contributors almost all say this is what got them in.

Proposal

Be specific & realistic

Clear problem → your approach → a week-by-week timeline → deliverables. Show how, not just what.

Habit

Submit early, keep editing

You can revise until the deadline. Early drafts get mentor eyes; last-minute ones don't.

Focus

Two orgs, not six

Depth reads as commitment. Spreading thin reads as shopping around.

Mindset

Momentum > perfection

Get your first PR merged in ~3 weeks. A small merged fix beats a perfect plan you never ship.