[Geoserver-devel] GSIP-206 Promote GeoPackage to extension

GeoServer GeoServer Developer
1

+1

-Jukka Rahkonen-

···

Lähettäjä: Andrea Aime <andrea.aime@…6887…>
Lähetetty: tiistai 4. tammikuuta 2022 16.14
Vastaanottaja: Torben Barsballe <torbenbarsballe@…403…>
Kopio: GeoServer geoserver-devel@lists.sourceforge.net
Aihe: Re: [Geoserver-devel] GSIP-206 Promote GeoPackage to extension

And +1 here too

Cheers

Andrea

On Tue, Jan 4, 2022 at 12:04 AM Torben Barsballe <torbenbarsballe@…403…> wrote:

Looking at the proposal now, +1 from me.

Cheers,

Torben

On Thu, Dec 30, 2021 at 7:42 AM Jody Garnett <jody.garnett@…403…> wrote:

Thanks Andrea, I will rename the proposal.

I have capacity to support the wps module on this one (as indeed a customer is funding this activity).

Jody

On Thu, Dec 30, 2021 at 5:11 AM Andrea Aime <andrea.aime@…6887…> wrote:

Hi Jody,

checking the proposal, I believe the title is misleading, it seems to suggest a classic module move from community to extension, as is… which does not match the actual proposal.

The actual proposal is:

  • Fold the WFS output format gs-wfs, the WMS output format in gs-wms, hence, move these two bits in core
  • Fold the WPS process in gs-wps-core

About the move to cover of the WMS/WFS output formats, from a technical point of view I’m not concerned:

  • The WFS output format will eventually break for large outputs due to HTTP time outs (needs to be written on disk first, streamed back once complete), but the same already happens for zipped shapefiles, so nothing really new
  • The WMS output format now honors the rendering time outs, so it should be fine

I should however point out that the core of GeoServer is “maintained by the PSC” so the rest of the PSC should be comfortable having that code in core, and realize the associated obligation.

About the move of the WPS process to wps-core, I’m also personally not deeply concerned, if the documentation

is very clear about the experimental extensions baked into the process (so doc updates are needed).

I’m however noting the code moving also moves its maintainership from “nobody” to me (the WPS module maintainer), which I’m not too fond of [1].

Since you’re making the proposal, I’d like you to step up as co-maintainer of the code you’re trying to push up. For the core bits, as a PSC member, you’re taking that

responsibility automatically anyways. Please step up to co-maintain the processes once moved in gs-wps-core.

Cheers

Andrea

[1] Due to both project and business obligations I’m responsible for way too many modules already,

something which is too big of a onus on my shoulders, and a big project liability in case I get sick

or decide to leave. It’s something we’ll have to address, possibly sooner rather than later.

On Thu, Dec 30, 2021 at 5:28 AM Jody Garnett <jody.garnett@…403…> wrote:

Please have a look at

https://github.com/geoserver/geoserver/wiki/GSIP-206 which outlines moving different sections of the geopackage community module into the appropriate core module: gs-wfs, gs-wms, and gs-wps.

The proposal is solid, please make note of the backwards compatibility section which proposes calling out wps geopackage supports for not yet finalized extensions. While there is nothing wrong with having geoserver specific extensions they should be documented as such (and marked as in progress if they are chasing a moving target). If folks feel strongly about documentation not being enough warning I can look at leaving these geopackage extensions as an optional install.

Jody

–

–

Jody Garnett

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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