On 17 September 2017 at 14:59, Ben Caradoc-Davies <b...@transient.nz> 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
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
