Contributor Ladder Vocabulary — Roles and Responsibilities
Learn vocabulary for open-source contributor ladder roles: contributor, committer, maintainer, project lead, and BDFL — definitions and responsibilities language.
0 / 10 completed
1 / 10
In open source vocabulary, what distinguishes a 'committer' from a general 'contributor'?
The contributor → committer distinction is fundamental in projects like Apache: contributors submit patches via pull requests or patches; committers have been trusted with direct write access. Committer status is earned through sustained, high-quality contributions and is granted by existing committers or a PMC vote.
2 / 10
What is a 'BDFL' (Benevolent Dictator For Life) in open source governance?
BDFL is a governance pattern popularised by Python (Guido van Rossum) and Django. The BDFL has final say on contested decisions, preventing governance deadlock. The 'For Life' is aspirational — Guido resigned in 2018. It works well in small projects but raises succession risk concerns as projects grow. Alternative: a steering council or technical committee.
3 / 10
What phrase correctly describes a maintainer's responsibilities in open source communication?
Maintainer responsibilities typically include: reviewing and merging PRs, triaging issues, cutting releases, shaping the roadmap, onboarding new contributors, enforcing the Code of Conduct, and representing the project to external stakeholders. The maintainer role is about stewardship, not just code production.
4 / 10
How would you correctly use 'project lead' in an open source context?
Project lead is a broad title that varies by project. Common responsibilities: setting vision and roadmap, coordinating maintainer team, making final calls on disputed RFCs, representing the project to foundations (e.g., CNCF, Apache), and managing relationships with sponsors. Distinguished from BDFL in that project leads are often term-limited or elected.
5 / 10
What is the correct vocabulary for describing the transition from 'contributor' to 'maintainer' in a governance document?
Standard maintainer promotion language in GOVERNANCE.md files: 'A contributor may be nominated for maintainer status by an existing maintainer. The nominee must have demonstrated sustained contributions over [time period], shown good judgement in code reviews, and a working knowledge of the codebase. Promotion requires [N/majority] vote of current maintainers.' This makes the ladder objective and transparent.
6 / 10
During a Slack discussion about the upcoming release of libwidget, Sarah, the project lead, asks John to review the proposed API changes. Which phrase best describes her role in this situation?
The project lead's role involves formal evaluation and approval of code changes. This is a key responsibility for ensuring quality and adherence to the project's standards. Options A and D misrepresent her authority; options B and C describe supporting functions rather than leadership.
7 / 10
You've submitted a pull request containing several bug fixes for the coreutils project. The maintainer, David, responds with: 'Thanks for submitting this! We'll need to discuss the tests you've added to ensure they cover all edge cases.' What does David likely mean?
David's comment highlights the need for a thorough review of the tests to guarantee they adequately address potential issues. This emphasizes the maintainer's responsibility in ensuring the quality and robustness of the codebase – it's not just about accepting the PR; it's about validating its effectiveness.
8 / 10
In a standup meeting, Mark, a contributor to the webserver project, says: 'I'm working on improving the performance of the static content delivery system. I've implemented some caching optimizations.' What is Mark effectively communicating regarding his contribution?
Mark's statement provides a clear and concise update on his work, detailing a specific action (caching optimizations) and its intended impact (improved performance). This demonstrates effective communication within a technical context – quantifiable results are key in standups.
9 / 10
You're drafting the description for a pull request proposing changes to the documentation of the database project. Which sentence is MOST appropriate?
'This PR updates the user guide with new information about the latest features.'
A pull request for documentation changes *always* requires thorough testing. This ensures that the updated information is accurate, consistent with the current codebase, and doesn't introduce any errors. The description should reflect this critical step in the process.
10 / 10
During a code review, Alice identifies a potential security vulnerability in Bob's code. She suggests a fix and explains the reasoning behind her recommendation. What is Alice demonstrating regarding her responsibilities?
A core responsibility of a reviewer – particularly in security contexts – is to identify vulnerabilities and offer solutions. Alice's action showcases her commitment to quality assurance and proactive risk mitigation, not just passive observation or criticism.
What will I practise in "Contributor Ladder Vocabulary — Roles and Responsibilities"?
This module focuses on OSS Governance — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this OSS Governance exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around oss governance — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more OSS Governance exercises?
See the OSS Governance hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.