Archive inactive Kubeflow repos

[animeshsingh]

There are multiple repos in the Kubeflow github organization where no code is being checked in. We shall identify and archive and/or move those repos. I will follow up with a subset of the list, and then we can expand from there.

[thesuperzapper]

@animeshsingh @Bobgy please list the repos to archive when you are ready

[animeshsingh]

https://github.com/kubeflow/metadata
https://github.com/kubeflow/fairing
https://github.com/kubeflow/triage-issues
https://github.com/kubeflow/reporting
https://github.com/kubeflow/marketing-materials
https://github.com/kubeflow/batch-predict
https://github.com/kubeflow/example-seldon
https://github.com/kubeflow/homebrew-core

[Bobgy]

Not sure about fairing, @jinchihe said he wanted to keep maintaining it.

Currently, WGs are paused for expansion of scope. So shall we reconsider that later

[Bobgy]

https://github.com/kubeflow/kubebench
Is this ready to archive? @kubeflow/wg-training-leads

[Bobgy]

https://github.com/kubeflow/frontend
KFP should move its content to KFP repo, then it can be archived

[Bobgy]

https://github.com/kubeflow/features

[gaocegege]

https://github.com/kubeflow/kubebench
Is this ready to archive? @kubeflow/wg-training-leads

cc @xyhuang

[gaocegege]

https://github.com/kubeflow/caffe2-operator

[gaocegege]

https://github.com/kubeflow/chainer-operator

Is it ready to archive?

@everpeace

[thesuperzapper]

Here is my reading of the final list to be actioned in the next few days.

Please like if you agree, or comment if you disagree.

To DELETE:

• https://github.com/kubeflow/fastpages
• https://github.com/kubeflow/features
• https://github.com/kubeflow/frontend (move content to kubeflow/pipelines)
• https://github.com/kubeflow/homebrew-cask
• https://github.com/kubeflow/homebrew-core
• https://github.com/kubeflow/marketing-materials (move content to kubeflow/community)
• https://github.com/kubeflow/triage-issues

To ARCHIVE:

• https://github.com/kubeflow/batch-predict
• https://github.com/kubeflow/example-seldon
• https://github.com/kubeflow/kubebench
• https://github.com/kubeflow/reporting

To DISCUSS:

@kubeflow/wg-training-leads, please confirm if actively maintained:

• https://github.com/kubeflow/caffe2-operator
• https://github.com/kubeflow/chainer-operator
• https://github.com/kubeflow/fate-operator

@kubeflow/wg-pipeline-leads, please confirm if actively maintained:

• https://github.com/kubeflow/kfp-tekton-backend (seems to be duplicate of the active kubeflow/kfp-tekton)
• https://github.com/kubeflow/metadata

@jinchihe / @xauthulei, please confirm if actively maintained:

• https://github.com/kubeflow/fairing

[terrytangyuan]

I am not sure about https://github.com/kubeflow/fate-operator. @gaocegege @jiahaoc1993 @LaynePeng Is this project still active?

@thesuperzapper Please archiving instead of deleting. We should never delete a repo.

[thesuperzapper]

@thesuperzapper Please archiving instead of deleting. We should never delete a repo.

The the ones I propose to delete are either forks (with no actual commits from us), or effectively empty repos.

[terrytangyuan]

What about this one? https://github.com/kubeflow/frontend Even though the content will be moved to another repo, there can be lessons learned from history/discussions as well as people's contributions/commits in the past.

[LaynePeng]

yes, it still active. And it is supporting the latest FATE. Furthermore, we are planning a big refactoring. Sent from iPhone 在 2021年3月3日，下午9:46，Yuan Tang <notifications@github.com> 写道：  I am not sure about https://github.com/kubeflow/fate-operator. @gaocegege<https://github.com/gaocegege> @jiahaoc1993<https://github.com/jiahaoc1993> @LaynePeng<https://github.com/LaynePeng> Is this project still active? @thesuperzapper<https://github.com/thesuperzapper> Please archiving instead of deleting. We should never delete a repo. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#479 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMRRELLOFSJ724RNWD54OLTBY4TXANCNFSM4XVON4CQ>.

[gaocegege]

https://github.com/kubeflow/fate-operator is active, please keep it.

[Bobgy]

https://github.com/kubeflow/frontend

Should be archived, there were real work there

[jinchihe]

personally I suggest keep Fairing, that's used and active. Thanks. @Bobgy

[stale]

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.

[Bobgy]

I'm going to act on the following list based on request, please comment ASAP if you disagree with anything:

To DELETE:

• https://github.com/kubeflow/fastpages
• https://github.com/kubeflow/features
• https://github.com/kubeflow/homebrew-cask
• https://github.com/kubeflow/homebrew-core
• https://github.com/kubeflow/triage-issues

To ARCHIVE:

• https://github.com/kubeflow/batch-predict
• https://github.com/kubeflow/example-seldon
• https://github.com/kubeflow/reporting
• https://github.com/kubeflow/code-intelligence (based on request: Archive kubeflow/code-intelligence Repo code-intelligence#208)
• https://github.com/kubeflow/caffe2-operator
• https://github.com/kubeflow/metadata
• https://github.com/kubeflow/chainer-operator
• https://github.com/kubeflow/pytorch-operator
• https://github.com/kubeflow/mxnet-operator
• https://github.com/kubeflow/xgboost-operator

WAITING:

• https://github.com/kubeflow/frontend (wait for moving content to kubeflow/pipelines, then archive)

To DISCUSS:

@kubeflow/project-steering-group, please confirm if moving to kubeflow/community?

https://github.com/kubeflow/marketing-materials (move content to kubeflow/community)

@xyhuang, please confirm if we can archive kubebench?

https://github.com/kubeflow/kubebench

@everpeace, please confirm if actively maintained:

https://github.com/kubeflow/chainer-operator

@animeshsingh @Tomcli, please confirm if actively maintained:

• https://github.com/kubeflow/kfp-tekton-backend (seems to be duplicate of the active kubeflow/kfp-tekton)

[jbottum]

@Bobgy the fastpages (https://github.com/kubeflow/fastpages) was set-up to help people post to blog.kubeflow.org. I think we might keep it.

[terrytangyuan]

@Bobgy the fastpages (https://github.com/kubeflow/fastpages) was set-up to help people post to blog.kubeflow.org. I think we might keep it.

@jbottum I don't think we need it anymore. The new repo for blog is in https://github.com/kubeflow/blog now.

[jbottum]

@Bobgy ok, the newer repo looks good. I agree.

[jlewi]

@Bobgy Any plan to follow up and archive some of the inactive repositories like kubeflow/code-intelligence?

[Tomcli]

https://github.com/kubeflow/kfp-tekton-backend can be archived since we migrated that repo to kfp-tekton already.

[zijianjoy]

https://github.com/kubeflow/frontend is ready for archive

[zijianjoy]

Hello everyone, I am targeting Nov 30th 2021 for archiving the repos mentioned in #479 (comment), as well as the deletion of repos in the same comment.

Please let me know if:

1. Any personnel you want to notify about the deletion/archive plan.
2. Any alternative you suggest people to use after certain repo is archived.
3. Any change you want to make for the deletion/archive plan.

Thank you so much!

[terrytangyuan]

@zijianjoy The Training WG has added archival notice and decided to archive operator repos for PyTorch, XGBoost, and MXNet. Could you archive these repos as well? Thanks. See context in kubeflow/training-operator#1423

[zijianjoy]

Hello @terrytangyuan , sounds good to me for archiving XGBoost, MXNet, PyTorch operators repos.

[everpeace]

Hi, @Bobgy. sorry for the late response. https://github.com/kubeflow/chainer-operator is not maintained actively anymore. please go archive it.

[zijianjoy]

Hello @everpeace, would you like to put on deprecation notice on README.md file for chainer-operator using format https://github.com/kubeflow/metadata#warning-kubeflowmetadata-is-not-maintained, and suggest an alternative for this tool? Please let me know once you have added this notice, thank you!

[everpeace]

Please let me know once you have added this notice, thank you!

@zijianjoy I added a deprecation notice on chainer-operator repo.

[zijianjoy]

@everpeace Thank you! I have added chainer-operator repo to archive list

[zijianjoy]

Notification has been sent to kubeflow-discuss email list: https://groups.google.com/g/kubeflow-discuss/c/GZw4LsPfrcY

[terrytangyuan]

Thank you! @zijianjoy

[zijianjoy]

Hello everyone,

Quick update that I will be taking the action to deprecate inactive repos today.

Archive:

• https://github.com/kubeflow/batch-predict
• https://github.com/kubeflow/example-seldon
• https://github.com/kubeflow/reporting
• https://github.com/kubeflow/code-intelligence
• https://github.com/kubeflow/caffe2-operator
• https://github.com/kubeflow/metadata
• https://github.com/kubeflow/frontend
• https://github.com/kubeflow/pytorch-operator
• https://github.com/kubeflow/mxnet-operator
• https://github.com/kubeflow/xgboost-operator

Delete:

• https://github.com/kubeflow/fastpages
• https://github.com/kubeflow/features
• https://github.com/kubeflow/homebrew-cask
• https://github.com/kubeflow/homebrew-core
• https://github.com/kubeflow/triage-issues

[zijianjoy]

Update: The deprecation is finished. Thank you everyone for your help.

[Bobgy]

Thank you for driving this!

[thesuperzapper]

🎉

[theadactyl]

Thanks James!

…

On Wed, Dec 1, 2021 at 9:00 PM Mathew Wicks ***@***.***> wrote: 🎉 — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#479 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABREJVKB3GDLADYHGKUUXKTUO34NRANCNFSM4XVON4CQ> .