Open Source Governance Meeting Language — Steering Committee, RFC, Voting
Learn vocabulary for open source governance meetings: steering committee, RFC process, proposal acceptance, voting procedures, and consensus-building language.
0 / 10 completed
1 / 10
What is an RFC (Request for Comments) in open source governance vocabulary?
RFC processes (used by Rust, Kubernetes KEPs, Python PEPs, TC39 for JavaScript, React RFCs) standardise how significant changes are proposed: a written document describing the motivation, detailed design, alternatives considered, and drawbacks. The community comments during a review period; then a decision is made by maintainers, steering committee, or vote. This prevents ad-hoc decision-making.
2 / 10
What is a 'steering committee' in open source project governance?
Steering committees (Kubernetes Steering Committee, Knative Steering Committee, etc.) handle: overall project governance, code of conduct enforcement escalations, changes to governance documents, working group creation/dissolution, and cross-cutting concerns that span maintainer teams. Members are typically elected by contributors with voting rights for fixed terms (e.g., 2 years, staggered).
3 / 10
Which phrase correctly describes a proposal outcome in a governance meeting?
Standard governance meeting outcome language: 'The proposal is accepted / rejected / deferred / withdrawn.' Acceptance often comes with conditions: 'accepted with the following amendments', 'accepted pending a security review', 'accepted for inclusion in v2.0'. Rejected proposals should include reasoning. Deferred means revisiting in a future cycle. Clear outcomes prevent ambiguity.
4 / 10
What does '+1', '-1', and '0' mean in Apache-style open source voting?
Apache-style voting: +1 (yes, approve), 0 (abstain, no strong opinion), -1 (veto — must be accompanied by a technical justification; in Apache governance a -1 is a binding veto that blocks the vote). In many projects, only PMC members or maintainers have binding votes; others can express +1/-1 as advisory non-binding votes. Three binding +1 and no binding -1 is a common passing threshold.
5 / 10
What is 'lazy consensus' in open source governance communication?
Lazy consensus (widely used in Apache projects): post a proposal with a '[VOTE]' or '[LAZY CONSENSUS]' subject; if no binding -1 is received within the review window (e.g., 72 hours for regular decisions, longer for releases), the proposal passes automatically. This prevents governance bottlenecks — requiring active approval from all voters would stall progress. Contentious decisions require explicit votes.
6 / 10
You're attending a steering committee meeting for the OpenLib project. A member proposes adding a new feature: automatic code formatting upon commit. The discussion quickly becomes heated, with some members arguing it's unnecessary complexity and others insisting it would improve developer workflow. Which phrase best describes the next step in this process?
A steering committee meeting needs a defined process. Simply continuing discussion without a formal motion doesn't represent a decision. Option 1 correctly identifies that a concrete justification for the feature is required before proceeding. Options 2 and 4 are premature; option 3 is too passive.
7 / 10
Review this code review comment:
`It looks good, but can you add a unit test for the `calculate_price` function? I'm not sure if it handles edge cases correctly.`
Which of the following best describes the tone of this comment?
This comment is constructive because it identifies a potential issue (lack of unit tests) and offers a specific suggestion (adding one). It avoids harsh criticism or judgment. Options 1 and 3 are inaccurate; option 2 describes overly critical phrasing.
8 / 10
A developer, @johndoe, sends this Slack message in the #project-alpha channel:
`@jane.doe just merged a PR with a massive code change! Seriously, who wrote this?! 😡`
What does this message primarily demonstrate about @johndoe's communication style?
The message contains negative emojis and a judgmental question. This demonstrates an unprofessional communication style characterized by negativity and potentially disrespect. Options 1 and 3 are incorrect; option 4 is irrelevant to the tone.
9 / 10
You're writing a PR description for a change that fixes a bug in the authentication module. The description should clearly communicate the issue and the solution. Which of the following is the MOST effective phrasing?
The best description provides context and explains *why* the change was made. Option 1 is too vague; option 3 is simply stating an action; option 4 is misleading as it doesn't explain the impact of the fix.
10 / 10
During a daily stand-up, Sarah says: 'I spent yesterday investigating the performance issues with the API endpoint. I'm still not sure what's causing the slowdown.'
What does this statement primarily indicate about Sarah's progress and next steps?
Sarah admits she hasn't yet found a solution. She's stated that she is still 'not sure what's causing the slowdown,' indicating a lack of clear progress and requiring further investigation. Options 1, 3 and 4 are all incorrect.
What will I practise in "Open Source Governance Meeting Language — Steering Committee, RFC, Voting"?
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.