Community Health Vocabulary — Bus Factor, CHAOSS, Issue Triage
Learn vocabulary for open source community health: bus factor, contributor diversity, issue triage, good first issue, help wanted labels, and CHAOSS metrics language.
0 / 10 completed
1 / 10
What is the 'bus factor' (also called 'truck factor') in open source vocabulary?
Bus factor (or truck factor) is a key community health metric. Bus factor = 1 is a critical risk: one person leaving, burning out, or becoming unavailable stalls the entire project. Mitigation strategies: documentation (no tribal knowledge), pair programming/reviews, onboarding multiple people to each critical area, spreading commit access, and succession planning. CHAOSS tracks this as 'contributor absence factor'.
2 / 10
What does 'good first issue' mean as a GitHub label and why is it important for community health?
Good first issue (GFI) is a community health tool: it signals to newcomers 'this is achievable for you'. Effective GFIs have: clear problem description, pointer to relevant code, expected outcome, and ideally a maintainer offering to mentor. Projects with active GFI programs (e.g., Kubernetes, VS Code) consistently attract new contributors. 'Up for grabs' and 'beginner-friendly' are synonyms in some projects.
3 / 10
What is 'issue triage' in open source community vocabulary?
Issue triage is a critical (and often under-resourced) community health activity. Without triage, issue queues become unmanageable: valid bugs get lost, duplicates multiply, and contributors give up. Many projects have dedicated triage teams or rotations. Triage labels: 'needs-reproduction', 'confirmed', 'wontfix', 'duplicate', 'backlog', 'priority/critical'. Regular triage meetings are a sign of a healthy project.
4 / 10
What is CHAOSS (Community Health Analytics Open Source Software) in open source vocabulary?
CHAOSS (chaoss.community) is a Linux Foundation project that standardises community health metrics: Contributor activity (commits, reviews, issues), Diversity & Inclusion (contributor demographics, CoC presence), Risk (bus factor, licence compliance, security response time), Value (downstream usage, organisational affiliation). Tools like GrimoireLab implement CHAOSS metrics. Used by CNCF, Eclipse Foundation, and others to assess project health.
5 / 10
What is 'contributor diversity' in open source community health vocabulary and why does it matter?
Contributor diversity has multiple dimensions: organisational diversity (no single company controls >50% of commits — a CNCF graduation criterion), individual diversity (distributed knowledge, no bus factor of 1), demographic diversity (gender, geography, background — tracked by CHAOSS D&I metrics). Projects dominated by a single employer risk: sudden withdrawal of resources, licence changes, and loss of community trust. Kubernetes tracks organisational diversity per release cycle.
6 / 10
A project's 'bus factor' refers to the number of developers who know the critical parts of the codebase. A high bus factor indicates stability and resilience, but a low one suggests vulnerability if key individuals leave. Which of the following best describes the significance of this metric in open source projects?
The 'bus factor' measures the risk associated with losing contributors. A high bus factor (few people know everything) is risky; a low bus factor (many people know critical parts) is also risky. Option 3 represents a balanced approach – some redundancy is normal but key developers should still be present. Options A and D are too extreme.
7 / 10
You're reviewing a pull request for the 'AwesomeLib' project. The PR description includes a label: 'Needs Review - High Bus Factor'. What does this label primarily indicate?
The 'High Bus Factor' label signals that changes in this PR are potentially very sensitive and reliant on a small group of developers. This means careful review is critical to avoid introducing significant problems if those key individuals leave or their knowledge is lost. Option 2 is incorrect because it focuses on the contributor, not the impact.
8 / 10
During a Slack discussion about improving the 'WidgetCore' project's community health, someone mentions 'issue triage'. What is the primary purpose of issue triage in an open source context?
Issue triage is about systematically sorting and prioritizing bugs or feature requests. This ensures that the most important issues are addressed first, maximizing the impact of community contributions. Options A, C, and D represent misinterpretations – triage isn't automation or permanent removal; it's prioritization.
9 / 10
A developer is using the CHAOSS toolkit to assess the health of a project. Which of the following metrics does CHAOSS primarily focus on measuring?
CHAOSS provides tools to analyze open-source projects based on various health metrics. It focuses heavily on dependencies – tracking versions and identifying potential conflicts—as this is a key indicator of stability and maintainability. Options A, B, and D are broader measures of community activity that CHAOSS doesn't directly assess.
10 / 10
A project maintainer is concerned about a lack of diversity among contributors to the 'DataStream' library. Why might this be a significant issue for community health?
A lack of diversity in contributors can lead to blind spots – different backgrounds and experiences bring different perspectives, which is crucial for identifying potential vulnerabilities (security, usability). A more diverse team is likely to be better equipped to anticipate a broader range of use cases. Options A, C, and D are optimistic but not the core concern.
What will I practise in "Community Health Vocabulary — Bus Factor, CHAOSS, Issue Triage"?
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.