PRINCIPLES.md: update link to license allowlist policy (cncf#479)

KjeldF · Jun 25, 2020 · 7e2ee40 · 7e2ee40
1 parent 136e7db
commit 7e2ee40
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/PRINCIPLES.md b/PRINCIPLES.md
@@ -78,7 +78,7 @@ Via the “no kingmakers” principle and “what is a project”, the CNCF may
 
 This means that the CNCF is not promoting a single, monolithic stack of technologies. 
 
-CNCF projects may have dependencies on other open source projects that comply with the [CNCF IP policy]( https://github.com/cncf/foundation/blob/master/whitelist-policy.md), which may be outside the CNCF. Widely-used dependencies are preferred; pluggable dependencies fit well with our principles but are not essential. _Examples: Kubernetes' dependency on etcd, which was not a CNCF project at the time Kubernetes was brought into the CNCF; CNI, which enables pluggable networking dependencies._ 
+CNCF projects may have dependencies on other open source projects that comply with the [CNCF IP policy](https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md), which may be outside the CNCF. Widely-used dependencies are preferred; pluggable dependencies fit well with our principles but are not essential. _Examples: Kubernetes' dependency on etcd, which was not a CNCF project at the time Kubernetes was brought into the CNCF; CNI, which enables pluggable networking dependencies._ 
 
 The CNCF is a badge of quality and velocity. CNCF projects should be on a path to being tools that users can trust, broadly work together, and that meet other cloud native criteria. But the CNCF badge does not mean “this is the standard tool”.