Practise the collocations for maintaining repositories, reviewing contributions, and engaging the open-source community.
0 / 5 completed
1 / 5
The foundation assigned a team of three engineers to ___ the core repository long-term.
Maintain a repository is the standard open-source collocation for ongoing stewardship of a project — triaging issues, merging PRs, and releasing versions. 'Look after around' is informal. 'Service out' applies to hardware. 'Keep along' is too vague.
2 / 5
The governance committee met weekly to ___ contributions from the community and approve changes.
Review contributions is the standard open-source governance collocation for evaluating pull requests, issues, and proposals from external contributors. 'Check over all' and 'look through around' are informal. 'Assess out' is not standard.
3 / 5
The project leadership created a CONTRIBUTING.md file to ___ the Apache 2.0 license for all submissions.
Enforce a license is the standard open-source governance collocation for ensuring that contributions comply with the project's licensing terms. 'Apply out' and 'require around' are informal. 'Push along' is not used in this legal context.
4 / 5
The maintainers used GitHub Releases to ___ a new version every six weeks.
Publish a release is the standard open-source collocation for making a new version publicly available. 'Release out' is redundant. 'Ship along' is informal. 'Send around' implies a communication, not a software release.
5 / 5
The project relied on Discord and GitHub Discussions to ___ the community around the tool.
Engage the community (or 'engage with the community') is the standard open-source and developer relations collocation for building active participation. 'Involve along' and 'interact with around' are informal. 'Connect out' is not standard.