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

Apply non-critical suggestions from code review 

suggestions are grammatical, layout, punctuation, or other minor changes that do not change the content.

Co-authored-by: Lin Sun <lin.sun@solo.io>
Co-authored-by: Kevin Wang <kevinwzf0126@gmail.com>
Signed-off-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
This commit is contained in:
Emily Fox 2024-03-04 17:51:33 -05:00 committed by GitHub
parent bb4104ba24
commit 3fa4b28bf2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.github/ISSUE_TEMPLATE/template-graduation-application.md vendored
View File

@ -15,7 +15,6 @@ Project points of contacts: $NAME, $EMAIL
### Adoption Assertion
_The project has been adopted by the following organizations in a testing and integration or production capacity:_
*
### Criteria

4
operations/toc-templates/template-kickoff-notes.md
View File

@ -24,8 +24,8 @@ _A list of 5-7 potential interviewees. The TOC member can record status changes
_This contains notes, observations, and discussion items. This document is shared_
### September check-in
* **DONE(waiting for merge)!** Non- Blocking OpenSSF badging (criteria is for graduation not incubation) - $SUB-PROJECT repo is showing 99%, the only outstanding item: The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) [contribution_requirements] .
* Looking over the contributing file (recommend linking this on the community contributor ladder as the initial starting point for potential contributors), it does not specify the requirements for acceptable contributions beyond DCO. You'll need to add a section that defines the top level acceptable contributions and links to the community repos acceptable contributions as appropriate.
* **DONE(waiting for merge)!** Non-Blocking OpenSSF badging (criteria is for graduation not incubation) - $SUB-PROJECT repo is showing 99%, the only outstanding item: The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) [contribution_requirements] .
* Looking over the contributing file (recommend linking this on the community contributor ladder as the initial starting point for potential contributors), it does not specify the requirements for acceptable contributions beyond Developer Certificate of Origin (DCO). You'll need to add a section that defines the top level acceptable contributions and links to the community repos acceptable contributions as appropriate.
### Kick off Meeting

4
process/README.md
View File

@ -10,7 +10,7 @@ CNCF Projects experience a project lifecycle that conveys their completion of a
The TOC defines 4 stages of the project lifecycle:
* **[Sandbox](sandbox.cncf.io)** - experimental or innovative projects that are early in their life
* **[Sandbox](https://sandbox.cncf.io)** - experimental or innovative projects that are early in their life
* **Incubation** - growing maturity projects that are on the precipice of "crossing the chasm"
* **Graduated** - highly mature, robust projects whose adopters have demonstrated their production-readiness by their deployment to production environments
* **[Archived](archiving.md)** - inactive or low activity projects that are no longer supported by the TOC or are not recommended for use due to a variety of factors (project specific)
@ -49,7 +49,7 @@ While the details of the process are described in detail further for Incubating
*Who: TOC Sponsor(s) and Project*
* The TOC will schedule time with the project to set expectations and layout out the process. The TOC will use the meeting notes document to capture blockers, recommendations, and other findings as they review the issue and the project's respositories, channels, release process, metrics, governance, and other sources of information that support the project's completion of the criteria. The TOC member will refer back to these notes to support their forumlation of the Due Diligence PR. The project is asked to identify 5-7 adopters for interviews.
* If the TOC sponsor(s) finds the project is not yet ready to move levels, they will re-engage the project discuss next steps, detail specific blockers that prevent the project from moving, and any actions that need completed but are non-blocking. The Application issue is updated with this summary once discussed the project and the issue is close.
* If the TOC sponsor(s) finds that the project is not yet ready to move levels, they will re-engage with the project to discuss next steps, detail specific blockers that prevent the project from moving, and any actions that need to be completed but are non-blocking. The Application issue is updated with this summary once the project is discussed.
#### Due Diligence creation or refresh
*Who: TOC Sponsor(s)*