Thanks for round up Andrea, mongoDB has also a number of java developers
but now actual module maintainer listed in the pom.xml file. I know my name
is there from back when I had access to a development environment.
--
Jody Garnett


On Sun, 10 May 2020 at 01:36, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:

> Hi all,
> the current release package contains a number of modules that are
> un-maintained and for which
> we don't have a build actually running (they are depending on online tests
> which are not setup).
> The last part is the one that worries me the most, a module without a
> dedicated maintainer can still
> stay around just because its tests are covering it... sort of
> "self-serving", until there are specific troubles
> with it, I would not go and propose a demotion (sample module in this
> situation is gt-graph).
>
> Here is a list with some observations.
>
> *imagemosaic-jdbc*
> We already discussed it, inquired for this one on the users list and on
> tickets of people showing interest on the module,
> nothing came up, the module is un-maintained and will stay that way. Time
> to demote it.
>
> *epsg-postgresql*
> Has been kept around for a while, but no tests are run. Maybe we could
> setup an online build for it as a github action.
> Could be hard, if tests in it are actually failing (nobody knows).
>
> *jdbc-db2*
> Has not been touched for years, the last actual DB2 related change goes
> back to 2015. I believe no-one among
> the current developers has experience with it, and has been driving zero
> business flat.
> I've inquired on this ticket to see if we can get a new maintainer or at
> least a build to check if things are still working:
> https://osgeo-org.atlassian.net/browse/GEOT-6584
>
> *jdbc-mysql*
> Same situation as the others. I might try to setup a build and see how bad
> it is, if we're not too far away, I'd
> create an PR build check for it and keep it (otherwise, bye bye)
>
> *jdbc-spatialite*
> Think we already decided it should be demoted time ago, no maintainer and
> outdated spatialite version included in
> the jars. Guessing it did not happen yet due to lack of time. Gonna put
> some efforts towards making it happen
>
> *jdbc-teradata*
> Same situation as db2 I believe. Tried to connect to the original author
> on this S.O. thread, so far got
> no answer:
>
> https://gis.stackexchange.com/questions/268871/tessellation-in-teradata-is-deprecated-but-geoserver-expects-it-to-improve-spat?utm_source=dlvr.it&utm_medium=twitter
> I'd say, move to unsupported if nothing changes in the next couple of
> weeks.
>
> Comments welcomed!
> Also, can you think of any other module lacking both maintainers and tests
> actually running?
>
> 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.*
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to