Merge branch 'cncf:main' into main

operations/toc-templates/template-adopter-questions.md

@@ -38,4 +38,16 @@ Expectations conveyance with interviewers: “I’ll record raw notes here, then
 
 13. What are the overall strengths of the project?
 
-14. Do you have any future plans regarding the project? More involvement, feature requests, expansion, etc.
+14. Do you have any future plans regarding the project? More involvement, feature requests, expansion, etc.
+
+### Maturity Level Survey
+
+The following set of questions goes beyond the scope of the specific project adoption.
+
+Their goal is to benefit from having access to CNCF project adopters and survey their understanding of the CNCF project maturity levels and any reliance on their meaning for decision making. This information should allow the TOC to better document maturity levels targeting adopters.
+
+1. Do you feel you have a good understanding on the meaning of each maturity level for CNCF projects?
+
+2. Is there information missing regarding the meaning of each different level?
+
+3. Do you rely on those levels internally in any way, and if yes how?

process/README.md

@@ -23,6 +23,10 @@ Projects may enter the CNCF either by applying as a sandbox project or applying
 
 Evaluting projects against the criteria does take some time and the TOC has recently modified the Due Diligence process to reduce duplication of work, streamline handoffs, and provide better transparency to the project and its adopters about its conformance and implementation of the criteria.
 
+##  Naming conventions for projects
+
+All CNCF projects are subject to the [Trademark Usage Policies](https://www.linuxfoundation.org/legal/trademark-usage) set by Linux Foundation. Specifically, new or incoming projects should avoid use existing trademarks in their proposed project names. In addition, if they are intending to use a popular prefix/suffix of an existing project (like "kube" or "k8s"), then they should consult the leadership group of the respective project to seek their approval and document the consensus reached. Existing projects are encouraged to document their naming guidelines to make this process smooth as well to avoid lengthy deliberation process for new project names.
+
 ### Project resources and guide posts
 
 The TOC, with support from the [Technical Advisory Groups](/tags/README.md), have a wide variety of resources available to assist projects.  Current and aspiring maintainers of cloud native projects can find a lot of information and templates on [contribute.cncf.io/maintainers](https://contribute.cncf.io/maintainers/). The TOC also maintains [project Guide Posts](../docs/project_guideposts.md) - a collection of guiding points that have assisted cloud native projects as they grow and mature in the ecosystem. These are not requirements for moving levels, those may be found in the respective application issue templates ([Incubation](../.github/ISSUE_TEMPLATE/template-incubation-application.md), [Graduation](../.github/ISSUE_TEMPLATE/template-graduation-application.md)). The [Guide Posts](../docs/project_guideposts.md) are a resources for projects to leverage that is beneficial in meeting or exceeding the criteria defined.