Thanks Andrea, Taking feedback here for discussion (rather than editing the page directly):
1. This practice allows to centralize code ownership on OSGeo, and as a result, on the GeoServer PSC. Change to "control", since CLA does not affect "ownership" (or "authorship"). > This practice allows greater control of the GeoServer codebase by OSGeo, and as a result, by the GeoServer PSC. 2. At the same time, this sometimes limits contributions the project can accept, and there are growing opinions against the concept of CLA itself, see for example ... Changed to highlight author may be unavailable (rather than just unwilling). At the same time, this sometimes limits code we can include in our project. If the author is unavailable, or unwilling, to grant OSGeo additional permissions. For example ... 3. This proposal aims at relaxing the CLA requirements so that code can be contributed without signing a CLA, under some restrictive conditions that still make it possible for the PSC to retain control of core modules. Changed to be explicitly just GeoServer license (GPL+EPL excepting) conditions: > This proposal removes the CLA requirements so that code can be contributed to an extension without signing a CLA. The community or extension README will clearly indicate that use of GeoServer LICENSE (GPL w/ EPL library use), and the headers of the files affected will be maintained. 4. The licence is compatible with the GPL Modified to say GeoServer LICENSE (we cannot add in any GPL code as we require an exception for with "the EMF, XSD and OSHI Libraries". This should still work for any extension written with GeoServer in mind, but it does hamper the reuse of random found GPL code on the internet. > * Explicitly include the GeoServer LICENSE.md file > * The headers from the original files are maintained, and not updated to indicate (c) OSGeo Foundation. > * Classes written post-donation can include OSGeo header if all authors have signed CLA 5. This will influence also pull request review, reviewers will have to verify that code coming from extensions and community modules can indeed be moved, and otherwise reject the request. Changed as CLA more than covers contributions to these modules. > Pull requests are un-affected as CLA covers the distribution of code by an open source license, and these modules are distributed under the GeoServer GPL License. Although perhaps you are referencing moving code between these "found-code" extensions/community modules and "core"? If so the files should clearly have a header that does not say OSGeo and thus be easy to check. > Pull requests updating these extensions/community modules are un-affected as our required CLA covers the distribution of code by an open source license. These these extensions/community modules are distributed under the terms of the open source GeoServer GPL License. > Review of pull requests moving code from these extension/community modules should be easy to catch due to use of non OSGeo header. Q: Would you be willing to call these "found-code extension" or "found-code community module" just to have a quick way to talk about the difference? -- Jody Garnett On Wed, 22 Jan 2020 at 10:01, Andrea Aime <[email protected]> wrote: > Hi, > following up the last december PSC meeting discussion, here is a proposal > to relax the CLA requirements > for code contribution, under some specific conditions: > > https://github.com/geoserver/geoserver/wiki/GSIP-186 > > Feedback welcomed. > > Cheers > Andrea > > > == 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 > (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.* > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
