Open Source Maintainer
Open source maintainers communicate constantly — in GitHub issues, PR reviews, mailing lists, and release announcements — with a global audience of varying English fluency and technical background. This path builds the vocabulary and writing patterns to run a healthy project: welcoming contributors, navigating difficult community conversations, writing governance documents, and announcing changes in ways that build rather than burn trust.
Topics covered
- community governance
- contributor onboarding
- license compliance
- issue triage
- community health
Vocabulary spotlight
4 terms every Open Source Maintainer should know in English:
Benevolent Dictator For Life — a governance model where one person has final decision-making authority, typically the project founder
"Python used the BDFL model until Guido van Rossum stepped back in 2018."
A documented progression of roles (contributor → committer → maintainer) with defined responsibilities and rights at each level
"Our contributor ladder makes it clear how someone moves from occasional contributor to core maintainer."
A document that sets behavioural expectations for community members and describes how violations are handled
"Before contributing, please read our code of conduct — we take it seriously."
A decision-making approach where a proposal is accepted if no objection is raised within a defined period
"We use lazy consensus for minor changes — if nobody objects in 72 hours, the PR merges."
Contributor Licence Agreement — a legal document that grants the project rights to use a contributor's code
"You need to sign the CLA before we can merge your first contribution."
Developer Certificate of Origin — a lightweight sign-off in each commit confirming the contributor has the right to submit the code
"We switched from a CLA to a DCO to lower the barrier for first-time contributors."
📚 Vocabulary Reference
Key terms organised by category for Open Source Maintainers:
Governance
Legal & Licensing
Community
Release & Deprecation
Recommended exercises
Real-world scenarios you'll practise
- Writing a CONTRIBUTING.md that makes first-time contributors feel welcome rather than overwhelmed.
- Responding to a first-time contributor whose PR needs significant rework without discouraging them.
- Triaging an issue backlog and writing clear "won't fix" responses that explain the decision without dismissing the reporter.
- Announcing a breaking change or deprecation in a way that gives users time and information to migrate.