Practice community health vocabulary: bus factor, community burnout, maintainer fatigue, under-maintained projects, seeking new maintainers, and healthy contribution funnel concepts.
0 / 13 completed
1 / 13
What does 'bus factor' mean when applied to an open source community?
Bus factor (also called truck factor) measures resilience: if N people were 'hit by a bus', would the project survive? A bus factor of 1 means one person leaving could collapse the project. Healthy communities work to distribute knowledge and responsibilities.
2 / 13
A maintainer posts: 'I'm experiencing maintainer fatigue.' What does this signal?
Maintainer fatigue is a recognized phenomenon where open source maintainers become burned out from the volume of demands — especially when they are unpaid volunteers handling issues, PRs, and support questions without sufficient contributor support.
3 / 13
A project is described as 'under-maintained.' What does this typically mean?
An under-maintained project shows signs of neglect: stale issues, unreviewed PRs, outdated dependencies, and infrequent releases. This is often due to maintainer burnout, life changes, or the project outgrowing its volunteer capacity.
4 / 13
What is a 'healthy contribution funnel' in community management?
A healthy contribution funnel describes the journey from user to contributor to maintainer. Healthy communities create entry points at each stage — good documentation, 'good first issue' labels, mentoring, and a path to increased responsibility.
5 / 13
A project posts: 'we're looking for new maintainers.' What does this typically communicate?
This is a community health signal: the project is actively trying to expand its maintainer base to reduce bus factor, share the workload, and ensure long-term sustainability. It typically targets active, trusted contributors.
6 / 13
Sarah, a new contributor, asks the project maintainer, David, 'What's a 'core team' and why is it important?' David replies: 'A core team is the small group of people who are most actively involved in the project – they're essentially our bus factor. If they leave, it could seriously impact the project.' What does David mean by 'bus factor'?
David is referring to the 'bus factor,' a term coined by Doug Engelbart. It represents the risk an open-source project faces if its most critical members leave. A low bus factor means the project is heavily reliant on a few individuals and vulnerable to disruption if those individuals depart.
7 / 13
Slack message from @maintainer_jane: 'Ugh, this pull request review took me ages. I'm experiencing maintainer fatigue.' What does Jane's statement primarily signal?
'Maintainer fatigue' describes a state where developers feel excessively burdened by ongoing maintenance tasks – bug fixes, documentation updates, etc. This often leads to decreased motivation and reduced productivity; it isn't necessarily about the code complexity itself.
8 / 13
During a community management meeting, the team discusses 'healthy contribution funnel.' What does this concept refer to?
A 'healthy contribution funnel' describes a well-structured process that guides contributors from initial engagement to sustained involvement within the project. It's about creating opportunities for people to get involved and contribute meaningfully over time.
9 / 13
David, the project lead, is reviewing a pull request and notes that the commit message lacks context. He asks the contributor, Ben, 'Can you add some detail about why this change was made?' What does David likely mean by requesting more context in the commit message?
David is emphasizing the importance of maintainability and understanding. A good commit message isn't just about what was changed; it's about *why* it was changed – this allows future developers to quickly grasp the intent and context of the code. While conventions and issue links can be helpful, the core request is for clarity regarding the change itself.
10 / 13
Slack message from @community_manager_alice: 'We're seeing a lot of small, isolated pull requests – mostly just bug fixes. It's making it difficult to assess the overall health of the project.' What does Alice's statement primarily indicate about the community's contribution patterns?
Alice's observation suggests a lack of cohesive development. A high volume of small, isolated pull requests often indicates that the community isn't collaborating on larger goals or integrating changes effectively. This can lead to technical debt and difficulty in maintaining a consistent codebase – it's a classic sign of a less 'healthy' project.
11 / 13
PR description for a proposed change: 'Fixes a typo in the documentation.' What type of contribution does this represent?
This PR focuses solely on correcting a minor inconsistency (a typo). While important for maintainability and user experience, it doesn't involve adding new functionality or fundamentally altering the code. It's a straightforward fix, often categorized as technical debt – addressing existing issues without introducing new ones.
12 / 13
Standup update from @developer_richard: 'I've been working on improving the error handling in the authentication module. I'm experiencing maintainer fatigue.' What does Richard likely mean by expressing 'maintainer fatigue' during his stand-up?
'Maintainer fatigue' is a common term used in open source communities – it signifies that the maintainer feels burdened by the responsibilities of maintaining the project. This could be due to excessive workload, technical challenges, lack of support from the community, or feeling disconnected from the project's direction.
13 / 13
@maintainer_john posts in a Slack channel: 'We're looking for new maintainers to help with the project's scalability issues. Anyone interested should reach out.' What does this primarily communicate?
This statement signals an active need for assistance. The phrase 'scalability issues' indicates that the project is facing challenges related to handling increased load or complexity – a clear call for more maintainers to help tackle these specific problems and contribute to its future development.
What does the "Community Health Vocabulary Quiz" exercise practise?
Practice community health vocabulary: bus factor, community burnout, maintainer fatigue, under-maintained projects, seeking new maintainers, and healthy contribution funnel concepts.
How many questions are in this exercise?
This exercise has 13 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Developer Community Management category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Community Health Vocabulary Quiz" part of a larger series?
Yes — it's one exercise in the Developer Community Management category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Developer Community Management category page for related exercises, or browse the main Exercises hub for other IT English topics.