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?
(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?
(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?
Kind regards,
--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
------------------------------------------------------------------------------
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
