What: Update TOC Due Diligence guide with recent changes cncf#1503 #1508
+115
−40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Why: * the TOC has fielded feedback from maintainers and TOC members, implemented changes to address issues, and needs to update our docs to reflect this. This change address the need by: * re-writing the triage to align with current process * calling out the adopter form for adopter interview collection * detail process for projects not yet ready to move * linking the adopter interview form in the process/README * updating process/README to inform on triaging and not-ready applications Signed-off-by: Emily Fox <[email protected]>
dims
reviewed
Dec 13, 2024
dims
reviewed
Dec 13, 2024
dims
reviewed
Dec 13, 2024
dims
reviewed
Dec 13, 2024
operations/dd-toc-guide.md
Outdated
| @@ -185,9 +236,9 @@ Evaluation summary is composed of two parts: the Criteria and the Adoption. The | |||
|
|
|||
| ## TOC Internal Review | |||
|
|
|||
| Once the TOC member has completed the Due Diligence, the TOC member tags the TOC on the PR for an TOC internal review. The TOC member should move the project's card on the [Appliction to Move Levels board](https://github.com/orgs/cncf/projects/27/views/9) to "TOC Review". | |||
| Once the TOC member has completed the Due Diligence, they should create a PR in their personal TOC repo and share the link with the TOC for review. The TOC member should move the project's card on the [Appliction to Move Levels board](https://github.com/orgs/cncf/projects/27/views/9) to "TOC Review". | |||
There was a problem hiding this comment.
create a PR in their personal TOC repo should be create a branch in their personal fork of the TOC repo with DD markdown file.
(Once there is consensus, the branch is used to create a PR in the main TOC repo)
linsun
reviewed
Dec 13, 2024
linsun
reviewed
Dec 13, 2024
| All TOC members are expected to assist in the triaging of project applications to move levels to ensure that when a TOC member is ready to be assigned, the project is ready to be evaluated with no immediate blockers that would inhibit or delay the TOC's engagement. | ||
|
|
||
| This light-weight triage/evaluation must cover the list below (it is not exhaustive and is a minimum triage set from the [incubation template retrieved 12 DEC 2025](https://github.com/cncf/toc/blob/c2943ffc98064dd88e9ef9c4afd5a8856898942f/.github/ISSUE_TEMPLATE/template-incubation-application.md)): | ||
| * Adoption Assertion includes the Adopters file link, and the project has an entry in the Adopter's form responses to provide 5-7 adopters to reach out to. |
There was a problem hiding this comment.
Where would the project specify this info? Got a link for the Adopter's form?
There was a problem hiding this comment.
I've added this as a modification to the application template update issue. I don't think we get a UUID from the form for them to provide so right now we have no auditable trail beyond manually looking for the entry in the form responses. CC @mrbobbytables in case there are some ideas bouncing around about how we could do this.
linsun
reviewed
Dec 13, 2024
Signed-off-by: Emily Fox <[email protected]>
angellk
requested changes
Dec 19, 2024
operations/dd-toc-guide.md
Outdated
| ### Kicking off the due diligence | ||
|
|
||
| Once the project is assigned a TOC member and the initial evaluation looks good to proceed, the TOC member engages the project's maintainers or leadership group to kick off the due diligence. This can be done by commenting on the Issue, starting a slack channel (public or private), slack group direct message, email exchange, or thread in the project's primary communication channel. We strive to keep these discussions transparent and visible but should consider any potential sensitive issues that come about as a result of the review (resolution of vulnerabilities for instance). | ||
| Once the project is assigned to the TOC member(s), the TOC member(s) engages the project's maintainers or leadership group to kick off the due diligence. This can be done by commenting on the Issue, starting a slack channel (public or private), slack group direct message, email exchange, or thread in the project's primary communication channel. We strive to keep these discussions transparent and visible but should consider any potential sensitive issues that come about as a result of the review (resolution of vulnerabilities for instance). |
There was a problem hiding this comment.
add:
Any form of communication must include two members of CNCF staff to ensure consistency and continuity throughout the process.
Signed-off-by: Emily Fox <[email protected]>
angellk
approved these changes
Jan 6, 2025
|
Multiple TOC reviews and major comments resolved. Merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
This change address the need by: