Practice vocabulary for OSS license compliance: CLA, DCO, GPL copyleft, dual licensing, and the inbound equals outbound principle.
0 / 10 completed
1 / 10
What does CLA stand for and what is its purpose in OSS governance?
A CLA (Contributor License Agreement) is a legal document contributors sign granting the project (or foundation) rights to use, relicense, or distribute their contributions.
2 / 10
What is the DCO (Developer Certificate of Origin)?
The DCO is a lightweight alternative to a CLA. Contributors add a 'Signed-off-by' line to commits, certifying they have the right to submit the code under the project's license.
3 / 10
What is the 'inbound = outbound' principle in OSS licensing?
'Inbound = outbound' means contributions are accepted under the same license the project uses for distribution. This prevents license incompatibility and simplifies governance.
4 / 10
What is 'dual licensing' in open source?
Dual licensing releases software under two licenses simultaneously — typically an open source license (like GPL) for the community and a commercial license for companies that want to avoid copyleft obligations.
5 / 10
Why is GPL copyleft considered a 'risk' in some OSS governance contexts?
GPL copyleft requires that derivative works must also be licensed under GPL. For companies with proprietary products, incorporating GPL code can force them to open-source their entire codebase — a significant governance and legal risk.
6 / 10
During a code review of the 'ProjectPhoenix' library, Sarah notices a comment from Ben regarding the use of the Apache 2.0 license. He asks if the team has considered the implications of including the original GPLv3 source code within their project. Which statement best describes Ben's concern?
Ben's concern centers on the 'copyleft' nature of GPLv3. This means that any derivative works based on GPLv3 code must also be licensed under GPLv3, potentially forcing Sarah's team to open-source their entire project if they build upon it. Apache 2.0, being a more permissive license, does not have this requirement.
7 / 10
You're reviewing a Pull Request submitted by Alex for the 'NovaCore' API. The PR includes a modified version of the authentication module and a DCO (Developer Certificate of Origin) form has been attached. What is the primary purpose of this DCO?
The DCO's core function is to establish provenance. It's a digital oath that Alex takes, stating he hasn't made prior claims to the code and thus isn't infringing on existing copyrights. This mitigates legal risks for the project.
8 / 10
During a standup meeting, David explains that his team is using the 'CosmosDB' database in their new microservice. He mentions they are carefully considering the licensing terms to avoid potential issues. Which of the following best describes the 'inbound = outbound' principle related to open-source licenses?
The 'inbound = outbound' principle applies when you incorporate code licensed under a copyleft license (like GPL). The obligation to open-source your own code arises from the *incoming* use of that copyleft code. It's about reciprocal obligations – you receive freedom, so you must give it back.
9 / 10
The 'Stardust' project uses a 'dual licensing' model: an MIT license for the core engine and a GPLv3 license for any plugins developed by third-party contributors. Why might a project team choose this approach?
Dual licensing provides flexibility. The MIT license allows for commercial use without copyleft obligations, attracting businesses wanting to integrate the core engine. GPLv3 ensures community contributions remain open-source, balancing commercial interests with openness.
10 / 10
During a discussion about the 'Orion' project's license selection, Maria raises concerns about using GPLv2. She argues that it could pose a 'risk' to the project's long-term sustainability. What is the primary reason for this concern?
The risk associated with GPLv2 stems from its copyleft nature. This means that any derivative works based on GPLv2 code must also be licensed under GPLv2. This can restrict commercialization or modification of the code if a company wants to keep it proprietary – essentially, forcing them to open source their own work.
What will I practise in "License Compliance & Governance Vocabulary"?
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.