Thanks Martin (replying to the list so it's on the record) Bottom line: it is still fine to port code from JTS to GEOS.
--strk; On Wed, Apr 26, 2017 at 02:08:00PM -0700, Martin Davis wrote: > I checked with the LocationTech team, and here's the advice: > > JTS is now distributed under a normal BSD 3 clause license, and is very > much compatible with GPL. > JTS is dual licensed, with the goal of appealing to a larger audience while > remaining compatible with GPL. > > * The Eclipse Distribution License is a normal BSD 3-Clause license. It is > unfortunate that Eclipse made their own acronym - it really is just BSD. > * The Eclipse Public License is being enhanced with specific guidance to > let projects like JTS work with GPL. > > Hopefully this settles all concerns. GEOS is fine to carry on using GPL. > > On Sat, Apr 1, 2017 at 9:55 AM, Sandro Santilli <[email protected]> wrote: > > > On Thu, Mar 16, 2017 at 12:17:15PM -0700, Martin Davis wrote: > > > The selling feature of moving to LocationTech and relicensing to a > > > business-friendly license was that companies would then throw money at > > JTS > > > to make it bigger and better. That will probably start happening any day > > > now... > > > > Are we (as a community) reacher yet ? > > > > > The intent was definitely not to cut off the ability to keep GEOS alive > > and > > > well and in synch with JTS. I really hope there will be no legal issues > > > with continuing to port changes. > > > > > > I'll get in touch with LocationTech legal to get an opinion on this. > > > > Any answer ? > > Or are them too busy handling the load of money thrown by > > restrictive software license owners to friendly packages ? > > > > > > --strk; > > _______________________________________________ geos-devel mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/geos-devel
