Mentoring
The projects on this site are the teaching material. There is no separate curriculum, no exercise repo, and no toy problem set — you contribute to software that other people actually use, and the review you get is the lesson.
What you get
Section titled “What you get”- A pull request read properly. Not a rubber stamp and not a drive-by “LGTM”. Reviews say why, and point at the specific line.
- The reasoning, not just the verdict. When a change is rejected, the tradeoff that killed it gets written down — usually in the repository’s own docs, so the next person finds it.
- Real constraints. Accessibility rules, browser behaviour, hosting budgets, someone else’s API rate limit. The things that make software actually hard.
What is expected of you
Section titled “What is expected of you”- Pick something small first. A first PR that touches one file gets merged. A first PR that redesigns a subsystem usually does not.
- Say what you tried. “I expected X, got Y” is worth more than a screenshot of an error.
- Take the review as information. Changes get requested on almost every PR, including from maintainers. It is not a grade.
What this is not
Section titled “What this is not”- Not a paid position, and not a promise of one.
- Not a bootcamp with a completion certificate.
- Not a queue with an SLA — this is unpaid work on both sides, so reviews come when they come.
Where to start
Section titled “Where to start”Contributing has the mechanics. The active project is Vizably.