Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change dataplane licensing to meet CNCF requirements #78

Closed
shaneutt opened this issue Mar 3, 2023 · 1 comment · Fixed by #79
Closed

Change dataplane licensing to meet CNCF requirements #78

shaneutt opened this issue Mar 3, 2023 · 1 comment · Fixed by #79

Comments

@shaneutt
Copy link
Member

shaneutt commented Mar 3, 2023

In the midst of our migration of this project to Kubernetes SIGs and trying to get approved for inclusion of GPLv2 code we learned that a combination of GPLv2 + BSD-2-Clause licensing for eBPF code is currently allowed licensing for CNCF inclusion with precedents.

The purpose of this task is to update our licensing of the dataplane code from GPLv2 to GPLv2 + BSD-2-Clause to get our migration moving along.

@shaneutt shaneutt added this to the v0.2.0 - TCPRoute Support milestone Mar 3, 2023
@shaneutt shaneutt self-assigned this Mar 3, 2023
@shaneutt shaneutt removed the on-hold label Mar 3, 2023
shaneutt added a commit that referenced this issue Mar 6, 2023
Changes the dataplane licensing from `GPLv2` to dual-licensed `GPLv2 +
BSD-2-Clause` as per CNCF requirements as outlined in #78.

Resolves #78
@shaneutt
Copy link
Member Author

shaneutt commented Apr 6, 2023

For posterity: all contributors to the dataplane code at the time of this change signed off on the change in #79 👍

shaneutt added a commit to shaneutt/blixt that referenced this issue Oct 11, 2023
Changes the dataplane licensing from `GPLv2` to dual-licensed `GPLv2 +
BSD-2-Clause` as per CNCF requirements as outlined in kubernetes-sigs#78.

Resolves kubernetes-sigs#78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant