🌱 Open Source Community Building
0 / 26 completed
1 / 26
A new contributor submits their first PR. It has minor style issues but the logic is correct. Which maintainer response best builds community?
First-contribution responses set the community tone. The effective response: welcomes explicitly, validates the substantive work (logic), gives specific actionable feedback (inline comments), commits to merging after fixes, and opens the door to questions. Closing for style issues without guidance drives away contributors permanently. Merging silently misses a teaching opportunity.
2 / 26
Which label strategy best helps new contributors find accessible issues?
"good first issue" is the industry-standard label that surfaces in GitHub's contributor discovery pages. Effective good-first-issue descriptions include: what the problem is, which file/function to look at, estimated effort, and what knowledge is needed. "help wanted" alone is too broad. No labels means contributors have to triage the entire backlog themselves.
3 / 26
Your project's CONTRIBUTING.md should include which sections?
CONTRIBUTING.md is the onboarding document for new contributors. Effective guides cover: environment setup (so contributors can run the project), issue discovery (so they find appropriate work), PR conventions (so they know what a good contribution looks like), review expectations (so they know what happens next), and the code of conduct (so they know community norms). Missing any of these creates friction that reduces contribution rates.
4 / 26
A contributor asks: "Is this project still active?" — there have been no commits in 3 months. Which response best serves the community?
Transparency about project status is a community health practice. "Maintenance mode" is a legitimate and respected status. Honest status communication lets contributors make informed decisions about investing their time. Ignoring the question damages trust. Saying "yes, active" when development is paused sets false expectations. Archiving without notice leaves dependent users without warning.
5 / 26
Which sentence best exemplifies a "welcoming newcomer" message in a community Discord or Slack?
Welcoming newcomer responses: answer the question directly, validate that it is a reasonable question, point to the relevant documentation, and — where possible — invite the newcomer to contribute. The "read the docs first" and "search before asking" responses, while sometimes justified, communicate unwelcome signals when used as the primary response to a genuine question. Redirecting channels without answering is a friction-maximising response.
6 / 26
Sarah, a new contributor, has submitted a PR to the AwesomeLib project. The code is functionally correct but uses a slightly outdated API version and lacks clear comments explaining its purpose. David, one of the core maintainers, responds with:
'> Thanks for submitting this! We appreciate your contribution. Just updating to the latest API version and adding some comments would be fantastic.'
Which of these options best describes David's response in terms of community building?David's response demonstrates key community-building behaviors. He acknowledges Sarah's effort (positive reinforcement), but importantly, he frames the feedback as 'fantastic,' rather than demanding an immediate overhaul. This approach is more welcoming and encourages a collaborative spirit – highlighting that improvement is a process, not a criticism. The incorrect options either focus solely on technical debt (too harsh) or fail to acknowledge the positive initial contribution.
7 / 26
Alex, a junior developer on the OpenSourceFramework project, submitted a pull request to fix a minor bug in the authentication module. The code was functionally correct but lacked sufficient documentation and followed outdated coding conventions. During a code review discussion on Slack, several senior members pointed out these issues, offering suggestions for improvement. Which of the following responses from the lead maintainer, Ben, best demonstrates proactive community building? 'Thanks for flagging this, Alex! We're always looking to improve our codebase and appreciate you bringing these points to our attention. Could you please address the documentation gaps and update your style guide to align with our project standards?'
This response is appropriate because it directly addresses the identified issues (documentation gaps and style guide alignment) while maintaining a professional and constructive tone. Crucially, it acknowledges Alex's effort—the 'appreciate you bringing these points to our attention' phrase demonstrates recognition and encourages continued engagement. The other options either lack specific guidance or adopt an unnecessarily critical approach which could be demotivating for new contributors.
8 / 26
Liam, a new contributor to the OpenSourceData project, has submitted a pull request containing a clever optimization for data processing. However, his commit message lacks context – it simply states 'Optimized'. The core maintainer, Maria, responds with:
'Great find, Liam! This is a valuable improvement. Could you add a brief description of the optimization and how it addresses the original problem in the commit message? Also, please include links to any relevant documentation or discussions.'This question tests understanding of effective community engagement. Option 1 misinterprets a request for context as overly demanding. Option 2 incorrectly frames Maria's response as verbose; she's simply seeking clarity to understand the *value* of the change. Option 4 best reflects a proactive approach – encouraging further dialogue and demonstrating that Liam's work is valued within the community, fostering a welcoming environment for questions and discussion. The key here is not just receiving feedback but actively building on it.
9 / 26
ProjectX is a popular open-source library for image processing. A new contributor, Rohan, submits a PR to fix a performance bottleneck in the resizing function. The code works correctly and significantly improves speed, but his PR description only includes a brief 'Fixed performance issue' message and doesn't mention the specific changes or any testing he performed. The lead maintainer, Sarah, responds with:
'Thanks for this, Rohan! Great to see you tackling a real problem. We appreciate your contribution.'
Which of the following actions best exemplifies community building in this scenario?The correct answer highlights that Sarah's response is sufficient—it acknowledges Rohan's contribution and subtly encourages further engagement. The other options represent missed opportunities for community building. Asking for a detailed report would be overly demanding at this early stage, and immediately merging without context could lead to issues down the line. A brief acknowledgment combined with an open invitation to continue contributing builds rapport and shows Rohan his work is valued.
10 / 26
Sarah, a new contributor, has submitted a PR to the AwesomeLib project. The code is functionally correct but uses a slightly outdated API version and lacks clear comments explaining its purpose. David, one of the core maintainers, responds with:
'> Thanks for submitting this! We appreciate your contribution. Just updating to the latest API version and adding some comments would be fantastic.'
Which of these options best describes David's response in terms of community building?David's response demonstrates key community-building behaviors. He acknowledges Sarah's effort (positive reinforcement), but importantly, he frames the feedback as 'fantastic,' rather than demanding an immediate overhaul. This approach is more welcoming and encourages a collaborative spirit – highlighting that improvement is a process, not a criticism. The incorrect options either focus solely on technical debt (too harsh) or fail to acknowledge the positive initial contribution.
11 / 26
Alex, a junior developer on the OpenSourceFramework project, submitted a pull request to fix a minor bug in the authentication module. The code was functionally correct but lacked sufficient documentation and followed outdated coding conventions. During a code review discussion on Slack, several senior members pointed out these issues, offering suggestions for improvement. Which of the following responses from the lead maintainer, Ben, best demonstrates proactive community building? 'Thanks for flagging this, Alex! We're always looking to improve our codebase and appreciate you bringing these points to our attention. Could you please address the documentation gaps and update your style guide to align with our project standards?'
This response is appropriate because it directly addresses the identified issues (documentation gaps and style guide alignment) while maintaining a professional and constructive tone. Crucially, it acknowledges Alex's effort—the 'appreciate you bringing these points to our attention' phrase demonstrates recognition and encourages continued engagement. The other options either lack specific guidance or adopt an unnecessarily critical approach which could be demotivating for new contributors.
12 / 26
Liam, a new contributor to the OpenSourceData project, has submitted a pull request containing a clever optimization for data processing. However, his commit message lacks context – it simply states 'Optimized'. The core maintainer, Maria, responds with:
'Great find, Liam! This is a valuable improvement. Could you add a brief description of the optimization and how it addresses the original problem in the commit message? Also, please include links to any relevant documentation or discussions.'This question tests understanding of effective community engagement. Option 1 misinterprets a request for context as overly demanding. Option 2 incorrectly frames Maria's response as verbose; she's simply seeking clarity to understand the *value* of the change. Option 4 best reflects a proactive approach – encouraging further dialogue and demonstrating that Liam's work is valued within the community, fostering a welcoming environment for questions and discussion. The key here is not just receiving feedback but actively building on it.
13 / 26
ProjectX is a popular open-source library for image processing. A new contributor, Rohan, submits a PR to fix a performance bottleneck in the resizing function. The code works correctly and significantly improves speed, but his PR description only includes a brief 'Fixed performance issue' message and doesn't mention the specific changes or any testing he performed. The lead maintainer, Sarah, responds with:
'Thanks for this, Rohan! Great to see you tackling a real problem. We appreciate your contribution.'
Which of the following actions best exemplifies community building in this scenario?The correct answer highlights that Sarah's response is sufficient—it acknowledges Rohan's contribution and subtly encourages further engagement. The other options represent missed opportunities for community building. Asking for a detailed report would be overly demanding at this early stage, and immediately merging without context could lead to issues down the line. A brief acknowledgment combined with an open invitation to continue contributing builds rapport and shows Rohan his work is valued.
14 / 26
Sarah, a new contributor, has submitted a PR to the AwesomeLib project. The code is functionally correct but uses a slightly outdated API version and lacks clear comments explaining its purpose. David, one of the core maintainers, responds with:
'> Thanks for submitting this! We appreciate your contribution. Just updating to the latest API version and adding some comments would be fantastic.'
Which of these options best describes David's response in terms of community building?David's response demonstrates key community-building behaviors. He acknowledges Sarah's effort (positive reinforcement), but importantly, he frames the feedback as 'fantastic,' rather than demanding an immediate overhaul. This approach is more welcoming and encourages a collaborative spirit – highlighting that improvement is a process, not a criticism. The incorrect options either focus solely on technical debt (too harsh) or fail to acknowledge the positive initial contribution.
15 / 26
Alex, a junior developer on the OpenSourceFramework project, submitted a pull request to fix a minor bug in the authentication module. The code was functionally correct but lacked sufficient documentation and followed outdated coding conventions. During a code review discussion on Slack, several senior members pointed out these issues, offering suggestions for improvement. Which of the following responses from the lead maintainer, Ben, best demonstrates proactive community building? 'Thanks for flagging this, Alex! We're always looking to improve our codebase and appreciate you bringing these points to our attention. Could you please address the documentation gaps and update your style guide to align with our project standards?'
This response is appropriate because it directly addresses the identified issues (documentation gaps and style guide alignment) while maintaining a professional and constructive tone. Crucially, it acknowledges Alex's effort—the 'appreciate you bringing these points to our attention' phrase demonstrates recognition and encourages continued engagement. The other options either lack specific guidance or adopt an unnecessarily critical approach which could be demotivating for new contributors.
16 / 26
Liam, a new contributor to the OpenSourceData project, has submitted a pull request containing a clever optimization for data processing. However, his commit message lacks context – it simply states 'Optimized'. The core maintainer, Maria, responds with:
'Great find, Liam! This is a valuable improvement. Could you add a brief description of the optimization and how it addresses the original problem in the commit message? Also, please include links to any relevant documentation or discussions.'This question tests understanding of effective community engagement. Option 1 misinterprets a request for context as overly demanding. Option 2 incorrectly frames Maria's response as verbose; she's simply seeking clarity to understand the *value* of the change. Option 4 best reflects a proactive approach – encouraging further dialogue and demonstrating that Liam's work is valued within the community, fostering a welcoming environment for questions and discussion. The key here is not just receiving feedback but actively building on it.
17 / 26
ProjectX is a popular open-source library for image processing. A new contributor, Rohan, submits a PR to fix a performance bottleneck in the resizing function. The code works correctly and significantly improves speed, but his PR description only includes a brief 'Fixed performance issue' message and doesn't mention the specific changes or any testing he performed. The lead maintainer, Sarah, responds with:
'Thanks for this, Rohan! Great to see you tackling a real problem. We appreciate your contribution.'
Which of the following actions best exemplifies community building in this scenario?The correct answer highlights that Sarah's response is sufficient—it acknowledges Rohan's contribution and subtly encourages further engagement. The other options represent missed opportunities for community building. Asking for a detailed report would be overly demanding at this early stage, and immediately merging without context could lead to issues down the line. A brief acknowledgment combined with an open invitation to continue contributing builds rapport and shows Rohan his work is valued.
18 / 26
Sarah, a new contributor, has submitted a PR to the AwesomeLib project. The code is functionally correct but uses a slightly outdated API version and lacks clear comments explaining its purpose. David, one of the core maintainers, responds with:
'> Thanks for submitting this! We appreciate your contribution. Just updating to the latest API version and adding some comments would be fantastic.'
Which of these options best describes David's response in terms of community building?David's response demonstrates key community-building behaviors. He acknowledges Sarah's effort (positive reinforcement), but importantly, he frames the feedback as 'fantastic,' rather than demanding an immediate overhaul. This approach is more welcoming and encourages a collaborative spirit – highlighting that improvement is a process, not a criticism. The incorrect options either focus solely on technical debt (too harsh) or fail to acknowledge the positive initial contribution.
19 / 26
Alex, a junior developer on the OpenSourceFramework project, submitted a pull request to fix a minor bug in the authentication module. The code was functionally correct but lacked sufficient documentation and followed outdated coding conventions. During a code review discussion on Slack, several senior members pointed out these issues, offering suggestions for improvement. Which of the following responses from the lead maintainer, Ben, best demonstrates proactive community building? 'Thanks for flagging this, Alex! We're always looking to improve our codebase and appreciate you bringing these points to our attention. Could you please address the documentation gaps and update your style guide to align with our project standards?'
This response is appropriate because it directly addresses the identified issues (documentation gaps and style guide alignment) while maintaining a professional and constructive tone. Crucially, it acknowledges Alex's effort—the 'appreciate you bringing these points to our attention' phrase demonstrates recognition and encourages continued engagement. The other options either lack specific guidance or adopt an unnecessarily critical approach which could be demotivating for new contributors.
20 / 26
Liam, a new contributor to the OpenSourceData project, has submitted a pull request containing a clever optimization for data processing. However, his commit message lacks context – it simply states 'Optimized'. The core maintainer, Maria, responds with:
'Great find, Liam! This is a valuable improvement. Could you add a brief description of the optimization and how it addresses the original problem in the commit message? Also, please include links to any relevant documentation or discussions.'This question tests understanding of effective community engagement. Option 1 misinterprets a request for context as overly demanding. Option 2 incorrectly frames Maria's response as verbose; she's simply seeking clarity to understand the *value* of the change. Option 4 best reflects a proactive approach – encouraging further dialogue and demonstrating that Liam's work is valued within the community, fostering a welcoming environment for questions and discussion. The key here is not just receiving feedback but actively building on it.
21 / 26
ProjectX is a popular open-source library for image processing. A new contributor, Rohan, submits a PR to fix a performance bottleneck in the resizing function. The code works correctly and significantly improves speed, but his PR description only includes a brief 'Fixed performance issue' message and doesn't mention the specific changes or any testing he performed. The lead maintainer, Sarah, responds with:
'Thanks for this, Rohan! Great to see you tackling a real problem. We appreciate your contribution.'
Which of the following actions best exemplifies community building in this scenario?The correct answer highlights that Sarah's response is sufficient—it acknowledges Rohan's contribution and subtly encourages further engagement. The other options represent missed opportunities for community building. Asking for a detailed report would be overly demanding at this early stage, and immediately merging without context could lead to issues down the line. A brief acknowledgment combined with an open invitation to continue contributing builds rapport and shows Rohan his work is valued.
22 / 26
During a code review of Maya's pull request for the `UserSession` module, David comments: 'This change introduces a potential race condition. We should add explicit locking to prevent data corruption.' Which of the following best describes David's intention?
David is highlighting a critical concern: a race condition. Race conditions occur when multiple threads or processes access and modify shared data concurrently without proper synchronization. His suggestion of 'explicit locking' is the standard approach to mitigate this risk, ensuring that only one thread can access the resource at a time. The other options misinterpret his feedback – it's not about style or test cases.
23 / 26
In a Slack channel dedicated to the `StreamProcessor` project, Ben writes: 'Hey team, just submitted a fix for that memory leak we identified. Pull request is here: [link]'. What's the *most* effective follow-up message from Maria to ensure thorough review?
Maria is focusing on ensuring the review process is complete. While load testing is valuable, a brief summary in the PR description provides context for reviewers – they don't need to dig through the code to understand *what* was fixed. Merging without further discussion is insufficient and updating documentation should be handled by a dedicated task.
24 / 26
When crafting a pull request description for a change to the `DataValidator` library, what's the *primary* purpose of including details about the 'motivation' behind the change?
The motivation is crucial for reviewers to understand *why* the change was made. It helps them assess if the solution addresses the underlying problem effectively and whether it aligns with the overall goals of the library. Simply stating 'fixed a bug' isn't enough; explaining the root cause ensures the fix is robust.
25 / 26
"Okay team, let's quickly catch up. Sarah reported she spent yesterday investigating performance issues in the `ReportGenerator` module and identified a slow query. She's currently working on optimizing it. Liam is continuing his work on the new UI component library. David is finalizing the documentation for the authentication service."
This is a typical stand-up update. Sarah's report needs immediate attention – she identified a critical issue and is actively working on it. The team's response should be supportive and focused on facilitating her progress, not shifting priorities or scheduling lengthy meetings unless absolutely necessary.
26 / 26
The `OpenSourceTracker` API returns the following JSON response when you request information about a contributor's activity:
```json{
"contributorId": "user123",
"commits": [{"timestamp": "2024-10-26T10:00:00Z", "repository": "ProjectX", "message": "Fixed a bug in the resizing function"}, {"timestamp": "2024-10-27T14:30:00Z", "repository": "AwesomeLib", "message": "Added new UI component"}],
"issues": [{"number": 15, "title": "Performance optimization", "status": "closed"}]
}```
What does the `status` field in the 'issues' array *indicate*?
The `status` field in this response indicates that the issue (number 15) was successfully resolved. The value 'closed' signifies that the problem has been addressed and the issue is no longer active. This is a common convention for tracking issues within an open-source project.
Frequently Asked Questions
What does the "Open Source Community Building" exercise practise?
Practice vocabulary for growing open source contributor communities, writing welcoming documentation, and onboarding new contributors. 5 exercises.
How many questions are in this exercise?
This exercise has 26 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 Conference & Community 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 "Open Source Community Building" part of a larger series?
Yes — it's one exercise in the Conference & Community 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 Conference & Community category page for related exercises, or browse the main Exercises hub for other IT English topics.