so. The document would
> not be a perfect fit but you could fill it out as an individual (not an
> organization), list “not applicable” for employees as nobody is working on
> your behalf, and then name the software component being donated.
> —
> Jody
>
> On Sat, Jan 25, 20
#x27;s how we'll be
able to move forward on the PR without getting individual/corporate CLAs
signed for each of them? Once it's merged what if a new contributor wanted
to contribute to the module but also couldn't sign the CLA?
On Fri, Jan 24, 2020 at 7:18 AM sjudeng wrote:
> Hi Jod
CLA,
> rather than to just the sentence on copyright ...
>
> If you want to pursue this with NGA management we can do so via Open
> Source Geospatial Foundation, they have been stuck on this for *years*.
>
> On Wed, Jan 22, 2020 at 7:03 PM sjudeng wrote:
>
>> Jody and And
Tools-side) and GPL
(GeoServer-side), is the inclusion of the associated source code not
similar to the inclusion of similarly licensed third-party dependency
libraries, which include contributors that haven't signed the OSGeo CLA?
On Mon, Jan 13, 2020 at 8:18 PM sjudeng wrote:
> Hello
at 1:41 AM Andrea Aime
wrote:
> On Mon, Jan 13, 2020 at 3:11 AM sjudeng wrote:
>
>> Hi all,
>>
>> If there is interest I'd like to try again to get ElasticGeo contributed
>> to GeoTools/GeoServer as a community module.
>>
>
> I don't remember
Would everyone need
to have a CLA on file for the contribution to be successful?
https://github.com/sjudeng/geotools/tree/elasticsearch
https://github.com/sjudeng/geoserver/tree/elasticsearch
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforg
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
com/ngageoint/elasticgeo/blob/df1234c3d56f43a0cdd46c98545798a92a6c0fd6/pom.xml#L39>
).
On Fri, Jun 2, 2017 at 4:42 PM, sjudeng wrote:
> 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 Garne
gt;>
>> 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
>>
>> On
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
10 matches
Mail list logo
