How to apply (playbook)
Programs differ, but successful applicants usually do the same things.
1. Start 3–6 months before applications
- Join the project’s chat / mailing list (Matrix, Slack, Discord, or lists — use what they ask for).
- Fix good-first-issue bugs and improve docs.
- Link your PRs in your application — selectors want evidence you can ship.
2. Pick fewer orgs, go deeper
- Two strong org relationships beat ten shallow ones.
- Read their roadmap and open proposals from past years (GSoC publishes archives).
3. Write proposals like a mini design doc
- Problem, approach, milestones, risks, schedule.
- Name your mentor contact only if the org allows it.
4. Calendar discipline
- Put every deadline in your calendar in UTC.
- Outreachy initial apps are short — do not wait for the full project list.
5. Parallel tracks
| If you are… | Consider |
|---|---|
| University student, Bitcoin-curious | Summer of Bitcoin + GSoC |
| Underrepresented in tech | Outreachy (often highest stipend) |
| Cloud / CNCF stack | LFX Mentorship |
| Complete beginner | 24 Pull Requests, then GSoC or GSSoC |
| Technical writer | Season of Docs |
6. After rejection
- Ask mentors for feedback (politely).
- Keep contributing — many acceptances happen on the second try.
7. Use the calendar
See when-to-apply.md so you do not miss short windows (Outreachy initial apps, SoB in February, etc.).
8. Pick orgs deliberately
See find-organizations.md for GSoC/LFX/Outreachy org browsers and contribution norms.
9. Templates & FAQ
- choose-a-program.md — pick 2–3 targets
- first-contribution.md — before you apply
- ../templates/gsoc-proposal-outline.md
- ../templates/outreachy-checklist.md
- ../FAQ.md