chore: clean up owners file

[jonburdo]

Note

Going forward, changes to OWNERS for the Kubeflow Hub team should be made to both of these files:

• kubeflow/model-registry root OWNERS file:
  https://github.com/kubeflow/model-registry/blob/main/OWNERS
• kubeflow/sdk sub-module file kubeflow/hub/OWNERS:
  https://github.com/kubeflow/sdk/blob/main/kubeflow/hub/OWNERS

Description

This cleans up the root OWNERS file to follow best-practices and more closely match the state of the kubeflow sdk file: https://github.com/kubeflow/sdk/blob/main/kubeflow/hub/OWNERS

Specifically this does the following:

• remove duplicate reviewers entries which are also in approvers:
  • andreyvelich
  • Al-Pragliola
  • pboyd

Also see: kubeflow/sdk#244 (comment)

How Has This Been Tested?

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages
• Automated tests are provided as part of the PR for major new functionalities; testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.
• For first time contributors: Please reach out to the Reviewers to ensure all tests are being run, ensuring the label ok-to-test has been added to the PR.

If you have UI changes

• The developer has added tests or explained why testing cannot be added.
• Included any necessary screenshots or gifs if it was a UI change.
• Verify that UI/UX changes conform the UX guidelines for Kubeflow.

[pboyd]

/lgtm

[tarilabs]

I had left Andrey with the comment to have someone outside of company bus factor in. If you notice the yaml comment, is used in the GH to check consistency with the ACL, which imho is the most important.

[jonburdo]

I had left Andrey with the comment to have someone outside of company bus factor in. If you notice the yaml comment, is used in the GH to check consistency with the ACL, which imho is the most important.

Definitely agree, good catch! Rebased and updated so it's just to remove duplicates

[Al-Pragliola]

/lgtm

[tarilabs]

I've noticed the added "note" at the beginning of this PR

I'd say for this iteration, this PR can move on.

I'd recommend adding a "linter" like already done for the KF/internal-acls to verify the Reviewer/Approver are "linted" to that files too :)

[tarilabs]

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tarilabs

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [tarilabs]

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