We got a bit sidetracked as geotools was mentioned, and how to handle public domain.
Net result is your proposal is fine: - CLA for core - individual module can use GeoServer license (gpl+Epl library) If we want to be explicit about how to handle public domain a second proposal could be drawn up. On Sat, Jan 25, 2020 at 5:14 AM Andrea Aime <[email protected]> wrote: > Hi Jody, > after reading this mail I'm more confused than before. Right now we have a > simple and clear rule, CLA or bust (it's what's written in our docs, did I > misread them?) > The proposal allows to open a second path for those that don't want/can't > sign a CLA. Seems clear too. > > What you are discussing here is new rules, which seem to made up for the > occasion, while they might be correct in general, I don't think they are > not a match for our documentation (happy to be proved wrong). > Could you clarify and possibly make a proposal to change the GT/GS > documentation accordingly, on how to handle public domain code? > > Cheers > Andrea > > On Fri, Jan 24, 2020 at 10:35 PM Jody Garnett <[email protected]> > wrote: > >> 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. >> > > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime > @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 > Massarosa > <https://www.google.com/maps/search/Via+di+Montramito+3%2FA%0D%0A55054++Massarosa?entry=gmail&source=g> > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > -- -- Jody Garnett
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
