So the background motivation is that "this sometimes limits contributions the project can accept" and the price to pay is possibly opening a can of worms in terms of revisions and acceptance of pull requests.
Wonder, are there any precedents for contributions that couldn't be accepted due to lack of a singed CLA? How were they resolved? Sorry I missed the discussion so far, but fear in adding even more overhead to the already very limited resources the project has. I'm under the impression, and this might be just me, that the project is already too permissive to incorporate content to its codebase under the community modules space. That might have been nice in the svn days, but with git anyone can have their unsupported geoserver plugins elsewhere and still publicly accessible and ready to merge. Or maybe a separate repository could be used for "community" modules? This is just a thought from the perspective that sometimes less is more, and I personally would like the codebase to be as succinct as possible maybe with just the stuff that is "ok", and think about other alternatives for pure RnD, possibly drop and forget contributions. On Wed, 22 Jan 2020 at 15: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 > -- Gabriel Roldán
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
