Existing glossaries
- TheFLOSSary - the repo is not public anymore. Here is a fork TheFLOSSary
Our own glossary
Table of content
C
Compatibility (License compatibility)
License A is compatible with license B if the terms of the licenses do not conflict.
In practice you typically end up in a situation like this:
- You have a program, P, that you would like to distribute under the Apache-2.0 license, i.e. outbound license is Apache-2.0
- Your program uses the library M, which is licensed under MIT, i.e. MIT is the inbound license
This means you will be asking the question: Can I use component M in my program P?
This question can be answered by using Open Source Compliance resources and tools.
R
Resource (Open Source Compliance resource)
A resource with data that can be used to solve specific compliance problem. The resource can be in different forms, including web site, JSON file or a FAQ.
Examples:
-
OSADL’s license matrix, part of OSADL’s license checklist. The matrix contains data with compatibility status between two licenses.
-
Open Source Software Data Analytics Lab@PKU-SEI’s license matrix, part of RecLicense. The matrix contains data with compatibility status between two licenses.
More resources can be found here: Tooling and resources
T
Tools (Open Source Compliance tool)
A software solving a specific compliance problem. The software can be in different forms, including web ui, command line program and module/library.
Examples:
-
ScanCode - ScanCode detects licenses, copyrights, dependencies by “scanning code”
-
flict - Flict checks compatibility between licenses and also for projects.
More tools can be found here: Tooling and resources