Your proposal is straightforward and to the point, some feedback for discussion:
- I would title the proposal "GeoServer ACL project" (as the important part is a new project; rather than the repository where it is located). - One thing I would like addressed in the proposal is indicating how to keep the project in sync with the geoserver update cycle? I do not wish to be in the situation where an "official" geoserver project is running against an unsupported version of geoserver. - The proposal covers publishing maven artifacts which would be done from build.geoserver.org (as I do not wish to see credentials scattered across systems). Suggest that "GeoServer ACL" main branch track GeoServer main branch in order to stay in sync and releasable? Taking the geoserver acl client community module to an extension would also meet this goal. -- Jody Garnett On Tue, Mar 21, 2023 at 6:23 AM Gabriel Roldan < gabriel.rol...@camptocamp.com> wrote: > Hi all, > > as discussed in the "GSIP-216 GeoFence 4.0.x" email thread, I've created a > new GSIP to request hosting the GeoFence fork, called GeoServer ACL, as a > sibling project to GeoServer, GeoFence, and GeoServer Cloud, under the > /geoserver Github organization. > > Please see https://github.com/geoserver/geoserver/wiki/GSIP-217 for > details, comment back and vote. > > Best regards, > Gabriel. > *camptocamp* > INNOVATIVE SOLUTIONS > BY OPEN SOURCE EXPERTS > > *Gabriel Roldan* > Geospatial Developer > > _______________________________________________ > 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
