Prepare Repo for a move to kubernetes-sigs about cluster-api-ipam-provider-in-cluster HOT 6 CLOSED

I checked licenses. Dependencies only have MIT, ISC, BSD-3-Clause, BSD-2-Clause and Apache 2.0 according to make license-report (aka. go-licenses). All of those should be fine.

The next step in the process would be to open an issue in k/org, but we should probably talk to sig-cluster-lifecycle leads again before we do that.

@fabriziopandini @CecileRobertMichon (cc @vincepri)
I see that this was brought up in a SIG meeting (which I missed, unfortunately) already. Was this accepted as a project for sig-cluster-lifecycle? Would you like some further discussion in the next meeting, or is async sufficient?
Is there anything we should add/change before moving the repository (e.g. approvers; we'll add more after some people have joined kubernetes-sigs)?

Some context: In the IPAM proposal I suggested to have at least one provider in kubernetes-sigs that can serve as a reference. In addition VMware has put in quite a bit of work, and it would feel better if it didn't live in the telekom org.
We've had a brief discussion in one of the CAPI meetings on whether we want to include it in the core cluster-api repository. We ultimately decided against it, since releasing is a little easier, and to decouple them from CAPI releases, since frequency might be a little lower.

from cluster-api-ipam-provider-in-cluster.

+1 from my side as well

This was brought up at the SIG office hours on 4/4 and there were no objections

from cluster-api-ipam-provider-in-cluster.

Additions of the standard Kubernetes header to code created by the contributors can occur post-transfer, but should ideally occur shortly thereafter.

Can we do this Pre-Move?

@adobley @schrej would it be possible for you to do this pre-move? 🙏

It's just cumbersome to track that the boilerplate has been added to all files after repo transfer. Easier if it's done pre-move.

from cluster-api-ipam-provider-in-cluster.

@schrej I'm +1 for the move, but given that folks got a little bit distracted by KubeCon, I suggest making a quick check via a ping to leads in the SIG channel

from cluster-api-ipam-provider-in-cluster.

@nikhita Boilerplate is in! There is a make verify-boilerplate (copied from k-sigs/cluster-api) make task in case you want to verify yourself, we don't have CI for it yet.

from cluster-api-ipam-provider-in-cluster.

Seems like we checked off all the tasks and the repo is moved. Closing this, but feel free to reopen if I'm overlooking something.

from cluster-api-ipam-provider-in-cluster.