Wanted to explicitly reply to "satisfying intent", and I hope project leads
agree with my take:

In the GeoTools MR fork all files have been updated with the OSGeo
> copyright headers. The one thing I haven't been comfortable with is the
> idea of rebasing out attribution to other contributors just because they
> can't sign the CLA. I was hoping since ElasticGeo is an established open
> source project released under LGPL (gt-elasticsearch) and GPL
> (gs-elasticsearch) that the contributions could be recognized as having
> satisfied the intent of the OSGeo CLA in this case.
>

Trying to establish:
- Intent (personal or employer) to shared with others as open source
- Permission for project leadership to do odd things (like donate to JTS,
or include in a product that has both GPL and a couple EPL code)

My take is your ElasticGeo work is fine:
- Attribution, and a note that the work was public domain, are going to be
maintained (we like to respect original authors)
- Contributions made as LGPL shows the understanding that this is going to
be distributed as open source
- Contributions made as LGPL show no conflict with use with EPL libraries
- Contributions made that extend GeoServer API also work (GPL with an
exception to work with a couple EPL library)
- Public domain is your cue to act as an individual and take the code
across any open source boundaries
- Public domain also let's the project leaders re-license etc...

Net result:
- If you want you could package this up, and fill in a software grant
<https://www.osgeo.org/resources/corporate-contributor-license/> (one of
the CLAs) indicating the work is a mix of open source and public domain
code you are providing to the geoserver project.

The place where we need GSP-186 is for the planet.com code which has just
placed into a repository (fortunately using the GeoServer GPL w/ exception)
license. If planet would donate this work to OSGeo we would be done,
without their participation we are stuck changing our procedure as Andrea
proposed.
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to