Practice open source event vocabulary: hackathons, contributor sprints, good first issues, pair programming at events, and shipping PRs.
0 / 5 completed
1 / 5
What is a 'contributor sprint' at an open source conference?
Contributor sprints (also called 'sprints' or 'dev sprints' at events like PyCon or DjangoCon) bring the distributed project community together physically to make focused progress on the project. They're highly productive because async communication barriers disappear.
2 / 5
A maintainer at an open source event says: 'We've labelled some issues as good first issue — come find us.' What does this mean?
The 'good first issue' label is a community-standard signal for beginner-friendly contributions. At events, maintainers actively guide newcomers to these issues and offer in-person help — dramatically lowering the barrier to first contribution.
3 / 5
What is the significance of 'we shipped a PR at the hackathon'?
'Shipped a PR' at a hackathon or sprint means a contribution was actually merged into the main project — the highest form of success at a contributor event. It's a concrete outcome that demonstrates both the contributor's work and the maintainer's responsiveness.
4 / 5
What does 'we're sprinting on issue X' mean at an open source event?
'Sprinting on issue X' means the group has aligned on that specific issue as the focus of their time-boxed collaborative work session — pooling attention, expertise, and code review capacity on a single problem.
5 / 5
What is 'pair programming at events' and why is it especially valuable?
Pair programming at events enables fast knowledge transfer that would take weeks of async communication. A new contributor can pair with a maintainer, navigate the codebase, understand conventions, and ship a contribution in hours with in-person guidance.