First merge
Weekly live reviews, triage sandbox, portfolio framing tied to merged work.
Custom desk
Open Source Training That Turns First-Time Developers Into Confident Contributors
This page is the long-form companion to the homepage question. It is not a funnel timer—it is a map you can send to a mentor who keeps asking what “open source practice” should look like in 2026.
How the contribution path works
- Pick a scoped issue with a written definition of done.
- Draft privately until CI passes on your branch.
- Request review with a cover letter that names risk, not ego.
- Respond with diffs, not arguments, when maintainers push back.
- Archive the lesson even if the merge never lands.
Issue
→
Branch
→
CI
→
Review
→
Merge or lesson
Mentor-led practice tracks
Git signals
Rebase, bisect, and recovery drills with reviewer-friendly commit messages.
Maintainer voice
Rewrite harsh threads, set boundaries, keep contributors returning without burnout language.
Success stories from first merged pull requests
Names appear with consent. We include the programs so you can verify the syllabus points we reference.
- First Merge Cohort · merged docs fix after three review rounds—participant cited mentor cover letter template.
- Patch Packaging Week · split a medium feature into four commits; maintainer thanked the CI babysitting checklist.
- Issue Triage Field Notes · duplicate linking habit carried into a civic OSS backlog without us staffing their desk.
Program Director
Haneul Park
Keeps cohort cadence honest and routes tricky maintainer conversations early.