+1 of the cleanup changes, although you may also wish to post this to the
forum?

I assume this is just about clean up and not yet cutting scope...
- -
Jody Garnett


On Nov 16, 2024 at 3:26:59 AM, Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi all,
> it's been a while since the last community space cleanup, I guess it's
> time to shed off some dead leaves again.
>
> Here is a list of modules that are in the community section, which do not
> seem to have any action, value, or chance of being resurrected anytime soon:
>
>
>    - app-schema/webservice-test
>    
> <https://github.com/geoserver/geoserver/tree/main/src/community/app-schema/webservice-test>:
>    run only with custom profiles (oddly, both "webservice" and "app-schema
>    
> <https://github.com/geoserver/geoserver/blob/main/src/community/pom.xml#L102>"
>    do). It does not even start to build, depends on the gone
>    gt-webservice-test module.
>    - gwc-distributed
>    
> <https://github.com/geoserver/geoserver/tree/main/src/community/gwc-distributed>:
>    containing just a Spring context and some dependencies, enables the 
> Hazelcast
>    distributed in memory tile cache
>    
> <https://docs.geoserver.org/latest/en/user/geowebcache/config.html#hazelcast-cache>.
>    Anyone using it?
>    - imagemap
>    <https://github.com/geoserver/geoserver/tree/main/src/community/imagemap>,
>    enables the HTML image map output format
>    <https://docs.geoserver.org/latest/en/user/community/imagemap.html>. I
>    guess nobody today uses HTML image maps in cartography, but if you do,
>    please let me know.
>    - jdbc-metrics
>    
> <https://github.com/geoserver/geoserver/tree/main/src/community/jdbc-metrics> 
> seems
>    to collect statistics about queries in JDBCFeatureReader
>    
> <https://github.com/geotools/geotools/blob/main/modules/library/jdbc/src/main/java/org/geotools/jdbc/JDBCFeatureReader.java#L269>.
>    On one side, it seems like a useful tool to track time actually spent
>    talking to the database, on the other, it has no documentation has has seen
>    to action for the past 7 years. Anyone using it, or that would be
>    interested in writing a bit of documentation for it?
>    - monitor-hibernate
>    
> <https://github.com/geoserver/geoserver/tree/main/src/community/monitor-hibernate>
>  provides
>    database storage for the monitoring subsystem. Unmaintained, based on the
>    dead Google code genericdao framework, and afflicted by using primary keys
>    in a log table (insertions become slower and slower), it probably deserves
>    some final rest, a suitable replacement would be a rewrite, not a few small
>    fixes.
>    - pgraster
>    <https://github.com/geoserver/geoserver/tree/main/src/community/pgraster> 
> despite
>    the name it's an easy to use UI on top of  the no longer existing
>    gt-imagemosaicjdbc.  This one already has a removal PR.
>    - saml
>    <https://github.com/geoserver/geoserver/tree/main/src/community/saml> is
>    gone already, but its assembly descriptor survived and should also be
>    removed.
>    - wps-sextante
>    
> <https://github.com/geoserver/geoserver/commits/main/src/community/wps-sextante>
>  is
>    based on the Sextante java libraries... which I cannot find any more. The
>    version it depends onto has been released around 2012
>    <https://mvnrepository.com/artifact/es.unex.sextante/sextante/1.0>,
>    the module received its last direct commit in 2015 (all others are mass
>    refactors), has no documentation, Sextante for Java seems nowhere to be
>    found...
>    - xslt
>    <https://github.com/geoserver/geoserver/tree/main/src/community/xslt> is
>    a WFS output format generator based on XSLT that was demoted to community
>    in May 2023. Looks like nobody complained, I'd complete the job.
>
> Regarding extensions, the following look like good candidates for demotion
> to community:
>
>    - h2
>    <https://github.com/geoserver/geoserver/tree/main/src/extension/h2>
>    store, based on the old and unmaintained H2 v1.x. While we cannot get rid
>    of it completely, as some modules keep on depending on it (e.g. the NetCDF
>    store family), I'd make its availability as a vector store harder to get.
>
> Feedback welcomed!
>
> 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  339 8844549
>
> 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
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to