add kubeflow-hub-team with Write to KF/model-registry#882
Merged
google-oss-prow[bot] merged 2 commits intoJan 15, 2026
Conversation
similarly to other Maintainers team on a per-repo basis, this one focused on the kubeflow/model-registry repo, also known as "Kubeflow Hub". Please note the intent of this team is indeed to focus only on this repository, so to enable the chore processes across the current list of OWNERS.approvers: https://github.com/kubeflow/model-registry/blob/272a5f6be87b258b9cecc1f2687a08748bb1fed8/OWNERS#L2C1-L10C14 specifically: - performing the Release process (https://github.com/kubeflow/model-registry/blob/272a5f6be87b258b9cecc1f2687a08748bb1fed8/RELEASE.md) - delegate wider access to Security reports at the time of writing, in pragmatic term, the above relies on a bus-factor of 2 (+1 one Manager role) so with aligning best practice in defining a team for the specific repo needs we standardadize across the Kubeflow community and provide complete ownership for all repo-related processes. Signed-off-by: tarilabs <matteo.mortari@gmail.com>
Comment on lines
+800
to
+808
| - Al-Pragliola | ||
| - andreyvelich | ||
| - ckadner | ||
| - ederign | ||
| - pboyd | ||
| - rareddy | ||
| - tarilabs | ||
| - Tomcli | ||
| - zijianjoy |
Member
There was a problem hiding this comment.
I think, you can remove myself @zijianjoy, and others from that team who are not involved in the Hub development at the moment
Signed-off-by: tarilabs <matteo.mortari@gmail.com>
5b17389 to
dfe1389
Compare
Member
andreyvelich
left a comment
There was a problem hiding this comment.
Thank you @tarilabs!
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andreyvelich The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
tarilabs
added a commit
to tarilabs/model-registry
that referenced
this pull request
Jan 19, 2026
see kubeflow/internal-acls#882 (comment) moving: - ckadner - Tomcli - zijianjoy as emeritus. Keeping andreyvelich being part of KSC for any special operations we may require Signed-off-by: Matteo Mortari <matteo.mortari@gmail.com>
8 tasks
google-oss-prow Bot
pushed a commit
to kubeflow/hub
that referenced
this pull request
Jan 20, 2026
* chore: maintenance of OWNERS files see kubeflow/internal-acls#882 (comment) moving: - ckadner - Tomcli - zijianjoy as emeritus. Keeping andreyvelich being part of KSC for any special operations we may require Signed-off-by: Matteo Mortari <matteo.mortari@gmail.com> * add GitHub workflow to check OWNERS files Add a simple workflow to annotate OWENERS file in case some entry in the file is not (yet?) reflected in the kubeflow-hub-team in the KF ACL. Make the workflow only annotate the file and non-blocking for PR merges. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Matteo Mortari <matteo.mortari@gmail.com> --------- Signed-off-by: Matteo Mortari <matteo.mortari@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
4 tasks
This file contains hidden or 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
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.
similarly to other Maintainers team on a per-repo basis, this one focused on the kubeflow/model-registry repo, also known as "Kubeflow Hub".
Please note the intent of this team is indeed to focus only on this repository, so to enable the chore processes across the current list of OWNERS.approvers: https://github.com/kubeflow/model-registry/blob/272a5f6be87b258b9cecc1f2687a08748bb1fed8/OWNERS#L2C1-L10C14
specifically:
at the time of writing, in pragmatic term, the above relies on a bus-factor of 2 (+1 one Manager role) so with aligning best practice in defining a team for the specific repo needs we standardadize across the Kubeflow community and provide complete ownership for all repo-related processes.
cc @kubeflow/kubeflow-steering-committee @andreyvelich