@@ -72,9 +72,9 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
72
72
- [ ] Delete your shared WG calendar
73
73
- [ ] Move the existing WG directory into the archive in ` kubeflow/community `
74
74
- [ ] GitHub archiving/removing/other transactions:
75
- - [ ] Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubernetes org
75
+ - [ ] Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubeflow org
76
76
- [ ] Each subproject a WG owns must transfer ownership to a new WG, outside the project, or be retired
77
- - [ ] File an issue with kubernetes /org if there are multiple repos
77
+ - [ ] File an issue with kubeflow /org if there are multiple repos
78
78
- [ ] Retire or transfer any test-infra jobs or testgrid dashboards, if applicable, owned by the WG.
79
79
- [ ] Migrate/Remove/Deprecate any SIG/WG labels in labels.yaml
80
80
- [ ] Remove or rename any GitHub teams that refer to the WG
@@ -90,7 +90,7 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
90
90
[ wg-governance.md ] : wg-governance.md
91
91
[ WG charter process ] : wg-charter
92
92
[ wgs.yaml ] : /templates/wgs.yaml
93
- [ generator doc ] : https://github.com/kubernetes /community/tree/master/generator
93
+ [ generator doc ] : https://github.com/kubeflow /community/tree/master/generator
94
94
[ GitHub management ] : https://github.com/kubeflow/community/blob/master/how-to/github_admin.md
95
95
[ code of conduct ] : https://github.com/kubeflow/community/blob/master/CODE_OF_CONDUCT.md
96
96
[ GoogleGroups ] : https://github.com/kubeflow/community/blob/master/how-to/kubeflow_assets.md#mailing-list
0 commit comments