That is fine by me. Just thinking out loud, in terms of having the least
amount of moving parts, since GeoSever cloud is already depending
on GeoServer, would it make sense to have a GeoServer community module with
all the "library" parts, as well as a module generating
a Spring Boot jar for stand
Update to GSIP with additional details, such as adding a repo.
Personally I would like these other geoserver repos to match geosever
release cycle from a QA standpoint.
On Thu, Mar 16, 2023 at 7:58 AM Gabriel Roldan <
gabriel.rol...@camptocamp.com> wrote:
> Hi Andrea, Emanuele, and all.
>
> Than
Hi Andrea, Emanuele, and all.
Thanks for this counter-proposal. It makes a lot of sense, and at
Camptocamp we just met and decided it's a good way forward.
The project will be called GeoServer ACL, as in Access Control List.
It will have a somewhat more limited scope than GeoFence, at least
init
Andrea Aime (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae9469ffc-5e16-4c2b-b7b0-b9c46e912f9e
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMGRhODlmNjViNjQ2NDBkN2I3ZmM2ZDg3MzQxZTRjMTMiLCJwIjoiaiJ9
) / Improvement
