Open Source Governance Models — Vocabulary and Discussion
Learn vocabulary for open-source governance models: Apache Way, BDFL, steering committees, and governance trade-offs.
0 / 10 completed
1 / 10
What is the 'Apache Way' in open source governance vocabulary?
The Apache Way is the ASF's governance philosophy: community matters more than code, decisions require rough consensus (not unanimity), those who do the work make the decisions (do-ocracy), all project communication is transparent and archived, and the community is self-governing within ASF policies.
2 / 10
What is 'BDFL' in open source governance vocabulary?
BDFL (Benevolent Dictator For Life) is a governance model where one person has final authority — named after Guido van Rossum's role in Python. It provides clear decision-making but creates a bus factor problem. Guido resigned as Python's BDFL in 2018, replaced by the Python Steering Council.
3 / 10
What is a 'Steering Committee' in open source governance?
A Steering Committee is a formal governance body with defined membership criteria (elected, appointed, or delegated), decision authority (what decisions require SC approval), and process (meeting cadence, voting rules). Examples: Python Steering Council, Kubernetes Steering Committee, Rust Leadership Council.
4 / 10
What is 'do-ocracy' in open source governance vocabulary?
Do-ocracy: influence is proportional to contribution. Those who write the code, review PRs, answer issues, improve documentation, and organize events earn the standing to make decisions in those areas. This is distinct from formal governance — it is an informal but powerful norm in many open-source communities.
5 / 10
What is a 'governance change proposal' in open source vocabulary?
Governance change proposals are formal documents (often in GitHub repos as GOVERNANCE.md PRs or RFC-style documents) proposing changes to the project's decision-making structure. They typically require community discussion, comment period, and formal approval — a higher bar than technical changes.
6 / 10
Reviewer: 'This PR needs more discussion before being merged. The maintainers are concerned about the potential impact on the core API's stability. Can you elaborate on your proposed changes and how they align with the project's governance model?', Which of the following best represents the reviewer's concern regarding this PR?
The reviewer is not simply criticizing the code's technical correctness. They are raising a concern directly related to open source governance – specifically, the impact of changes on the core API. The correct answer reflects an understanding that maintaining stability and adhering to established governance models (like phased rollouts) are key considerations in open-source projects. Options A and B present irrelevant concerns; option C demonstrates disregard for established processes.
7 / 10
Slack Message (from @johndoe): 'Just submitted a governance change proposal to formally request the addition of a dedicated security auditing task within the project's roadmap. It's currently under review by the steering committee.' What does this Slack message primarily indicate?
The key element here is 'formal request' and the mention of a 'steering committee'. This signifies that John has followed the established governance procedure by submitting a proposal for review. Options A and B misinterpret the context; option C describes a simpler process than this one suggests.
8 / 10
API Response (from the project's governance server): `{"status": "pending", "proposal_id": "GC-2024-123", "submitted_by": "johndoe", "review_deadline": "2024-10-27"}`. What does this API response primarily convey?
This API response provides critical information about the status of the governance change proposal. The `status: "pending"` indicates that it's awaiting review, and the other fields (proposal_id, submitted_by, review_deadline) offer further context regarding its progress. Options A, B, and C present inaccurate interpretations of the API data.
9 / 10
PR Description (from @sarah): 'This PR implements a new metric for tracking code churn. The Steering Committee suggested this as part of their ongoing effort to improve stability and reduce the risk of regressions.' What is Sarah's primary justification for her contribution, based on this description?
Sarah's justification lies in the fact that her work directly supports a decision made by the Steering Committee. This demonstrates adherence to established governance processes and highlights how individual contributions can be aligned with broader strategic goals. Option A presents an overly broad goal; option C ignores the existing process; option D is incorrect.
10 / 10
Standup Update (from @david): 'I've been working on drafting a formal governance change proposal to standardize the process for submitting code contributions. The goal is to reduce ambiguity and ensure consistency across all development efforts.' What does David's update primarily focus on?
David's statement highlights his involvement in improving the *governance* of the project. He's recognizing an existing weakness (ambiguity) and proposing a solution – standardizing contribution processes – which is directly aligned with good governance practices. Options A, B, and C present irrelevant activities.
What will I practise in "Open Source Governance Models — Vocabulary and Discussion"?
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.