Journey map
The beginner guide explains each step. This page is the one-screen version: every phase the tool tracks, what you leave it with, and the commands and guide page that belong to it.
learn → discover → evaluate → orient → community → find_issues → contribute → iterate → proposal → track
The order is a default, not a rule. You can loop (more issues after the first PR), and notes fit anywhere.
| Phase | You leave with | Commands | Guide |
|---|---|---|---|
learn |
You can explain GSoC and your own constraints | start, program, journey |
Understand GSoC |
discover |
Two or three organizations with a reason for each | orgs, org, ideas, mentors, projects, recommend |
Find organizations |
evaluate |
One or two repositories that merge newcomers' work | repos, repo |
Pick a repository and an issue |
orient |
You know where a change would go and how you would test it | orient |
Get your bearings |
community |
You have introduced yourself in the organization's public channel | org (channels), draft intro |
Introduce yourself |
find_issues |
One free, well-specified issue you can reproduce | issues, issue, pointers, draft claim |
Find a free issue |
contribute |
A reviewed pull request you can explain | draft pr, pr-check |
First contribution |
iterate |
Reviewers know you finish what you start | draft review-reply, next |
See it through review |
proposal |
An original draft in the organization's template | proposal, contributions, program |
Prepare a proposal |
track |
A weekly note habit | log, progress, next |
Track progress |
Mark a phase done with git-into-gsoc progress complete_phase --phase discover (or any other phase name from the table). Two orderings are deliberate. Orient comes before community, so your introduction can mention something concrete you read or ran. Community comes before claiming an issue, because the official contributor guide, Outreachy (another paid open-source internship program), and Google's guidance on low-quality proposals all say to make public contact first, and a short introduction makes your later comment on an issue land better.
Source: docs/journey.md on GitHub. Corrections are welcome.