(3) confirmed - we need to wait for EMF and XSD projects to take action;
until then there is nothing for us to change (well other than adding OSHI
to the list).
--
Jody Garnett
On 18 September 2017 at 09:58, Jody Garnett <[email protected]> wrote:
> Doing my own quick research on (3):
>
> Now that EPL-2.0 is final, can we just choose to use our EPL dependencies
>> under EPL-2.0, or do we need action from their maintainers?
>
>
> From the FAQ it appears as if we need to wait for EMF and CSD to adopt EPL
> 2.0: *So a project can use the new version by simply updating the file
> headers and notices. *
> - https://eclipse.org/org/documents/epl-2.0/faq.php
>
>
>> And is EPL-2.0 compatible with GPLv2 after all?
>
>
> It looks like this optional for new projects: *The new EPL v2 will allow
> initial contributors to new projects to specify if they want their EPL v2
> licensed project to be GPL compatible.*
>
> https://www.eclipse.org/org/press-release/20170829eplv2.php
>
> --
> Jody Garnett
>
> On 18 September 2017 at 09:52, Jody Garnett <[email protected]>
> wrote:
>
>> On 17 September 2017 at 14:59, Ben Caradoc-Davies <[email protected]>
>> wrote:
>>
>>> GeoServer is licensed under the GPLv2 with exceptions for named Eclipse
>>> libraries whose EPL-1.0 licenses would otherwise be incompatible with the
>>> GPL. The status-monitoring community module adds another EPL-1.0-licensed
>>> dependency (OSHI); the GeoServer license will be patched to permit this.
>>>
>>> (1) Should we change the GeoServer license to include a more generic
>>> exception so that we do not have to patch it for each new EPL-1.0
>>> dependency?
>>>
>>
>> I think we could, we were being very cautious when we did the original
>> change.
>>
>>
>>> (2) Should we change the GeoServer licence to a well-known
>>> EPL-compatible license, such as GPLv2+linking-exception or LGPL? Would such
>>> a license be strong enough?
>>>
>>
>> I do not think it would be strong enough, we had discussed this
>> perviously with OpenGeo. What it GPLv2+linking-exception?
>> Reading - https://en.wikipedia.org/wiki/GPL_linking_exception. So very
>> similar to the classpath exception.
>>
>> (3) Now that EPL-2.0 is final, can we just choose to use our EPL
>>> dependencies under EPL-2.0, or do we need action from their maintainers?
>>> And is EPL-2.0 compatible with GPLv2 after all?
>>>
>>
>> I will ask on the locationtech list for you.
>>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
