[Geotools-devel] Public domain contribution

Discussion:

sjudeng

2017-06-02 21:18:42 UTC

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 plugin are public domain. I can reach out to the list again in a
separate thread on whether this would be welcome and what would be required
from a technical perspective but wanted to start with this question first.

Jody Garnett

2017-06-02 21:22:46 UTC

Permalink

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 we use to
enforce our open source license.

I cannot remember the details now but you basically put your contribution
into the public domain and we pick it up (changing the packages and so on
becoming contributors and donating it to the geotools project).

So this is really not a lot of fun; do you have a legal requirement to use
the public domain? Or are you just looking for an alternative to your
employer signing a code contribution agreement?

--
Jody Garnett

Post by sjudeng
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 plugin are public domain. I can reach out to the list again in a
separate thread on whether this would be welcome and what would be required
from a technical perspective but wanted to start with this question first.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Jody Garnett

2017-06-02 21:24:32 UTC

Permalink

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

Post by Jody Garnett
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 we use to
enforce our open source license.
I cannot remember the details now but you basically put your contribution
into the public domain and we pick it up (changing the packages and so on
becoming contributors and donating it to the geotools project).
So this is really not a lot of fun; do you have a legal requirement to use
the public domain? Or are you just looking for an alternative to your
employer signing a code contribution agreement?
--
Jody Garnett

Post by sjudeng
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 plugin are public domain. I can reach out to the list
again in a separate thread on whether this would be welcome and what would
be required from a technical perspective but wanted to start with this
question first.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

sjudeng

2017-06-02 21:42:21 UTC

Permalink

Jody,

Thanks for your quick response. It does sound like a pain. I'll look into
the CLA.

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

Post by Jody Garnett
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 we use to
enforce our open source license.
I cannot remember the details now but you basically put your contribution
into the public domain and we pick it up (changing the packages and so on
becoming contributors and donating it to the geotools project).
So this is really not a lot of fun; do you have a legal requirement to
use the public domain? Or are you just looking for an alternative to your
employer signing a code contribution agreement?
--
Jody Garnett

Post by sjudeng
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 plugin are public domain. I can reach out to the list
again in a separate thread on whether this would be welcome and what would
be required from a technical perspective but wanted to start with this
question first.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Jim Hughes

2017-06-05 15:43:44 UTC

Permalink

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

Post by sjudeng
Jody,
Thanks for your quick response. It does sound like a pain. I'll look
into the CLA.
You can see the language used here -
http://docs.geotools.org/latest/userguide/welcome/license.html
<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
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 we use to enforce our open source license.
I cannot remember the details now but you basically put your
contribution into the public domain and we pick it up
(changing the packages and so on becoming contributors and
donating it to the geotools project).
So this is really not a lot of fun; do you have a legal
requirement to use the public domain? Or are you just looking
for an alternative to your employer signing a code
contribution agreement?
--
Jody Garnett
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
<https://github.com/ngageoint/elasticgeo>), which is
licensed based on the GeoTools (LGPL) and GeoServer (GPL)
components. My contributions to the plugin are public
domain. I can reach out to the list again in a separate
thread on whether this would be welcome and what would be
required from a technical perspective but wanted to start
with this question first.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel
<https://lists.sourceforge.net/lists/listinfo/geotools-devel>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Jody Garnett

2017-06-08 01:47:35 UTC

Permalink

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

Post by Jim Hughes
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
Jody,
Thanks for your quick response. It does sound like a pain. I'll look into
the CLA.

You can see the language used here - http://docs.geotools.org/lat
est/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

Post by Jody Garnett
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 we
use to enforce our open source license.
I cannot remember the details now but you basically put your
contribution into the public domain and we pick it up (changing the
packages and so on becoming contributors and donating it to the geotools
project).
So this is really not a lot of fun; do you have a legal requirement to
use the public domain? Or are you just looking for an alternative to your
employer signing a code contribution agreement?
--
Jody Garnett

Post by sjudeng
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 plugin are public domain. I can reach out to the list
again in a separate thread on whether this would be welcome and what would
be required from a technical perspective but wanted to start with this
question first.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Jody Garnett

2017-07-10 22:43:59 UTC

Permalink

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

Post by Jody Garnett
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

You can see the language used here - http://docs.geotools.org/lat
est/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

Post by Jody Garnett
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 we
use to enforce our open source license.
I cannot remember the details now but you basically put your
contribution into the public domain and we pick it up (changing the
packages and so on becoming contributors and donating it to the geotools
project).
So this is really not a lot of fun; do you have a legal requirement to
use the public domain? Or are you just looking for an alternative to your
employer signing a code contribution agreement?
--
Jody Garnett

Post by sjudeng
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 plugin are public domain. I can reach out to the list
again in a separate thread on whether this would be welcome and what would
be required from a technical perspective but wanted to start with this
question first.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

sjudeng

2017-06-13 21:56:21 UTC

Permalink

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
<https://github.com/ngageoint/elasticgeo/blob/df1234c3d56f43a0cdd46c98545798a92a6c0fd6/pom.xml#L39>
).

Post by sjudeng
Jody,
Thanks for your quick response. It does sound like a pain. I'll look into
the CLA.

You can see the language used here - http://docs.geotools.org/lat
est/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

Post by Jody Garnett
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 we
use to enforce our open source license.
I cannot remember the details now but you basically put your
contribution into the public domain and we pick it up (changing the
packages and so on becoming contributors and donating it to the geotools
project).
So this is really not a lot of fun; do you have a legal requirement to
use the public domain? Or are you just looking for an alternative to your
employer signing a code contribution agreement?
--
Jody Garnett

Post by sjudeng
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 plugin are public domain. I can reach out to the list
again in a separate thread on whether this would be welcome and what would
be required from a technical perspective but wanted to start with this
question first.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Jim Hughes

2017-06-13 22:05:17 UTC

Permalink

Ah, so you are using the ElasticSearch REST client then?

Sounds like a reasonable solution.

Post by sjudeng
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
<https://github.com/ngageoint/elasticgeo/blob/df1234c3d56f43a0cdd46c98545798a92a6c0fd6/pom.xml#L39>).
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
You can see the language used here -
http://docs.geotools.org/latest/userguide/welcome/license.html
<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
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 we use to enforce our open source
license.
I cannot remember the details now but you basically put
your contribution into the public domain and we pick it up
(changing the packages and so on becoming contributors and
donating it to the geotools project).
So this is really not a lot of fun; do you have a legal
requirement to use the public domain? Or are you just
looking for an alternative to your employer signing a code
contribution agreement?
--
Jody Garnett
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
<https://github.com/ngageoint/elasticgeo>), which is
licensed based on the GeoTools (LGPL) and GeoServer
(GPL) components. My contributions to the plugin are
public domain. I can reach out to the list again in a
separate thread on whether this would be welcome and
what would be required from a technical perspective
but wanted to start with this question first.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the
world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel
<https://lists.sourceforge.net/lists/listinfo/geotools-devel>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/geotools-devel

sjudeng

2017-06-13 22:17:50 UTC

Permalink

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 (e.g. Guava).