open source has a door.
git into gsoc finds the Google Summer of Code organizations that fit what you already know, the repositories where a newcomer's pull request gets merged, and the beginner issues nobody has claimed. Every answer names its source.
curl -fsSL https://raw.githubusercontent.com/anandkaranubc/git-into-gsoc/main/install.sh | bash
# then, in a new terminal:
git-into-gsoc start
irm https://raw.githubusercontent.com/anandkaranubc/git-into-gsoc/main/install.ps1 | iex
# then, in a new PowerShell window:
git-into-gsoc start
The install needs only an internet connection. If Python is missing, the installer offers uv, a free tool that brings its own. Already use uv or pipx? uv tool install git-into-gsoc installs the package from PyPI. Other ways to install.
every reason names its source.
Every season, many first-timers end up in an inactive repository, under an issue five people already claimed, or with a proposal that reads like a hundred others. The information to avoid that exists. It is just scattered. This is what one real run looks like, recorded on 2 November 2026. Hover a note to see where it points.
- A fit, not a promise
Strong, good, or partial says how well the work matches you. It never guesses your chance of being accepted.
fit · why it fits - Years and projects, from the archive
How many years an organization has taken part and how many contributors it accepted each year, read from the official archive.
years · projects - The source, every time
A reason says where it came from: the official listing, the ideas page, the organization's repositories.
evidence
- the official program site and its archive of past projects
- each organization's ideas page, read into a table
- GitHub and GitLab: pull requests, issue timelines, claims, maintainer replies
$ git-into-gsoc orgs --tech python --topics science -n 3 GSoC organizations ┏━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━┓┃ Fit ┃ Organization ┃ Why it fits ┃ Years ┃ Projects ┃┡━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━┩│ good │ MDAnalysis │ Topic: │ 7 │ '23:2 '24:3 '25:4 '26:3 ││ │ │ Science and │ │ ││ │ │ research │ │ ││ │ │ software; │ │ ││ │ │ Uses Python │ │ ││ good │ Open Science │ Topic: │ 2 │ '25:4 '26:7 ││ │ Labs │ Science and │ │ ││ │ │ research │ │ ││ │ │ software; │ │ ││ │ │ Uses Python │ │ ││ good │ OSGeo (Open │ Topic: │ 11 │ '23:7 '24:7 '25:9 '26:6 ││ │ Source │ Science and │ │ ││ │ Geospatial │ research │ │ ││ │ Foundation) │ software; │ │ ││ │ │ Uses Python │ │ │└──────┴──────────────┴──────────────┴───────┴─────────────────────────┘2027 orgs are not announced yet; showing official 2026 participants, the best predictor of who returns. Years: how many years it took part. Projects: contributor projects accepted per year ('24:5 means 5 in 2024). MDAnalysis • Topic Science and research software: topic tag 'science' on its official GSoC listing; official category 'Science and medicine' • Skill Python: tech tag 'python' on its official GSoC listing; its official GSoC tagline • 6 ideas on its 2026 ideas page; of the 6 that state a difficulty: 4 easy, 2 medium • Took part in GSoC every year 2020-2026Open Science Labs • Topic Science and research software: topic tag 'open-science' on itsofficial GSoC listing; its official GSoC description • Skill Python: tech tag 'python' on its official GSoC listing; main language of 2 of its 3 GitHub repositories pushed in the last year • 22 ideas on its 2026 ideas page(shortened here: 20 more lines in the real run)
ten steps. one contribution.
The cursor is you. Scroll, and it walks the path from first read to merged pull request, with the recorded output for each step beside it. Skip what you know. Loop when you need to. Each step links to its guide page.
-
Learn
What GSoC is, what it isn't, and where you are in the year.
Understand GSoC
programSee the real output
$ git-into-gsoc program --year 2027╭─────────────────────────── git-into-gsoc ────────────────────────────╮│ GSoC 2027 dates: estimate ││ Now: Before the program is announced ││ The best time to start. Pick orgs that participated last year, ││ contribute steadily, and treat every date as an estimate until ││ Google publishes it. ││ ││ ESTIMATE projected from official 2026 dates. Google has not ││ published this timeline yet. ││ Verify: https://developers.google.com/open-source/gsoc/timeline │╰──────────────────────────────────────────────────────────────────────╯ Timeline (medium projects) ┏━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┓┃ Date (UTC) ┃ Milestone ┃ When ┃┡━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━┩│ ~2026-12-02 ±41d │ Program Announce Date │ in 30d ││ ~2027-01-18 ±14d │ Org Applications Open │ in 77d ││ ~2027-02-02 ±14d │ Org Application Deadline │ in 92d ││ ~2027-02-17 ±14d │ Org Notification Date │ in 107d ││ ~2027-02-18 ±14d │ Accepted Orgs Announced │ in 108d ││ ~2027-03-15 ±14d │ Contributor Proposals Open │ in 133d ││ ~2027-03-30 ±14d │ Proposal Deadline │ in 148d ││ ~2027-04-20 ±14d │ Proposal Ranking Deadline │ in 169d ││ ~2027-04-28 ±14d │ Projects Announced to Orgs │ in 177d │(shortened here: 30 more lines in the real run) -
Discover
A short list of organizations, each with a reason it fits you.
Find organizations
orgsorgideasSee the real output
$ git-into-gsoc orgs --tech python --topics science -n 3 GSoC organizations ┏━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━┓┃ Fit ┃ Organization ┃ Why it fits ┃ Years ┃ Projects ┃┡━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━┩│ good │ MDAnalysis │ Topic: │ 7 │ '23:2 '24:3 '25:4 '26:3 ││ │ │ Science and │ │ ││ │ │ research │ │ ││ │ │ software; │ │ ││ │ │ Uses Python │ │ ││ good │ Open Science │ Topic: │ 2 │ '25:4 '26:7 ││ │ Labs │ Science and │ │ ││ │ │ research │ │ ││ │ │ software; │ │ ││ │ │ Uses Python │ │ ││ good │ OSGeo (Open │ Topic: │ 11 │ '23:7 '24:7 '25:9 '26:6 ││ │ Source │ Science and │ │ ││ │ Geospatial │ research │ │ ││ │ Foundation) │ software; │ │ ││ │ │ Uses Python │ │ │└──────┴──────────────┴──────────────┴───────┴─────────────────────────┘2027 orgs are not announced yet; showing official 2026 participants, the best predictor of who returns. Years: how many years it took part. Projects: contributor projects accepted per year ('24:5 means 5 in 2024). MDAnalysis • Topic Science and research software: topic tag 'science' on its official GSoC listing; official category 'Science and medicine' • Skill Python: tech tag 'python' on its official GSoC listing; its official GSoC tagline • 6 ideas on its 2026 ideas page; of the 6 that state a difficulty: 4 easy, 2 medium • Took part in GSoC every year 2020-2026Open Science Labs • Topic Science and research software: topic tag 'open-science' on itsofficial GSoC listing; its official GSoC description • Skill Python: tech tag 'python' on its official GSoC listing; main language of 2 of its 3 GitHub repositories pushed in the last year • 22 ideas on its 2026 ideas page(shortened here: 20 more lines in the real run) -
Evaluate
One or two repositories that merge newcomers' work.
Pick a repository
reposrepoSee the real output
$ git-into-gsoc repo sympy/sympy╭────────────────────── Repo health ───────────────────────╮│ sympy/sympy grade A (100/100) ││ Strong candidate. Go ahead with setup and pick an issue. │╰──────────────────────────────────────────────────────────╯ ✓ Very recent activity (0d since push) ✓ Has a CONTRIBUTING guide ✓ Has a Code of Conduct ✓ Issue/PR templates guide contributions ✓ Has GitHub Actions workflows (automatic checks) ✓ 2 open 'good first issue' issue(s) nobody is assigned to ✓ 60% of human PRs merged ✓ Merges outside contributors' PRs (57% of 40) ✓ 19 different outside author(s) merged recently ✓ Pull requests from outsiders get a human reply within ~3h (median) ✓ 56 people landed their first and only commit in the last year (168 committers in total) · 1 closed outside PR(s) landed through a maintainer's own commit (counted as merged here; GitHub shows them as closed) · Merged PRs, the team's included, land in ~5h (median) · Merged outside PRs change ~14 lines (median), so focused changes arewhat land here · GitHub found a license file but cannot tell which license it is; read it to check that the code is open sourceGetting set up • Dev container available: open in Codespaces/VS Code for a ready env • Python project (pyproject.toml) • Python project (setup.py) • Read first: https://github.com/sympy/sympy/blob/master/CONTRIBUTING.mdNext: git-into-gsoc orient sympy/sympy to see how the code is laid out, then git-into-gsoc issues --repo sympy/sympy for a free beginner issue. -
Orient
You know where a change would go and how to test it.
Get your bearings
orientSee the real output
$ git-into-gsoc orient sympy/sympy╭──────────────────────────── Orientation ─────────────────────────────╮│ sympy/sympy A computer algebra system written in pure Python ││ Languages: Python 99%, XSLT 1%, ANTLR 0%, Perl 0% | License: Other ││ | Last push: 0d ago ││ As of commit 08d67a46f2 on master │╰──────────────────────────────────────────────────────────────────────╯ Code map (purpose is a guess from the directory name) ┏━━━━━━━━━━━━━━━┳━━━━━━━┳━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━┓┃ Directory ┃ Files ┃ Mostly ┃ Purpose ┃┡━━━━━━━━━━━━━━━╇━━━━━━━╇━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━┩│ sympy │ 1601 │ .py │ source (main package) ││ doc │ 415 │ .rst │ docs ││ bin │ 28 │ .py │ tooling ││ .github │ 10 │ .yml │ tooling ││ release │ 9 │ .py │ unknown ││ .ci │ 5 │ .json │ unknown ││ data │ 3 │ (none) │ data ││ .circleci │ 1 │ .yml │ tooling ││ .devcontainer │ 1 │ .json │ unknown ││ . │ 21 │ │ project root │└───────────────┴───────┴────────┴───────────────────────┘How CI runs the tests CI is the set of checks GitHub runs on every pull request. pytest -n auto --timeout 10 --durations=50 --durations-min=5 (.github/workflows/runtests.yml) pytest -Werror -n auto (.github/workflows/runtests.yml) pytest -n auto (.github/workflows/runtests.yml) pytest -m slow --timeout 595 -n auto -v --durations=0 (.github/workflows/runtests.yml) CI uses Python 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, pypy2.7, pypy-3.11;most jobs use 3.14 (.github/workflows/runtests.yml) CI runs on these systems: ubuntu-latest Dev container present: open in Codespaces or VS Code for a ready (shortened here: 55 more lines in the real run) -
Community
Mentors recognize your name from useful questions, before you claim anything.
Introduce yourself
draft introSee the real output
$ git-into-gsoc draft intro --org SymPy╭──────────────────────────── Draft: intro ────────────────────────────╮│ In https://groups.google.com/g/sympy, once: ││ ││ Hi, I'm <name> (GitHub: <handle>). I'm new to SymPy and preparing ││ for GSoC 2027. ││ I read <CONTRIBUTING or the developer guide> and got <component> ││ running on <OS>. ││ I'm interested in <area> because <one concrete reason tied to the ││ ideas page or your own use>. ││ I'm looking at <issue URL>; before I start, <one specific question>. │╰──────────────────────────────────────────────────────────────────────╯Fill these with real observations before sending ☐ What you read or ran before writing ☐ One specific question ☐ The area you care about and whyRules, with sources General practice, from projects that wrote it down: • Post in the public channel. Never private-message someone you do notknow without asking in public first. https://google.github.io/gsocguides/student/communication-best-practices • Read the channel for a few days first; bring at least a few real questions before offering opinions.(shortened here: 6 more lines in the real run) -
Find an issue
One available, well-specified issue you can reproduce.
Choose an issue
issuesissuepointersSee the real output
$ git-into-gsoc issues --repo sympy/sympy -n 5 Beginner-friendly issues ┏━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓┃ Score ┃ Status ┃ Issue ┃┡━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩│ 96 │ available │ sympy/sympy#5315 ││ │ │ Module names are imported with from sympy ││ │ │ import * ││ │ │ SymPy ││ │ │ filed by a maintainer ││ │ │ ! open since 2011 ││ 41 │ likely taken │ sympy/sympy#11166 ││ │ │ Clean up periodic_argument ││ │ │ SymPy ││ │ │ filed by a maintainer ││ │ │ ! 6 people have asked to work on it ││ 34 │ likely taken │ sympy/sympy#6588 ││ │ │ Docstring formatting for section titles ││ │ │ SymPy ││ │ │ filed by a maintainer ││ │ │ ! open since 2012 │└───────┴──────────────┴──────────────────────────────────────────────┘ Searching sympy/sympy. Left out: issues with an assignee or a linked pull request, and ones not updated in a year, so `repo` may count more. Using this repository's own beginner label(s) 'Easy to Fix' first. Next: check the one you like before you comment: git-into-gsoc issue sympy/sympy#5315 --track -
Contribute
A focused pull request you can explain line by line.
First contribution
draft prpr-checkSee the real output
$ git-into-gsoc draft pr --repo sympy/sympy╭───────────────────────────── Draft: pr ──────────────────────────────╮│ Start from the project's own template, ││ .github/PULL_REQUEST_TEMPLATE.md, and fill in every section. Make ││ sure it covers: ││ ││ Title: <imperative, under 70 characters, in the project's style> ││ ││ Problem: <what was broken or confusing>. Fixes #<issue>. ││ Change: <what changed and why; alternatives considered; known ││ shortcomings> ││ Validation: ran `pytest -n auto --timeout 10 --durations=50 ││ --durations-min=5`; <result>. <new or updated tests> ││ Duplicates checked: <searched open PRs for ...; none found / #123 ││ differs because ...> ││ Review guidance: <where to look first; one thing I am unsure about> ││ AI disclosure: <tools used and for what, as the project's template ││ asks> ││ ││ Before you start, once: ││ git clone https://github.com/<your-github-username>/sympy.git # ││ after forking sympy/sympy on GitHub ││ cd sympy && git remote add upstream ││ https://github.com/sympy/sympy.git && git fetch upstream ││ git switch -c <short-branch-name> upstream/master ││ python3 -m venv .venv && source .venv/bin/activate # Windows: ││ .venv\Scripts\activate ││ pip install -r requirements-dev.txt # install as CI does ││ pytest -n auto --timeout 10 --durations=50 --durations-min=5 # ││ run the tests once before changing anything ││ When the change is ready: ││ git push -u origin <short-branch-name> # then open the pull ││ request against master │╰──────────────────────────────────────────────────────────────────────╯Fill these with real observations before sending ☐ Problem and issue link ☐ What changed and why ☐ Validation: commands run and results ☐ Duplicates checkedRules, with sources General practice, from projects that wrote it down: • The first line is short and imperative; the body says what changed and why, and names shortcomings. https://google.github.io/eng-practices/review/developer/cl-descriptions.html • Every pull request costs reviewer time; keep it small, one logical (shortened here: 9 more lines in the real run) -
Iterate
Every review comment answered, through to a merge or a clear no.
See it through review
draft review-replySee the real output
$ git-into-gsoc draft review-reply --repo sympy/sympy╭──────────────────────── Draft: review-reply ─────────────────────────╮│ Under each review comment: ││ ││ Done in <commit>: <what changed>. ││ or ││ I kept this as is because <reason with evidence>; happy to change it ││ if you prefer <alternative>. ││ or ││ I don't follow this one. Do you mean <reading A> or <reading B>? │╰──────────────────────────────────────────────────────────────────────╯Fill these with real observations before sending ☐ Which comment you are answering ☐ What you changed or why you did not ☐ A question if you are unsureRules, with sources General practice, from projects that wrote it down: • Reply to every review comment; do not resolve threads you did not start. https://arxiv.org/pdf/2302.05058 • When you do not understand a comment, say so and ask; do not guess or get defensive.(shortened here: 4 more lines in the real run) -
Proposal
An original draft shaped by the organization's template and feedback.
Prepare a proposal
proposalSee the real output
$ git-into-gsoc proposalChecklist☐ Follow the organization's proposal template: Missing required sectionsis a common reason proposals are rejected.☐ Link prior contributions to the org: Link your merged pull requests, issues, reviews, or docs.☐ Show community interaction: Take part in the public chat or mailing list before you submit.☐ Clear scope, milestones, and weekly plan: Say what you will deliver each week, what is optional, and what you will cut if you fall behind.☐ Respect the org's AI policy: Say how you will use AI, or not, following the organization's rules.☐ Original authorship: Write in your own voice. You must understand every claim.☐ Submit only via the official GSoC site: Emailing a proposal to a mentor is not a submission.Suggested structure 1. Synopsis: one paragraph on the problem and what you will deliver 2. Benefits to the community 3. Deliverables, and what is out of scope 4. Implementation plan with milestones 5. Week-by-week timeline, with spare time for surprises 6. Related work and design notes 7. About you: relevant experience and links to your contributions 8. How you will use AI, following the organization's policyCheck a draft: git-into-gsoc proposal draft.md --github you -
Track
A weekly log, a shortlist, and always one manageable next step.
Track progress
nextlogSee the real output
$ git-into-gsoc next╭─────────────────────────── Where you are ────────────────────────────╮│ GSoC 2027 dates: estimate ││ Now: Before the program is announced ││ The best time to start. Pick orgs that participated last year, ││ contribute steadily, and treat every date as an estimate until ││ Google publishes it. │╰──────────────────────────────────────────────────────────────────────╯Coming up 2026-12-02 Program Announce Date (estimate) in 30dDo next 1. Answer four questions so every recommendation fits you git-into-gsoc start It saves your profile, which recommendations, starter issues, and this command use. 2. Shortlist 3 organizations that fit your skills git-into-gsoc orgs --tech python # then, for each: git-into-gsoc org "NAME" --shortlist Everything downstream (repos, issues, proposal) hangs off a shortlist.Actions are suggestions from your saved progress and public data. Dates for unpublished years are estimates; verify on the official site.
four questions. two minutes.
What you know, what you would enjoy working on, how much time you have, and how much open source you have done. Press Enter to skip any of them. Then you get:
- Organizations that fit you, from the official list, each with the reasons it matched and what its ideas page offers.
- A shortlist you build by typing numbers, saved in a file on your computer.
- Your next steps with the exact commands, so you are never stuck at a blank prompt.
The terminal tool goes further than the browser version: it reads live data to tell you which repositories merge newcomers' work and which beginner issues are still free.
$ git-into-gsoc start╭──────────────────────── git into gsoc: start ────────────────────────╮│ Four quick questions, then organizations that fit you and what to do ││ next. ││ Press Enter to skip any question. Your answers stay on this ││ computer. │╰──────────────────────────────────────────────────────────────────────╯GSoC 2027: Before the program is announcedNext date: Program Announce Date, 2026-12-02 (in 30 days, an estimate)The best time to start. Pick orgs that participated last year, contribute steadily, and treat every date as an estimate until Google publishes it.1 of 4 Your GitHub username? It lets the tool read your public languages. > (Enter)2 of 4 Languages and tools you know? For example: python, javascript, java, c++ > python3 of 4 What would you enjoy working on? Pick numbers or type your own words. 1 science and medicine 8 security 2 AI and machine learning 9 graphics, audio, and video 3 websites and web apps 10 operating systems 4 data and databases 11 education 5 developer tools 12 robotics 6 programming languages and compilers 13 mobile apps 7 cloud and infrastructure 14 gamesSeparate several with commas > 1, 44 of 4 About how many hours a week can you give? > 8Organizations that fit you2027 orgs are not announced yet; showing official 2026 participants, thebest predictor of who returns. 1. Machine Learning for Science (ML4SCI) Machine learning applications in science Why: Topic: Science and research software; Topic: Data science; Uses Python ✓ 70 ideas on its 2026 ideas page 2. CERN-HSF Umbrella for Particle Physics-related projects Why: Topic: Science and research software; Topic: Data science; Uses Python ✓ 39 ideas on its 2026 ideas page 3. NumFOCUS NumFOCUS promotes open source scientific software. Why: Topic: Science and research software; Topic: Data science; Uses Python ✓ 58 ideas on its 2026 ideas page; of the 18 that state a difficulty: 1 easy, 8 medium, 9 hard ! At 8 hours a week its medium ideas need a longer coding period than the standard 12 weeks; ask the mentors early ! At 8 hours a week, a small project (about 90 hours) fits in about 12 weeks; a medium one (about 175 hours) would take about 22 weeks, the longest period allowed, which leaves no room for exams or setbacks; large projects would not fit in the longest coding period (22 weeks, andonly if your mentor agrees). Choose a small idea and state your hours inyour proposal. Source: https://developers.google.com/open-source/gsoc/faqShortlist any of these now? Type their numbers, or press Enter to skip > 1✓ Your shortlist: Machine Learning for Science (ML4SCI)Your next steps 1. Read Machine Learning for Science (ML4SCI) closely: ideas page, chat channels, past projects git-into-gsoc org "Machine Learning for Science (ML4SCI)" 2. See which of its repositories mentors work in and welcome newcomers git-into-gsoc repos "Machine Learning for Science (ML4SCI)" 3. Whenever you are unsure what to do, ask git-into-gsoc next Change your answers any time: run start again, or git-into-gsoc profile.Prefer an AI assistant? Ask it in your own words, such as "Which GSoC issue should I try first?" If it does not know git-into-gsoc yet, run `git-into-gsoc setup` once.
house rules.
These are built into the tool, the assistant skill, and the docs. They are also stickers.
-
Every organization, repository, issue, and date has a source you can open. Scores are explained. When data is missing, the tool says so instead of guessing.
-
No typo farms, no mass "assign me" comments, no generated essays. One useful change you understand well enough to defend in review is worth more than twenty you don't.
-
The tool never posts, comments, or submits anything for you. Your profile and progress stay in a file on your computer. No account, no tracking. Every message a maintainer reads is one you wrote.
-
The goal is a reviewed, merged contribution and a mentor who knows your name from useful work.
bring your assistant.
The same tools run inside any MCP client (an assistant that supports the Model Context Protocol, the standard way assistants use outside tools), and a portable Agent Skill teaches the assistant how to coach without fabricating or spamming. It can look things up for you. It still can't write your proposal, and many organizations' AI policies say it shouldn't.
- Claude Code
- Codex
- Cursor
- VS Code
- Copilot CLI
- Gemini CLI
- Antigravity
- Windsurf
- any MCP client
The installer already ran setup for you; run it again whenever you add an assistant. Prefer a plugin? Claude Code, Codex, Copilot, Gemini CLI, and Antigravity install the skill and server with their own commands, listed on the assistant page. The assistant setup guide covers manual configuration, and the MCP reference lists every tool.
Or add only the server to one app with one click. All but the Claude Desktop download need uv, a free tool that runs it. The app shows what it will run and asks you first:
git-into-gsoc setup
git-into-gsoc doctor
setup finds your assistants (claude code, codex, cursor,
vs code, copilot, gemini, antigravity, windsurf),
copies the skill, and registers the mcp server.
keeps .bak copies.
doctor shows what is configured and where
then ask, in your own words: "I want to do Google Summer of Code. I know Python and like science. Where do I start?"