Practise courteous open-source phrases: welcoming first PRs, requesting changes kindly, declining politely, and thanking contributors.
0 / 10 completed
1 / 10
Which reply best welcomes a first-time contributor?
A warm acknowledgement encourages newcomers to keep contributing, which is vital for a healthy project community.
2 / 10
Which way of requesting changes stays constructive?
Specific, reasoned suggestions plus an offer to help guide the contributor without making them feel attacked.
3 / 10
Which message declines a PR respectfully?
Explaining the reason and thanking the contributor preserves goodwill even when the answer is no.
4 / 10
Which response models good etiquette when a contributor is frustrated?
Acknowledging feelings and offering reasoning de-escalates tension and keeps the collaboration civil per the code of conduct.
5 / 10
After merging, which closing line is good etiquette?
Thanking the contributor and noting when their work ships makes them feel valued and likely to return.
6 / 10
Sarah, a new contributor, asks: 'I'm not sure where to start with this feature. Could you point me to the relevant parts of the codebase and any existing documentation?' Which response best demonstrates good etiquette?
Option 1 offers a helpful and supportive response by guiding Sarah to the necessary resources. Options 2 provides specific assistance and links to documentation, demonstrating proactive support. Options 3 and 4 are dismissive and unhelpful, failing to acknowledge Sarah's request for guidance.
7 / 10
David sends a comment on a code review: 'This is terrible. You should rewrite the entire thing.' Which of the following statements best exemplifies constructive feedback?
Option 1 demonstrates a lack of empathy and constructive criticism. Option 2 encourages a dialogue about specific issues, focusing on improvement rather than simply stating dissatisfaction. Options 3 and 4 are overly harsh and unproductive.
8 / 10
"I've spent hours on this PR, and you're rejecting it without explanation! This is completely unacceptable."
Option 0 acknowledges the contributor's feelings while proposing a collaborative solution. It demonstrates empathy and encourages discussion. The other options dismiss the contributor's concerns or escalate the situation unnecessarily.
9 / 10
Maria writes in a Slack channel: 'This feature is broken! Fix it ASAP!' What's the most appropriate response?
Option 0 requests specific information to help Maria understand the problem and facilitates troubleshooting. It demonstrates a proactive approach to resolving the issue. Options 1 and 2 are dismissive, while option 3 minimizes the severity of the situation.
10 / 10
After successfully merging a PR, John sends a message to the team: 'Thanks for the reviews!'. Which of the following is the most appropriate concluding statement?
Option 1 expresses gratitude and acknowledges the contributions of the team while transitioning to the next step. It maintains a professional and collaborative tone. Options 2 is overly self-focused, while option 3 is rude and inappropriate.
What will I practise in "Maintainer–Contributor Etiquette"?
This module focuses on Open Source Contribution — 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 Open Source Contribution exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around open source contribution — 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 Open Source Contribution exercises?
See the Open Source Contribution 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.