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

What: addressing the question on originating sponsor. 

Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
This commit is contained in:
Emily Fox 2022-07-12 11:49:37 -04:00
parent 0280db457c
commit 9637161a62
No known key found for this signature in database
GPG Key ID: 2B5E8B9A27758A8C
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
FAQ.md
View File

@ -56,7 +56,7 @@ Adopters of a CNCF project are any organization that successfully leverages that
Direct adopters of a project are responsible for the project's development, packaging, configuration, or deployment in their use of it. Transitive adopters of a project are not responsible for the project's development, packaging, configuration, or deployment, however they may receive the benefits that the project provides. In the case of the example above, the Service Provider's use of Kubernetes enables their customers to use Knative, which relies on Kubenertes as part of its architecture. However, if the Service Provider's implementation enables their customers to develop, package, configure, or deploy Kubernetes as part of the Knative offering, those customers are then also direct adopters.
The TOC’s intent in identifying adopters is to better understand the operational or production-level use of a given project (which can also be a specification) by its operators or users. We do this to ascertain the level of maturity the project has reached, its interactions with adopters, and its likelihood to continue growing within and supporting the ecosystem.
The TOC’s intent in identifying adopters is to better understand the operational or production-level use of a given project (which can also be a specification) by its operators or users. We do this to ascertain the level of maturity the project has reached, its interactions with adopters, and its likelihood to continue growing within and supporting the ecosystem. Original sponsoring organizations, if any, may be included in the ADOPTERS.md file. It is the discretion of the TOC to determine whether a given adopter, for the purposes of interviews, can provide quality feedback on where the project is and where it is going next in their use and interactions with the project.
[Cloud native](https://github.com/cncf/toc/blob/main/DEFINITION.md) project adopters may be any one of the following. Please note that any single company can fall under several categories at once. If that's the case, it should enumerate all that apply and only be listed once. For the purposes of identifying the adopters of a project, we encourage the use of `adopter` to include all of the below, if a project needs to identify the category of adopter we encourage them to use the convention provided below.
* A CNCF End-User member - Companies and organizations who are End-User members of the CNCF (https://www.cncf.io/enduser/ & https://landscape.cncf.io/card-mode?enduser=yes). TThis group is identified in the written form by the convention `End-User`, capitalizing the `E` in `End`, hyphenating the two words, and captializing the `U` in `User`.