Hi guys,

I agree a link would be best. The compatibility matrix sounds like a great 
idea, but for GeoMesa at least, would be largely empty - our releases aren't 
synced up with GeoServer, and we don't have the bandwidth to test every version 
for compatibility. We've had regressions in the past from upgrading just bug 
fix versions of GeoServer, so we don't feel comfortable advertising 
compatibility past the specific version we test and release against. In our 
documentation, we have a chart[1] with the versions tested and the versions 
that should probably work, but I think having a link from specific GeoServer 
release version page would imply more robust compatibility than we offer most 
of the time (or the link would be missing for most releases, which also doesn't 
seem great).

Thanks,

Emilio Lahr-Vivaz
General Atomics, CCRi

[1] https://www.geomesa.org/documentation/stable/user/geoserver.html

________________________________
From: Andrea Aime <andrea.a...@geosolutionsgroup.com>
Sent: Friday, August 23, 2024 4:51 AM
To: Jody Garnett <jody.garn...@gmail.com>
Cc: Geoserver-devel <geoserver-devel@lists.sourceforge.net>
Subject: -EXT-Re: [Geoserver-devel] How to handle "external" community modules


WARNING:  This message is from an external source.  Evaluate the message 
carefully BEFORE clicking on links or opening attachments.

I vote for the least maintenance effort: a simple link.
And maybe add to the RC release procedure, a step to check if the links are 
still valid (a once every every six months task)


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


On Thu, Aug 22, 2024 at 9:16?PM Jody Garnett 
<jody.garn...@gmail.com<mailto:jody.garn...@gmail.com>> wrote:
We have had both GeoMesa and GeoStyler as community modules which have returned 
to external GitHub repositories for long term maintenance.

The PR<https://github.com/geoserver/geoserver/pull/7834> to remove GeoMesa 
resulted in an interesting discussion which I would like to share with the 
mailing list, and turn into a proposal.

Two ideas:

  1.  Add a section to the docs linking to "other" community 
modules<https://docs.geoserver.org/latest/en/user/community/index.html#community>;
 or

Pros: Easy doc change
Cons: Easy for the information to become stale, hard to check compatibility

  2.  Add download pages / links to the website.
- Teams would make a page, with page metadata indicating compatibility.
- Links would be shown on download page(s) for compatible releases.
- Download page could have an "Other" tab listing these pages.

Pros: Better user experience, content is not shown when stale.
Cons: Harder upfront with some ruby development. Teams (GeoFence, GeoMesa, 
GeoStyler) are responsible for "publishing" their release on the geoserver site 
(ie updating their page).

I kind of like the website idea - something like:

/other/geomesa/index.md

---
layout: other
title: GeoMesa
release:

     *   2.25.1: 5.0.1
     *   2.25.0: 5.0.0
     *   2.22.2: 4.0.0

max-version:
website: https://www.geomesa.org/
---
# GeoMesa

GeoMesa is an Apache-licensed, open-source suite of tools that enables 
large-scale geospatial analytics on distributed computing systems, letting you 
manage and analyze the huge spatio-temporal datasets that IoT, social media, 
tracking, and mobile phone applications seek to take advantage of today.


- -
Jody Garnett
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net<mailto: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