Re: [gef-dev] Re-license GEF Classic from EPL-1.0 to EPL-2.0

[Lars Vogel <lars.vogel@xxxxxxxxxxx>]

AFAIR the migration to EPL 2.0 is mandatory from the foundation and requires no agreement of the individual committers. 

At least we were forced to migrate in platform and we did not rechecked with wach contributor.

Emo, please comment?

Best regards, Lars 

Edward Willink via gef-dev <gef-dev@xxxxxxxxxxx> schrieb am Di., 3. Okt. 2023, 09:57:

Hi

In principle it's easy, but even though there is no real reason to
disagree you need to get every committing author to agree. For OCL with
limited committers, this was little problem. For GEF, I can imagine some
committers are no longer reachable. Perhaps you just get agreement of
all significant or very recent committers and then get the EF to give
you a common sense waiver for the rest.

     Regards

         Ed Willink

On 03/10/2023 08:30, Alois Zoitl via gef-dev wrote:
> Dear Friends of GEF!
>
> Currently GEF Classic is still licensed under EPL-1.0. As EPL-1.0 is deprecated I would also like to re-license GEF Classic to EPL-2.0. According to the EPL
> itself this is possible with out any special procedure.
>
> However I would like to ask you if there is any reason to not do this.
>
> Looking forward to your feedback.
>
> Cheers,
> Alois
>
>
> _______________________________________________
> gef-dev mailing list
> gef-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/gef-dev
_______________________________________________
gef-dev mailing list
gef-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/gef-dev