Practice OSPO (Open Source Program Office) vocabulary: license policy, contribution guidelines, inbound vs outbound open source, usage reviews, and OSPO program management.
0 / 5 completed
1 / 5
What does OSPO stand for?
OSPO (Open Source Program Office) is the team or function within a company responsible for managing open source strategy — both consuming open source (inbound) and contributing to or releasing it (outbound).
2 / 5
'The OSPO ___ open source usage.' Which verb fits a compliance review function?
'Reviews' is the natural verb: the OSPO reviews which open source libraries the company uses, checking for license compatibility, security vulnerabilities, and policy adherence.
3 / 5
What is the difference between 'inbound' and 'outbound' open source?
Inbound open source = third-party OSS your company consumes (libraries, tools). Outbound open source = code your company releases to the public or contributes to external projects. The OSPO manages both.
4 / 5
'We have an approved open source ___ policy.' Which noun fits?
An 'open source license policy' defines which OSS licenses are approved for use in the company's products (e.g., MIT and Apache 2.0 are usually fine; GPL may be restricted for proprietary products).
5 / 5
'The OSPO manages our open source ___ guidelines.' Which noun fits contributing to external projects?
'Contribution guidelines' govern how employees can contribute to external open source projects — e.g., what approvals are needed, IP assignment rules, and which projects are pre-approved.