Gabe: My initial feedback is - wow that is a big risk doing a month of work without having GSIP on the table for discussion on technical direction. Point of the proposal process is to reduce risk for camptocamp and community interaction to avoid being left with either a lot of re-work or a fork as indicated by your 4.x version number :)
In the future try to align GSIP process with some kind of design milestone for your customer; so you can get confirmation from your customer and the community before sinking a ton of budget into activity. It could be you found it easer to do a proof-of-concept and then share the design for discussion; but I wish to ensure you have budget for collaboration and compromise in reserve. Basic project management stuff for both geoserver and Camptocamp I admit; but it is important to control risk using the communication tools we have. For the actual proposal I am presently -0; since I do not feel knowledgeable on geofence and do not have active customers using the technology. It would be much easier for collaboration if each one of the risks you mentioned were his own GSIP; as the all-or-nothing thing makes discussion difficult to follow. If I understand: 1) Google's Generic DAO Framework --> what is the proposed solution for this? Looks like it may be some automatic code generation? Hard to see 2) Hibernate Spatial 1.1.3.2 replacement --> upgrade What is the impact of upgrading to a newer version? Migration challenges for existing users to address? reading: I see you identified h2 upgrade as a problem. I think this is a key upgrade that is blocking work :( 3) REST API differences between standalone and embedded --> definition of a new OpenAPI 3.0 interface What is impacted by this? Is it just the integration between geoserver and geofence or is there more functionality (such as GeoNode or MapStore) that requires care? reading: I see you acknowledge the REST API change. Is it possible to run both a v1 and a v2 rest api concurrently? We will need to hear from the community what the impact of this change is. It is always hard when your work impacts others as you need to ensure they have budget to proceed with the change. 4) Use of spring RMI --> Repository adapters? Not sure I follow the approach. -- Jody Garnett On Tue, Mar 7, 2023 at 6:34 PM Gabriel Roldan <gabriel.rol...@camptocamp.com> wrote: > Hi list, > > I've just created a GSIP (216) with a proposal to make several > improvements to GeoFence. > > Please see https://github.com/geoserver/geoserver/wiki/GSIP-216 for > details. > > *camptocamp* > INNOVATIVE SOLUTIONS > BY OPEN SOURCE EXPERTS > > *Gabriel Roldán* > 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
