Community: WG-Kubeadm-adoption has moved to a subproject

Created on 31 Jan 2019  路  11Comments  路  Source: kubernetes/community

This WG served it's purpose and hasn't had updated notes since October 2017.

Please follow: https://github.com/kubernetes/community/blob/master/sig-governance.md#sigwg-retirement

I think most of these don't apply since it's basically all just SIG Cluster Lifecycle at this point and has kubeadm as a subproject. We should howerver make sure we're not leaving zombie working groups in the repo.

/assign @kubernetes/sig-cluster-lifecycle

kinfeature sicluster-lifecycle sicontributor-experience

All 11 comments

+1
kubeadm went GA and this WG is no longer needed.

+1

It's a subproject for a long time now.

+1

fwiw, it's not really sunsetting. It was restructured year+ ago but this is a leftover.

It was restructured year+ ago but this is a leftover.

Agreed, we transferred it to the kubeadm Office Hours as part of the SIG as a subproject more than a year ago, but we just forgot to remove it from k/community. Thanks @castrojo let's fix it

Work with SIG Contributor Experience to:

ref @kubernetes/sig-contributor-experience-feature-requests
(don't know what exact team to tag for sunsetting...)

TODO list:

  • [x] Archive the mailing list/group

    • Not applicable, I don't remember we had one (not 100% sure though)

  • [x] Archive the leads mailing list/group

    • Not applicable, we never had one

  • [x] Archive the slack channel

    • Not applicable, we never had one

  • [x] Deactivate the group's Zoom license

    • Not applicable, we never had an own account, just used SIG Cluster Lifecycle's

  • [x] Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubernetes org

    • Not applicable, we never had our own repo

  • [x] File an issue with kubernetes/org if multiple repos that need to be retired

    • Not applicable, we never had our own repo

  • [x] Coordinate with SIG Testing on the following topics (if necessary)

    • Not applicable, we never had our own repo

  • [x] Clean up and remove all GitHub teams that refer to that SIG/WG

    • Not applicable, we never had any teams

  • [x] Migrate/Remove/Deprecate any SIG/WG labels in labels.yaml

    • TODO: wg/kubeadm-adoption needs to be removed

  • [x] Ensure that the YouTube Collaboration links are removed

    • TODO: I think I was added as a collaborator, and maybe @justinsb at the time. With the new automation and stuff, should our permissions be removed or preserved?

  • [x] Remove SIG Calendar and events from the community calendar

    • TODO: I think @justinsb sent the original invite, so he shall remove it

  • [x] Update sigs.yaml to reflect the removal of the SIG/WG

    • TODO: Somebody's gotta do it ;)

I believe I have now removed the calendar invite - let me know if anyone still has it!

/cc @parispittman

I've taken care of youtube, sigs.yaml and labels.yaml have a PR in flight, thanks everyone!

Thanks a lot @castrojo :clap:!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rlenferink picture rlenferink  路  4Comments

alouane picture alouane  路  4Comments

parispittman picture parispittman  路  3Comments

casusbelli picture casusbelli  路  4Comments

jamiehannaford picture jamiehannaford  路  3Comments