Open source governance has its own professional vocabulary. This quiz covers the collocations for accepting contributions, enforcing codes of conduct, cutting releases, and managing project direction.
0 / 5 completed
1 / 5
Fill in: 'The maintainers voted to ___ external contributions only after a signed CLA was in place.'
We 'accept contributions' — 'accept' is the open source governance standard for formally welcoming code or documentation from external authors. 'Take contributions' is informal; 'allow contributions' focuses on permission; 'approve contributions' emphasises the review step rather than the act of welcoming them into the project.
2 / 5
Fill in: 'Two core maintainers must ___ every pull request before it can be merged into the main branch.'
We 'review PRs' — 'review' is the standard open source term for providing structured technical feedback on a proposed change. 'Check' implies a quick verification; 'approve' is what comes after reviewing; 'read' describes a passive act, not the analytical feedback expected in a code review.
3 / 5
Fill in: 'The Technical Steering Committee has the authority to ___ the Code of Conduct when behaviour violates community standards.'
We 'enforce the Code of Conduct' — 'enforce' conveys the active exercise of authority to take action when violations occur. 'Apply' suggests a process without authority; 'use' is informal; 'implement' refers to establishing the policy initially, not acting on breaches.
4 / 5
Fill in: 'The maintainers plan to ___ the next major release once the three outstanding regressions are fixed.'
We 'cut a release' — 'cut a release' is the open source community collocation for performing the technical steps of tagging, building, and publishing a versioned release. 'Publish a release' focuses on distribution; 'ship a release' is common in product teams; 'release a release' is redundant.
5 / 5
Fill in: 'The community is invited to comment on the GitHub issue where we will ___ the roadmap for the next year.'
We 'manage a roadmap' — 'manage a roadmap' is the ongoing governance activity of maintaining, updating, and communicating a project's direction. 'Define a roadmap' describes the initial creation; 'plan a roadmap' focuses on the planning phase; 'set a roadmap' implies a one-time act rather than the continuous curation expected of open source governance.