License Usage Scenario
License Usage Scenario
Repository for discussing license usage scenario.
Background
The project Automate FOSS License Compliance sets out, among other things to classify licenses in both human and machine readable way. As part of that project Glossary and Definitions was written containing the following text:
Another key element, to assess if the Licensee is in a Compliant state, is the Licensee’s scenario or context of use (“Usage Scenario”): given a specific Usage Scenario, a Licensee may or may not need specific Permissions, and therefore may or may not need to fulfill specific Conditions. When Open Source software Licenses are involved, if the context of use is the mere internal running of the program, there are generally no Conditions to fulfill, since the corresponding Permission is entirely unconditional.
At FOSDEM 2026 Fringe: FOSS license and security compliance tools workshop Fri, Jan. 30, 2026 several people engaged in discussions about:
- how we use a component
- how we provide a component, typically as part of a bigger work, to our users
- whether or not the componet has been modified
We hope that this place will be a good starting point for continued discussions and hopefully reaching conclusions.
Goal
Background
-
A common vocabulary to use when communicating with users, customers, suppliers, developers, license compliance engineers and so on is crucial for avoiding mistakes.
-
A common interpretation of data, e.g. as provided in SBoMs, is crucial when developing compliance tools.
With the efforts here we hope to:
- identify usage scenarios
- harmonize or map usage scenarios between various resources
Existing resources
References
Sponsors
Automate FOSS License Compliance was funded through the NGI0 Core Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101092990
About this page
This page was automatically generated from ssh://git@codeberg.org/software-compliance-org/license-usage-scenario/src/branch/main/README.md