[Board] osgeo code contribution agreement
Mattmann, Chris A (388J)
chris.a.mattmann at jpl.nasa.gov
Sun Feb 3 14:12:53 PST 2013
Hi Jody,
From: Jody Garnett <jody.garnett at gmail.com<mailto:jody.garnett at gmail.com>>
Date: Sunday, February 3, 2013 1:43 PM
To: jpluser <chris.a.mattmann at jpl.nasa.gov<mailto:chris.a.mattmann at jpl.nasa.gov>>
Cc: "board at lists.osgeo.org<mailto:board at lists.osgeo.org>" <board at lists.osgeo.org<mailto:board at lists.osgeo.org>>
Subject: Re: [Board] osgeo code contribution agreement
On Monday, 4 February 2013 at 4:08 AM, Mattmann, Chris A (388J) wrote:
Ah, OK, is there a record of that somewhere, just out of curiosity would love to see.
Apache representatives spoke at FOSS4G 2006 in Victoria.
Thanks! Will scope it out.
[..snip..]
Reading the proposal I didn't see mention of LGPL anywhere in the contributor agreement. Are you suggesting that the contributions of each individual or corporation be licensed to OSGeo under LGPL? If so, I think that would need to be reified somewhere in the ICLA or CCLA. That said, I think it would then run afoul of the Copyright Grants and Patent Grants, since those pretty much defeat the reciprocity of the LGPL as licensed from individual/corporation to the Foundation.
The code contribution agreement *just* covers donating code to the OSGeo foundation. The license of each project remains unchanged, in this specific case GeoTools is distributed under an LGPL license, my understanding is that the distribution license has no effect on 'code contribution".
That's my understanding too, but your proposal here:
http://docs.codehaus.org/display/GEOTOOLS/Replace+Contribution+Agreement
Mentions that:
3) Change license to LGPL
Which was making me wonder if you were thinking code distribution instead of contribution since for contribution, you shouldn't have to specify the license, right?
Cheers,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20130203/de26c8b5/attachment.htm>
More information about the Board
mailing list