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
Switch to EPL 2.0 License #1393
Milestone
Comments
Since no objections here and in gitter I think we shall do this. |
I think it is okay if we proceed with it. |
Actually such task already exist since 2020 - #1008 |
avgustinmm
added a commit
to bosch-io/hawkbit
that referenced
this issue
Sep 14, 2023
Switching license from EPL v1 to v2. Following https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw Signed-off-by: Marinov Avgustin <Avgustin.Marinov@bosch.com>
avgustinmm
added a commit
that referenced
this issue
Sep 14, 2023
Switching license from EPL v1 to v2. Following https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw Signed-off-by: Marinov Avgustin <Avgustin.Marinov@bosch.com>
done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be good to switch to the newer EPL version 2.0.
Some clarification about how to could be found at How Do I Re-license from EPL-1.0 to EPL-2.0.
It seems that just modification in the pom files, file header and notification to the community is needed.
The text was updated successfully, but these errors were encountered: