cncf
/
toc
mirror of https://github.com/cncf/toc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify dependencies (#388) 

* Clarify dependencies need to comply with IP policy
This commit is contained in:
Liz Rice 2020-03-23 17:27:57 +00:00 committed by GitHub
parent 4bb08c76e1
commit de7446cd7d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
PRINCIPLES.md
View File

@ -78,6 +78,8 @@ 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._
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”.
- Overlapping projects are ok, especially where they make significantly different design tradeoffs