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

chore: update license to EPL 2.0 #170

Merged
merged 1 commit into from
Aug 27, 2024
Merged

chore: update license to EPL 2.0 #170

merged 1 commit into from
Aug 27, 2024

Conversation

sebthom
Copy link
Member

@sebthom sebthom commented Aug 26, 2024

See also https://www.eclipse.org/legal/epl-2.0/faq/#epl-relicensing For open source projects (including Eclipse Foundation projects) under the EPL-1.0 who wish to re-license to the EPL-2.0 they should do so by simply updating the file headers and notices.

Signed-off-by: sebthom <sebthom@users.noreply.github.com>
@sebthom sebthom requested a review from vorburger August 26, 2024 16:46
@vorburger
Copy link
Member

FTR, this PR is the continuation of this discussion:

After having read https://www.eclipse.org/legal/epl-2.0/faq/#epl-relicensing, quote:

The EPL allows new versions of the license to be adopted by projects with little work. Specifically, the license states that, "Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version." \n For open source projects (including Eclipse Foundation projects) under the EPL-1.0 who wish to re-license to the EPL-2.0 they should do so by simply updating the file headers and notices. (Please see 3.4 and 3.5 below.)

Re. this aspect:

Note that it is good community practice to discuss this change on your public mailing lists, and to make every attempt to ensure that: (a) downstream users are aware of the change, and (b) that there is a rough consensus amongst the committers that this is the right time to switch.

I'm hereby, pro forma, making "every attempt to ensure that (...) there is a rough consensus amongst the committers that this is the right time to switch." by paging some past contributors to this repo @J-N-K and @rPraml and @focbenz and @maggu2810 and @ctron as well as committers @triller-telekom and @sylvainlaurent and @Bananeweizen and @wborn to shout if they have any objections to changing the license of LastNPE.org from EPL 1.0 to 2.0.

Let's give it, say... 48h? Then I intend to merge, assuming no objections.

Copy link
Member

@J-N-K J-N-K left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@vorburger vorburger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've meanwhile had some private email exchange about this with someone who would need (he wrote it!), which together with the x2 LGTMs from @wborn and @J-N-K give me the confidence to merge this!

Copy link
Member

@vorburger vorburger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've meanwhile had some private email exchange about this with someone who would need (he wrote it!), which together with the x2 LGTMs from @wborn and @J-N-K give me the confidence to merge this!

@vorburger vorburger merged commit 227e1f1 into lastnpe:main Aug 27, 2024
1 check passed
@sebthom sebthom deleted the epl2 branch August 27, 2024 10:23
@Bananeweizen
Copy link
Contributor

While I'm late to the party, I hereby fully agree. I also cannot image for what reason someone would not agree to such a change. The EPL version 2 is basically identical to version 1 from my software developer eyes point of view. (I understand that this would be a different beast e.g. when changing GPL2 to GPL3)

@J-N-K J-N-K added this to the 3.0.0 milestone Aug 31, 2024
Copy link
Contributor

@maggu2810 maggu2810 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

6 participants