Practice the English used by open-source maintainers: welcoming contributors, reviewing PRs, managing feature requests, and communicating project decisions.
0 / 8 completed
1 / 8
Which response best welcomes a first-time contributor who submitted a PR with an issue?
Good maintainer communication thanks the contributor, acknowledges what is right, provides specific actionable feedback, and offers support. This encourages continued contribution.
2 / 8
How would a maintainer professionally close a feature request that is out of scope?
Professional scope rejection thanks the requester, explains the project's focus, closes with a reason, and offers an alternative path. This maintains community goodwill even when declining.
3 / 8
What does 'project governance' mean in an open-source context?
Governance defines decision-making power: who is a maintainer, how new maintainers are added, how disputes are resolved. Clear governance prevents conflict and makes the project more trustworthy for adopters.
4 / 8
Which sentence correctly describes 'triage' in an open-source issue tracker?
Issue triage is essential for maintainable projects. Without it, the issue tracker becomes a dumping ground. Triage labels (bug, enhancement, question, duplicate) help contributors and maintainers navigate the backlog.
5 / 8
What is a 'stale issue' and how should maintainers communicate about it?
Polite stale issue communication explains the reason for potential closure, gives the reporter a chance to respond, and maintains a clean issue tracker. Automated stale bots use similar language.
6 / 8
How would a maintainer communicate a breaking change in a new release?
Breaking changes require proactive, detailed communication: what changed, who is affected, how to migrate, and where to find help. This reduces friction for upgraders and support requests.
7 / 8
What does 'LGTM' mean in a code review comment on a PR?
LGTM (Looks Good To Me) is a widely used code review abbreviation indicating approval. It originated in open-source projects and is now standard in both open-source and corporate engineering.
8 / 8
What is 'bus factor mitigation' strategy for open-source maintainers?
Open-source projects with a single maintainer are fragile. Mitigating bus factor means bringing in co-maintainers, documenting everything, and distributing permissions — so the project survives if the primary maintainer becomes unavailable.