WIP: root approver requirements

[juliusvonkohout]

Root Approver requirements

The goal of the requirements is to quantify the main pillars that we documented
above. The high level reasoning is that approvers should have lead efforts and
have expertise in the different processes and artefacts maintained in this repo
as well as be invested in the community of the WG.

• Need to be a root reviewer - Yes
• Have been a WG liaison for a KF release - Yes for the Security WG
• Has at least 3 substantial PRs merged for /common - TODO
  • I.e. updating the versions of Istio, Dex or Knative - TODO Rootless Kubeflow part one (istio-cni) #2455
  • I.e. update manifests to work with newer versions of kustomize TODO
• Has at least 2 substantial PRs merged for /testing - TODO
• Has at least 1 substantial PR merged for /proposals - TODO I think that https://github.com/kubeflow/manifests/blob/master/proposals/20220926-contrib-component-guidelines.md participation does not count
• Has been an active participant in issues and PRs for at least 3 months - Yes
• Has attended at least 50% of Manifests WG meetings - Yes

Checklist:

• Unit tests pass:
  Make sure you have installed kustomize == 3.2.1
  1. make generate-changed-only
  2. make test

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: juliusvonkohout
Once this PR has been reviewed and has the lgtm label, please assign yanniszark for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[juliusvonkohout]

closed in favor of #2337