Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Owners file for kubeflow/metadata needs to be updated #1138

Closed
jlewi opened this issue Apr 28, 2020 · 4 comments
Closed

Owners file for kubeflow/metadata needs to be updated #1138

jlewi opened this issue Apr 28, 2020 · 4 comments
Labels
area/metadata kind/process lifecycle/stale priority/p2

Comments

@jlewi
Copy link
Contributor

jlewi commented Apr 28, 2020

The OWNERs file for metadata needs to be updated it looks like the current set of approvers is no longer up to date and responsive.

See #928
@jlewi jlewi added the kind/bug label Apr 28, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
kind/bug 0.71

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@jlewi jlewi mentioned this issue Apr 28, 2020
Merged
1 task
@jlewi
Copy link
Contributor Author

jlewi commented Apr 29, 2020

Discussion about metadata future is in kubeflow/metadata#225.
This is probably relevant figuring out who the OWNERs will be.

@stale
Copy link

stale bot commented Jul 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Aug 5, 2020

This issue has been closed due to inactivity.

@stale stale bot closed this as completed Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/metadata kind/process lifecycle/stale priority/p2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jlewi