Thanks everyone for the discussion and consideration for this proposal. Since all the PSC members casted their vote, I've transitioned the proposal to in-progress, and created this JIRA ticket to track progress: https://osgeo-org.atlassian.net/browse/GEOS-10913
It contains subtasks for the identified steps to completion. Cheers, Gabe *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Gabriel Roldan* Geospatial Developer On Tue, Mar 28, 2023 at 1:52 PM Torben Barsballe <torbenbarsba...@gmail.com> wrote: > After catching up on the background of 216 along with this proposal, the > approach makes sense to me. > One piece I didn't see covered is build/release infrastructure for the new > project - since it is now independent from geofence I assume it will be its > own group on jenkins, but we can deal with that when we get there. > > +1 > > Cheers, > Torben > > 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
