Open Source Roadmap — Governance and Communication
Learn vocabulary for communicating open-source project roadmaps: WONTFIX decisions, feature request processes, and public roadmap communication.
0 / 12 completed
1 / 12
What does 'WONTFIX' mean in open source issue tracking?
WONTFIX is a deliberate decision: the project maintainers have decided this issue will not be fixed (for reasons: out of scope, design decision, not aligned with project direction, better handled by the user). A good WONTFIX response explains why, and often points to alternatives or workarounds.
2 / 12
What is a 'feature request process' in open source governance?
A well-defined feature request process prevents scope creep and manages community expectations: submit an issue using the feature request template, discuss feasibility and alignment with project goals, maintainer decision (accept, decline, or defer), and if accepted — contribution pathway (who will implement it).
3 / 12
What is 'scope creep' in an open source project context?
Scope creep in open source: incrementally accepting features that expand the project's responsibilities beyond its core purpose. Each individual addition seems reasonable but collectively they bloat the project, increase maintenance burden, confuse new users about what the project does, and slow development of core functionality.
4 / 12
What is a 'public roadmap' in open source governance vocabulary?
A public roadmap communicates project direction transparently: what is planned (committed work), what is being considered (proposals under discussion), and what is out of scope. It helps users plan integrations, lets contributors self-select work aligned with direction, and sets community expectations.
5 / 12
What is a 'deprecation notice' in open source project vocabulary?
A deprecation notice: 'Feature X is deprecated as of v2.3 and will be removed in v3.0 (expected Q4 2025). Use Feature Y instead. Migration guide: [link].' Good deprecations: give ample warning (typically 1–2 major versions), provide clear migration paths, and add code warnings to alert users at runtime.
6 / 12
Sarah from the Core Team sent this Slack message to the project maintainers: 'Hey team, we've received a lot of feedback on adding support for GraphQL. While it's technically feasible, it significantly expands the scope and introduces complexities that could derail our current sprint goals. Let's discuss if this aligns with our prioritized roadmap.' What is Sarah primarily communicating?
This question tests understanding of communication within an open-source project. Sarah isn't simply stating feasibility; she's raising concerns about scope creep and potential disruption to the current roadmap. Option B accurately reflects her cautious approach – prioritizing strategic alignment over immediate implementation based on perceived demand.
7 / 12
Mark is writing a pull request description for a small bug fix. He includes the following: 'Fixed an issue where the user profile image wasn't loading correctly on mobile devices. This was reported by David in Issue #1234.' What aspect of open source governance does this best illustrate?
This question focuses on community involvement and issue tracking. Mark's description highlights how bug reports (Issue #1234) are documented and linked to the code change – a crucial element of transparency and accountability within an open-source project. Tracking contributions like this demonstrates that the project values community feedback.
8 / 12
David from the community reported a potential security vulnerability via a GitHub issue. As a maintainer, which of the following is the MOST appropriate response to include in the PR description for addressing this report?
The correct answer prioritizes realistic open-source governance. While acknowledging the report and forwarding it are good steps, a common approach in many projects is to defer security fixes until features are stable. Option A is too vague; option B implies premature deployment without proper testing. Option D focuses on routing, neglecting the core issue of prioritization.
9 / 12
Elena, a new contributor, proposes adding a complex new feature to the project's API. During the discussion, several maintainers express concerns about potential performance impacts and the need for extensive testing. Which of the following statements BEST reflects the appropriate next step in the governance process?
This scenario tests understanding of collaborative governance. The best response involves acknowledging the suggestion but also demanding a critical evaluation. Option A is reactive and doesn't address concerns. Option C demonstrates poor governance; rejecting without discussion isn't productive. Option D is dismissive and fails to foster collaboration.
10 / 12
Mark is drafting a pull request description for a minor UI update. He wants to ensure transparency. Which of the following phrases would be MOST effective in clearly communicating the change's purpose and impact?
The key here is providing context and demonstrating value. Option A is too technical and doesn't explain why the change was made. Option B provides a clear explanation of the change and its intended benefit. Options C and D are overly simplistic descriptions of minor changes.
11 / 12
Liam, the project lead, sends out the following message to the team regarding a planned roadmap update: 'We're shifting our focus from v2.0 to v2.1, incorporating user feedback and addressing critical performance bottlenecks. This means some previously discussed features might be delayed.' What does this communication primarily illustrate about open-source roadmap management?
This question tests understanding of dynamic roadmapping. The message clearly shows a shift in priorities due to feedback and performance issues – a common occurrence in agile software development. Rigid timelines and inflexible documents are detrimental. Option D is the opposite of best practice.
12 / 12
Chloe is reviewing a pull request that adds support for a new data format. The code is well-written and functionally correct, but the documentation lacks details about how to use the new format. Which of the following actions should Chloe prioritize in her review feedback?
Documentation is critical for long-term maintainability and adoption. While bug fixes are important, comprehensive documentation ensures others can understand and use the feature effectively. Option A demonstrates a lack of foresight; option C is dismissive; and option D focuses only on code correctness.
What will I practise in "Open Source Roadmap — Governance and Communication"?
This module focuses on OSS Governance — real workplace phrasing you'll use on the job. It contains 12 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 12 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.