cluster-api-provider-bringyourownhost
cluster-api-provider-bringyourownhost copied to clipboard
Identify tasks for repo migration to kubernetes-sigs
- [ ] #368
- [ ] Token used by codecov also is based on current org (vmware-tanzu) -> get / update token
- [ ] #371
- [ ] as pointed out in the sig mailing list, we will change all copyright license headers from
VMware, Inc.
toThe Kubernetes Authors
. Refer this message. Refer to any existing copyright header - https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/134604ab96e2e52901dda1b6414de21e67674616/controllers/svcdiscovery_controller_intg_test.go#L1-L15 - [ ] https://github.com/vmware-tanzu/cluster-api-provider-bringyourownhost/issues/369
- [ ] https://github.com/vmware-tanzu/cluster-api-provider-bringyourownhost/issues/370
- [ ] Update badges on Readme.md and register on 3rd party sites as required.
After all the above are done (with Draft PRs), raise repo migration request here
I will start off with the first one:
Update go.mod reference and any other reference to vmware-tanzu in import statements
- [ ] Update badges on Readme.md and register on 3rd party sites as required.
- [ ] Update badges on Readme.md and register on 3rd party sites as required.
@NilanjanDaw Edit the main issue description itself. Will be easier to track all tasks.
Hi Team 😄 I was exploring the project and was curious if there were any updates for the repo migration to k8s-sigs?
Hey @pokearu, This is put on hold for the time being but we definitely aspire to migrate this over to k8s-sigs in the future.
Hey @pokearu, This is put on hold for the time being but we definitely aspire to migrate this over to k8s-sigs in the future.
Ah got it 👍 Thanks for the update.