Open Source Contributions: PR & Community Communication Phrases
5 exercises on open source communication phrases. Choose the most natural and professional option.
0 / 11 completed
1 / 11
You've discovered a bug in a popular open source library and want to report it professionally. What's the best opening line in your issue?
"I found a bug in X — when Y, Z happens" is the model bug report opener: it names the component, the trigger, and the symptom. This gives maintainers everything they need to triage without back-and-forth. Real examples: "I found a bug in the router — when the path ends with a trailing slash, the handler is called twice"; "Found a bug in the serialiser: Unicode characters above U+FFFF are corrupted on Windows." Options A/B are blunt and unhelpful. Option D is the most useless — it doesn't say what goes wrong, when, or where.
2 / 11
A maintainer has opened an issue for a feature. You want to express interest in contributing without over-committing. What do you say?
"Happy to take this on if there's still interest" is the polite open-source contribution opener. It signals enthusiasm without claiming ownership, checks that the issue is still active, and offers a small preview of your approach. Real examples: "Happy to take this on if there's interest — I'm thinking we handle it at the middleware level"; "Happy to take this on — would a PR with just the core change be useful, or do you want docs too?" Options B/C/D sound assertive but skip the collaborative check — the issue may already be assigned or stale.
3 / 11
Before writing code, you want to confirm the maintainer would welcome a contribution. What do you ask?
"Would a PR be welcome?" is the canonical open-source etiquette phrase. It respects maintainer time (they don't have to review unwanted PRs) and shows you're aware that contributions have a cost. Adding "fits the project direction" demonstrates maturity. Real examples: "Would a PR be welcome? I don't want to spend a week on something that's out of scope"; "Would a PR be welcome for adding TypeScript types? Happy to do the work if it aligns with your roadmap." Options A-C are shorter but miss the context-setting that makes Option D so professional.
4 / 11
A reviewer has requested changes on your PR. You've made the changes and pushed. What do you comment?
"I've addressed the review comments in the latest push" is the professional re-review request. It confirms you acted on the feedback, summarises what specifically changed, and invites a second look without being demanding. Real examples: "Addressed all comments in the latest push — the main change was splitting the god class into three smaller ones"; "I've addressed the review comments — I also added a CHANGELOG entry as suggested." Option A is too terse. Option C sounds slightly demanding. Option D ("PTAL" = Please Take Another Look) is a valid shorthand but provides no summary of what changed.
5 / 11
A maintainer says they prefer contributors to discuss proposals before submitting code. How do you correctly respond when starting a new contribution?
"Should I open an issue first?" is the correct issue-first etiquette question. It shows you've read the contributing guidelines and understand the process. In many projects, an accepted design in an issue prevents wasted work on rejected PRs. Real examples: "Should I open an issue first, or is there already one tracking this?"; "Happy to open an issue outlining the approach before writing any code — let me know if you'd prefer that." Option B creates parallel work unnecessarily. Option C is exactly the attitude contributing guides warn against. Option D asks where, not whether — skips the key question.
6 / 11
Alice, a junior developer, has submitted a PR to the AwesomeLib project. The reviewer, Bob, comments: 'This is good work, but could you please explain your reasoning for this approach?' What's the most appropriate response for Alice to add to her comment?
The goal here is collaborative problem-solving. Option 2 demonstrates a willingness to explain her thought process, which is crucial in open source. Options 1 and 4 are too dismissive or simply polite but don't address the reviewer's request for justification. Option 3 is also good, but option 2 directly answers the question.
7 / 11
Charlie, a contributor to the ReactX project, has submitted a PR proposing a new hook. The reviewer, David, replies: 'Thanks for this! It's a solid start, but could you add some tests to cover the edge cases?' What's the most helpful response to David?
The reviewer specifically asked for tests. Acknowledging that the PR is a 'solid start' but highlighting the need for a test suite directly addresses the request and demonstrates understanding of best practices for open-source contributions. Options A, B, and C introduce irrelevant concerns.
8 / 11
Sarah is drafting a Slack message to announce her intention to contribute code to the Kubernetes project. She wants to be polite and collaborative. Which of the following messages would be most effective?
A good Slack message for announcing a contribution should clearly state your intention and invite collaboration. Option 3 – 'a clear call to action' (e.g., asking if there are specific areas where you can help) is the most proactive and helpful. The other options either lack clarity or use an inappropriate tone.
9 / 11
You've spent two days working on a feature for the Apache Kafka project. During a standup meeting, your team lead asks: 'What's the status of your PR?' You respond with: 'I'm still debugging some issues and haven't merged it yet.' What's the best way to elaborate?
Standups are about providing a brief update on progress and any roadblocks. Simply stating you're 'still debugging' isn't sufficient. You need to provide specific details about the issues you've encountered (e.g., 'I'm struggling with concurrency issues related to consumer offsets') so the team can offer assistance or guidance.
10 / 11
Emily has submitted a PR to the TensorFlow project. The reviewer, Frank, comments: 'This implementation is efficient, but could you refactor it using functional programming principles?' What's the most appropriate response?
Frank has offered a specific suggestion (functional programming). Ignoring it or dismissing it is unhelpful. A good response acknowledges the feedback and indicates your willingness to explore alternative approaches – even if you don't immediately implement it. Saying 'I'll consider that' shows openness to collaboration.
11 / 11
You're preparing a PR description for a small change in the Node.js Express project. The reviewer, George, asks: 'Can you briefly summarize the problem this PR solves?' What's the best approach to structuring your description?
The reviewer specifically requested a summary. A concise description focusing on *what* problem the PR solves is crucial. Avoid lengthy technical details in the initial PR description; save those for the code itself and potentially the subsequent discussion. Focusing only on the code ignores the broader context.
What will I practise in "Open Source Contributions: PR & Community Communication Phrases"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 11 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 11 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 Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — 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 Phrasebook exercises?
See the Phrasebook 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.