Moving to Kubernetes SIGs, CNCF CLA #42
Replies: 8 comments 9 replies
-
|
Here's an example of how @wheelerlaw went about triggering a CLA sign for himself: kubernetes-sigs/gateway-api#1588 (comment) Feel free to do the same: create a draft PR on https://github.com/kubernetes-sigs/gateway-api either with a real change you want to contribute, or something we can just close once we're done. OR if you already signed but I haven't counted you in the list yet, just link a previous CNCF PR of yours. |
Beta Was this translation helpful? Give feedback.
-
|
@acald-creator is now all set: kubernetes-sigs/gateway-api#1592 |
Beta Was this translation helpful? Give feedback.
-
|
@alejandroEsc is all set kubernetes-sigs/cluster-api#6188 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @shaneutt am I all set -- kubernetes-sigs/gateway-api#1593 |
Beta Was this translation helpful? Give feedback.
-
|
@RudranshGoel just wanted to check in on this, please let us know if you can or have already signed the CNCF CLA (by sharing a PR). If we don't hear back from you in the coming weeks, the most likely action will be we'll have to drop or revert your commits from the repository before we transfer. Please check in if you can! |
Beta Was this translation helpful? Give feedback.
-
|
@RudranshGoel just wanted to give you a heads up that we expect things to be moving soon, so please note that for compliance reasons we will be dropping commits authored by you if we don't hear back from you soon. Let us know if there's any confusion, and if we can help! |
Beta Was this translation helpful? Give feedback.
-
|
@RudranshGoel just wanted to provide one more warning that if we don't hear back from you on this one, we may need to drop your contributions before we can migrate to the CNCF. If you get this message, please read this announcement over and let us know if you have any questions, concerns or problems we can assist with. |
Beta Was this translation helpful? Give feedback.
-
|
@synthe102 if I'm not mistaken you are already signed up for CNCF contributions? Just share a relevant PR here if so, and if not feel free to follow the "test PR" approach some used above. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I signed up, the CLA check is valid on this PR: #61 |
Beta Was this translation helpful? Give feedback.
-
|
That's better: kubernetes-sigs/gateway-api#1720 |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@levikobi if you could link to an upstream Kubernetes or CNCF PR prior to your contribution in #93, (OR just use the "test PR" approach as seen above) it would be greatly appreciated as we should be really close to the point where cncf/foundation#474 should be done and we should be starting the CNCF migration to ksigs. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
#42 has the potential to help move this along, if the vote there to graduate Cilium (which shares a similar licensing schema to us) succeeds, just a heads up for everyone that we're still waiting, but it's possible after this is resolved we could get moving finally. |
Beta Was this translation helpful? Give feedback.
-
|
Licensing as been approved: cncf/foundation#474 the process should be able to continue now! |
Beta Was this translation helpful? Give feedback.
-
|
The migration is now fully complete, thanks everyone! |
Beta Was this translation helpful? Give feedback.
-
Hi everyone 👋
Several weeks ago at Kong we decided we wanted to donate this load-balancer to Kubernetes SIGs for use in upstream Gateway API.
We've been approved for contribute this repository to the CNCF and Kubernetes SIGs:
kubernetes/org#3875
What follows next are some formalities, some of which we'll need contributor participation for.
Licensing Review
We're obligated to use a GPL compatible license for parts of our code because we use eBPF for the data-plane and link to Linux kernel code. This however needs to undergo legal review in the CNCF because this is generally not a well-trodden path:
cncf/foundation#474
CNCF Contributor License Agreement
Everyone who has contributed to the repository so far will need to have signed the CNCF Contributor License Agreement (CLA) before we can migrate. This can be done by creating any PR in any Kubernetes SIGs repository, and the bot will send you a link if you haven't already signed it.
The following is a list tracking contributors and whether or not they've signed the CNCF CLA:
@RudranshGoelPlease feel free to reach out to me directly if you have any trouble with this or any questions, I can be reached on Kubernetes Slack
@shane, OR feel free to add a comment here in this discussion letting us know if/when you've signed the CLA.If you haven't signed the CLA and we don't get a response from you in the next few weeks, OR if for some reason you're opposed to signing the CLA just note that we may have to drop your commits from the
mainbranch. Not something we want to do, but this is the fallback position for compliance.Thanks all, will continue to post updates about the progress of things, but also feel free to subscribe to these:
And let us know in this discussion if you have any questions.
Beta Was this translation helpful? Give feedback.
All reactions