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.

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

Ownership for kubeflow/example? #845

Closed
Bobgy opened this issue Jan 26, 2021 · 3 comments
Closed

Ownership for kubeflow/example? #845

Bobgy opened this issue Jan 26, 2021 · 3 comments

Comments

@Bobgy
Copy link

Bobgy commented Jan 26, 2021

I'm no longer actively involved in this repository. I'm not sure what the current ownership structure is.

It doesn't look like this repo is currently owned by a WG:
https://github.com/kubeflow/community/blob/master/wgs.yaml

Which suggests to me it might be orphaned.
cc @kubeflow/project-steering-group

I would suggest starting a thread on the mailing list to figure out which WG owns this repository and if no WG owns it what to do about it.

Originally posted by @jlewi in #843 (comment)

@Bobgy
Copy link
Author

Bobgy commented Jan 26, 2021

/cc @jinchihe
Creating a separate issue to discuss this.

@davidspek
Copy link

Re-posting my thoughts from my comment on the PR:

It seems like some of the examples do contain OWNERS files. I think another route of action is that each example should belong to a WG, this way an example demonstrating serving would be owned by the serving WG. With this structure it would be possible to pull in the example folder from each upstream repo (such as pipelines or serving) and have them together in this repo, similar to how manifests works.

@stale
Copy link

stale bot commented Jun 2, 2021

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

@stale stale bot added the lifecycle/stale label Jun 2, 2021
@stale stale bot closed this as completed Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants