Some further thoughts: > Relax CLA requirements > > Discussion: > > - > > Right now we ask for CLA, for anything but trivial changes, … > - > > Word on the street is to stop using CLA all together … > https://opensource.com/article/19/2/cla-problems > - > > We actually make use of CLA: > - > > To relicense code and donate to GeoTools, JTS, GeoWebCache :) > > License: > > - > > https://www.osgeo.org/about/licenses/ > - > > Individual Contributor License Agreement > - > > Software Grant and Corporate Contributor License Agreement > > > Context: > > - > > Stratus: Wraps geoserver, so similar setup to GeoFence > - > > GSR: Code is open source and available, but we do not have a specific > corporate CLA for it > - > > GeoTools module: https://github.com/geotools/geotools/pull/2592 > > > The issue: > > 1. > > We value having a CLA so we can relicense code and make donations to > other projects > 1. > > It also confirms person had permission to make functionality open > source > 2. > > Some protection around patents and trademarks > 2. > > We have some GPL code in the wild we would like to build on, but we > would have no ability to relicense > > > Idea: > > - > > Allow GPL’d code without a CLA to be merge into the codebase > - > > Mark the module as “Strictly GPL” > - > > No code from that module can be moved into core or another extension > (it would make them tainted too) > - > > Same for GeoTools, using LGPL licence. > > > Danger: > > - > > More folks would like to avoid CLA if we have a mechanism to support > - > > Limit mechanism to single modules, no intermingling > > Just on "how to do it" clearly front:
1. Maintain original GPL header 2. Add our own header (if we make changes beyond repackaging) This is the same process used for other code reuse, and should be fairly clear. It also has the advantage of being visible on a file by file basis. This does not take away from documenting in module README, we can also consider an explicit LICENSE file for these modules. One thing we cannot necessarily fix is granting the additional clause used in the GeoServer license (although for any modules such as GSR based on GeoServer already need to account for this). -- Jody
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
