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