Re: [Geotools-devel] Public domain contribution

It has now been a month since I passed this to the OSGeo borad, I will ask for a status update. Sorry this is taking so long, everyone must be on summer holiday. -- Jody Garnett On 7 June 2017 at 18:47, Jody Garnett wrote: > I am working with sjudeng and the board to see if we can get an OSGeo

Re: [Geotools-devel] Public domain contribution

That's right. Going this route simplified the project configuration since separate jars are no longer needed for different ES versions (e.g. same modules/binaries work with both ES2 and ES5). Also of course it's always good when plugin install instructions don't involve removing core GeoServer jars

Re: [Geotools-devel] Public domain contribution

Ah, so you are using the ElasticSearch REST client then? Sounds like a reasonable solution. On 06/13/2017 05:56 PM, sjudeng wrote: Hi Jim, In the last ElasticGeo release I removed the org.elasticsearch:elasticsearch dependency and as a result freed it from the transitive Guava dependency. Guav

Re: [Geotools-devel] Public domain contribution

Hi Jim, In the last ElasticGeo release I removed the org.elasticsearch:elasticsearch dependency and as a result freed it from the transitive Guava dependency. Guava is still used in the project but I backed it down to version 17.0 for consistency with GeoServer (see POM

Re: [Geotools-devel] Public domain contribution

I am working with sjudeng and the board to see if we can get an OSGeo CLA suitable for governments to sign (as an alternative to the public domain dance). I am waiting to hear back, and possibly talk to Ben who is good at this stuff, before recommending a course of action. -- Jody Garnett On 5 J

Re: [Geotools-devel] Public domain contribution

Hi all, Separate from the licensing, I believe that ElasticSearch uses Guava 18. GeoTools and GeoServer uses version 17. Does ElasticGeo work with Guava 17? Cheers, Jim On 06/02/2017 05:42 PM, sjudeng wrote: Jody, Thanks for your quick response. It does sound like a pain. I'll look into

Re: [Geotools-devel] Public domain contribution

Jody, Thanks for your quick response. It does sound like a pain. I'll look into the CLA. On Fri, Jun 2, 2017 at 4:24 PM, Jody Garnett wrote: > You can see the language used here - http://docs.geotools.org/ > latest/userguide/welcome/license.html > > Indeed we tried to make our demo code public

Re: [Geotools-devel] Public domain contribution

You can see the language used here - http://docs.geotools.org/latest/userguide/welcome/license.html Indeed we tried to make our demo code public domain, but because that was not a license it made it even harder for people to use. We now have our demo code as BSD. -- Jody Garnett On 2 June 2017 a

Re: [Geotools-devel] Public domain contribution

It has been done before in the geotools library. Mostly for us government employees who's work is in the public domain (since it was paid for by the people). Please understand that public domain is an alternative to copyright - not an alternative to having a license. Indeed copyright is the stick

[Geotools-devel] Public domain contribution

Is it possible to make a public domain contribution to GeoTools and GeoServer without a CLA? I'm interested in contributing an Elasticsearch plugin (https://github.com/ngageoint/elasticgeo), which is licensed based on the GeoTools (LGPL) and GeoServer (GPL) components. My contributions to the plugi