Sorry I was tired, I am proposing changes on this email thread as I want to get the words right, as an example "found code" not working for you to communicate these community / extensions modules. Any other ideas for a "catchy name" ...
Missing from this was my personal feedback: - For everything written as a GeoServer extension I believe the approach you outline will work fine and I am +1 to the approach - For incorporating random GPL code found on the internet I think we are stuck (due to our license having an exception to the GPL), not a down check we just need to be aware of the limits - My personal dial is moving from open source license towards free software license the more I see frustrations like this, and the more I see GPL keep code together in a sustainable pile rather than fragment ... aside: For the elastic search there are to problems a) lack of CLA b) use of government code. Rant: *Especially for American government it is the "public domain" part making it inconvenient to work with; NGA tried to work out how to sign something with OSGeo but they got stuck. These CLAs are about "owner" providing permission, setting projects up to use copyright to enforce open source license. Public domain messes with that making open source license hard to enforce. Work around in geotools is to have an individual copy the content into the project, but after a while that ends up being us developers so it is not a sustainable approach.* -- Jody Garnett On Thu, 23 Jan 2020 at 03:53, Andrea Aime <[email protected]> wrote: > Hi Jody, > thanks for your feedback. > > Your wording uses the past tense, as if you did changes on the page... but > none of the edits were applied. > I've just applied what I could. > > On Thu, Jan 23, 2020 at 3:24 AM Jody Garnett <[email protected]> > wrote: > >> 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? >> > > Confusing, not all is found code, see for example the ElasticSearch case > in GeoTools (just an example, I'm aware that a separate > proposal will be required for GeoTools, want to first hash out this one). > > 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
