Governance review request process

[aliok]

Let's set up a process for projects that ask our review of their governance.

Deliverables of this task that I can think of:

• [x] Issue template for governance review requests. Done: https://github.com/cncf/tag-contributor-strategy/pull/572

• [ ] Process setup and documented

  • [ ] What project members need to do (do self eval first, then ask for a review, then respond the TAG member questions, etc)
  • [ ] What TAG members need to do
  • ...

• [ ] Also update the self assessment guide with the information coming out of this work

[aliok]

We discussed how a process can look like in a meeting and here's our brainstorming:

0. Project creates an issue in TAG CS repository
   • Using a special GitHub issue type
   • GitHub issue template gives instructions
     • Self assessment template
     • Self assessment guide
1. Project maintainers do the self-evaluation, and send a PR to TAG in a special “self-evaluations” folder.
2. TAG members review self-evaluation, ask questions, but don’t alter. They merge when the project maintainers are happy with their self assessment.
   • TAG members might need to explicitly state that this is a self assessment and we’re happy to store these for projects.
3. TAG members do their own review, using the self-assessment as the basis. They open a PR with the “official” tag review.
4. Project (and sponsor) responds to eval (PR comments)
   • At this stage, we can wait for short fixes - things that can be fixed in a week.
   • But if there are bigger changes needed, we merge with the issues reported and later the project can ask for a new review.
   • With self evaluations though, we think issues would be identified earlier and there will be less time spent in this wait-for-fixes stage.
5. Revise evaluation, revise PR
6. Liaison (& sponsor?) approve PR

Notes:

• We wanted to separate the self assessment PR and the TAG review PR as:
  • We didn’t want to alter the self assessment output (the name suggests it is a more personal thing).
  • There are issues with revising the PR contents, for example for volunteer reviewers
• We didn’t want to use Google docs when interacting with projects because comments can be deleted and the whole thread will be vanished

Relevant Slack thread: https://cloud-native.slack.com/archives/CT6CWS1JN/p1694110297185549

[geekygirldawn]

What's the status of this issue @aliok

[aliok]

Some content: https://cloud-native.slack.com/archives/CT6CWS1JN/p1716296927853679