Ali Ok

In today's Governance WG meeting, we decided to continue with this work, instead of waiting the Project Moving Levels initiative to finish. We can always update the self evaluation guide...

Tasks: - Fix the TODOs in the current doc (https://github.com/cncf/tag-contributor-strategy/pull/520) - ~~Explain the process based on https://docs.google.com/document/d/1252lARpe1KYv_MIy4MHQpnRRyEs5LHOQoJ5JgOwksfs/edit?pli=1#heading=h.dobo4actnqfy:~~ - ~~Do a self assessment first~~ - ~~Then fill the governance review request...

We need to update this doc based on the check list. @jberkus can you give me a link to the check list?

It might be a better idea to start with a related task, [Create RELEASE.md template](https://github.com/cncf/tag-contributor-strategy/issues/535)

@divya-mohan0209 Based on your comment [here](https://github.com/cncf/tag-contributor-strategy/issues/535#issuecomment-1791851504), would you be interested in working on this document with us?

@thedevelopnik do you think this issue is still relevant?

Some notes: - This is more about the non-code duties that can exist in a technical project. - https://github.com/cncf/tag-contributor-strategy/issues/327 is more about projects/groups that are non-code by nature

Thanks @divya-mohan0209, your input would be great.

In Knative community, we're setting up an initiative to work with designers. The outcome would be: - Learning how to enable the designers - Finding out what designers can contribute...

I think there are a few different ideas in this discussion: #### 1. CNCF cross-project buddy system (the original post of my understanding) - 2 maintainers buddy up - To...