WG sponsorship for arena

[Bobgy]

Hi, with the same rationale as kubeflow/fairing#526

/kind process

Per the governance discussions. All projects need to find WG sponsorship or they will eventually be archived.

Opening this issue to begin discussions about what to do about arena

/cc @cheyang

[Bobgy]

/cc @kubeflow/project-steering-group

[Bobgy]

/assign @cheyang @wsxiaozhang @denverdino

[Bobgy]

Some possible paths forward:

• Find a WG that makes sense to sponsor Arena, but we are in a WG expansion pause window, because they were just formed and need some time to run smoothly on their own first. So I think you can consider this as an option, and we may revisit after several months.
• Fork to whatever your own choice of organization and continue the project there.
• Archive the repo.
• Propose a new WG, you may refer to guidelines here: https://github.com/kubeflow/community/blob/master/wgs/overview.md, but note we are in a temporary pause period too, to let current WGs focus on their goals.

We do not have a fixed date to reach a resolution yet, but recommend evaluating these options early.

[davidspek]

Arena and Fairing seem to be somewhat similar and both have discussions regarding what WG they will belong to. Maybe it is an idea to form a new WG with the 2 of them?

[gaocegege]

How about maintaining arena at Traning WG? @cheyang

[ChenYi015]

How about maintaining arena at Training WG?

@gaocegege What about creating a new WG for arena (like CLI WG?), for that arena can be used to submit training jobs, serving jobs and manage model versions .

[ChenYi015]

Hi @Bobgy , we would like to propose a new CLI WG to sponsor arena. I will raise a draft WG CLI PR to the community recently.

/cc @kubeflow/project-steering-group @cheyang @Syulin7

[github-actions]

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.