Formally document the IP Policy of the LoopBack Project, which may include:
- Supported licenses
- Copyright notices
- Exceptions granted by the board
The IP Policy must be within the constraints of https://github.com/openjs-foundation/cross-project-council/blob/845960f44870e731c1208497c154952a87468b8d/governance/IP_POLICY_GUIDANCE.md.
Git Repository licenses to check
We'll need to check the licenses of our Git Repositories to ensure they're compliant with the list from the OpenJS Foundation IP Policy Guidance document.
For those with incompatible licenses:
- If there's no DCO sign-offs, we can change the license immdiately
- If there's DCO sign-offs...
- If it's a StrongLoop/IBM maintainer or a maintainer that has signed the CLA, we can the change the license(?)
- If it's an active maintainer, get their permissions to change the license.
- If it's own outside contributor, we may need to get their permission to change the license(?)
- Otherwise, we may need to get an exception from the OpenJS Foundation.
A tick represents a compatible license and not outstanding issues,
see also: loopbackio/loopback-connector-sqlite3#10
Formally document the IP Policy of the LoopBack Project, which may include:
The IP Policy must be within the constraints of https://github.com/openjs-foundation/cross-project-council/blob/845960f44870e731c1208497c154952a87468b8d/governance/IP_POLICY_GUIDANCE.md.
Git Repository licenses to check
We'll need to check the licenses of our Git Repositories to ensure they're compliant with the list from the OpenJS Foundation IP Policy Guidance document.
For those with incompatible licenses:
A tick represents a compatible license and not outstanding issues,
see also: loopbackio/loopback-connector-sqlite3#10