Archive WG Serving

[terrytangyuan]

See https://groups.google.com/a/kubernetes.io/g/dev/c/nDjMph1146A/m/z-T7POJQBQAJ for the announcement.

• Remove WG from sigs.yaml (this repo): Archive WG Serving #8848
• Slack for #wg-serving channel (?)
• Zoom accounts (?)
• Mailing list (?)

Anything else?

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[terrytangyuan]

cc @soltysh

[terrytangyuan]

We will hold off on deleting any YouTube and Zoom accounts for now until all subprojects (Gateway API Inference Extension and Inference Perf) have finished migration.

[palnabarun]

Anything else?

@terrytangyuan the steps for archival are documented in https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md#retirement

[terrytangyuan]

Thanks. Here’s the TODO list:

Steps:

• Send an email to dev@kubernetes.io and community@kubernetes.io alerting the community of your intentions to disband or merge. Done: https://groups.google.com/a/kubernetes.io/g/dev/c/nDjMph1146A/m/z-T7POJQBQAJ
• This kicks off the process for Contributor Experience’s community managers who will reach out and set an issue against kubernetes/community with exact next steps covered below. We can help walk through this when you get there. Most of this is covered in the same creation communication docs as above.
• Archive the member and lead/chair mailing lists/[GoogleGroups]
• Check the [slack-guidelines.md] for latest process on archiving the slack channel
• Deactivate the zoom license
• Delete your shared SIG/WG calendar
• Ensure that the [youtube-guidelines.md] links are removed and you've uploaded all SIG/WG meetings to date
• Move the existing SIG directory into the archive in kubernetes/community: Archive WG Serving #8848
• GitHub archiving/removing/other transactions:
  • Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubernetes org
  • Each subproject a SIG owns must transfer ownership to a new SIG, outside the project, or be retired
  • File an issue with kubernetes/org if there are multiple repos
  • Retire or transfer any test-infra jobs or testgrid dashboards, if applicable, owned by the SIG. Work with SIG-Testing on this.
  • Migrate/Remove/Deprecate any SIG/WG labels in labels.yaml; find instructions in [labels.md]
  • Remove or rename any GitHub teams that refer to the SIG
  • Update sigs.yaml to remove or rename

[terrytangyuan]

/reopen

[k8s-ci-robot]

@terrytangyuan: Reopened this issue.

Details

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[terrytangyuan]

The WG folder has been archived as part of #8848. We'll need help on the remaining items.

Please keep the Zoom account, WG calendar, and YouTube account for now until all subprojects have moved to their own accounts managed by corresponding SIGs.