Hi all, Internal priority shifts stalled the continuation of this discussion until now. We at Camptocamp managed to release the second stable prototype of the Cloud Native GeoServer project and are now in a position and willing to proceed with donating it to the GeoServer community.
Here's the current project URL: https://github.com/camptocamp/geoserver-microservices While I'm working to generate more documentation, it'd be good to gather your feedback. Two courses of action have been mentioned previously: making a proposal (which I take as a GSIP), and that the parties involved fill in a "Software Grant and Corporate Contributor License Agreement" naming the project in order to donate it to OSGeo. Given the project can't be put as a community module (technically it's a separate, spring-boot project, and conceptually it's not a GeoServer extension but a complete overhaul on its configuration and deployment mechanisms), the logical choice would be to host it as a sibling project at GeoServer's Github organization. So as for the proposal, I'm not sure a GSIP fits, although there're valuable components developed under this new project that could well be subject of GSIPs to make their way upstream, such as improvements in the design of the catalog/config subsystem, event-based synchronization, and Jackson-databind bindings for all Catalog and Config objects, including GeoTools Filters. Yet, since there's probably no other prescribed process to support this sort of donation, at least to the best of my knowledge, we could probably abuse/extend the GSIP scope. What are the precedents in that regard? Has the landing of GeoFence as a sibling project gone through something similar? As for granting rights to OSGeo, Camptocamp is willing to do so, so if you could point out how to proceed, I'd be glad to pursue it, once the PSC establishes the contribution can proceed. That's it for now, looking forward to your comments. Gabriel. On Wed, 9 Sept 2020 at 13:48, Gabriel Roldan <[email protected]> wrote: > Hi Jody, > On Tue, 8 Sep 2020 at 23:27, Jody Garnett <[email protected]> wrote: > >> Morning Gabe: >> >> Just getting back after a long weekend, I look forward to reviewing your >> repo and approach (although you covered some of this in geoserver meetings >> in the last month). >> >> It is good to know the intention to include in the community, perhaps a >> proposal can be started now to collect notes and feedback. >> > > Yeah, that's probably the best course of action, just looking for > consensus, let's see if someone else chimes in. > > >> The CODE_OF_CONDUCT.md presently lists Simone as a contact person, >> perhaps you can fill you in your contact details there while this is under >> development. >> > Done, good catch. > > >> A proposal is also useful to establish what work/resources is needed so >> the geoserver community is in a position to accept. >> >> When the time comes, for large contributions like this, we will no doubt >> ask that the parties involved fill in a "Software Grant and Corporate >> Contributor License Agreement" naming the project in order to donate it to >> OSGeo. This is how GeoServer and GeoWebCache were placed in the care of >> OSGeo. >> > > Sounds absolutely reasonable. > > >> >> Thanks for both starting this off Gabriel, and doing so with open >> communication. >> > > No problem. As mentioned on the PSC meetings, I waited until I was > confident the approach is proved feasible, given basically the complexity > of it all when it comes to splitting out such a monster into smaller > pieces. Of course, there's a lot to figure out yet, but some of the biggest > questions have been answered in the prototype phase, so, cool. > > >> -- >> Jody Garnett >> >> >> On Sat, 5 Sep 2020 at 20:24, Gabriel Roldan <[email protected]> >> wrote: >> >>> Hi all, >>> >>> I'd like to introduce this project to all developers. Some might know >>> about it already from a couple PSC meetings ago >>> https://github.com/camptocamp/geoserver-microservices. >>> >>> First and foremost, let me note that I've taken the liberty to use, at >>> least for the time being, the org.geoserver.cloud namespace, name the >>> project "Cloud Native GeoServer", and use directly other material from >>> GeoServer - like the LICENSE.md, CODE_OF_CONDUCT.md, and CONTRIBUTING.md >>> files - because both Camptocamp and the customer funding it intend to >>> donate it in its entirety to the GeoServer community. So, following further >>> discussion, may it not be acceptable to be somehow incorporated to >>> GeoServer's code-base, I'll take care of remedying that. >>> >>> In terms of donating the code, my preference would be for it to become a >>> sibling project inside GeoServer's github organization, being in nature a >>> separate project that "uses" GeoServer components, and moving any module >>> that extends GeoServer's capabilities, as community modules, so they can >>> also be used in its traditional form. >>> >>> Secondly, let me encourage any interested party in participating by >>> asking questions, trying it out, submitting bug reports, providing patches >>> of course, etc. Read the project's README, and let me know if there's >>> anything to clear up. >>> >>> I haven't set up a mailing list or other sort of discussion forum other >>> than the github issues itself. May this project become part of the >>> GeoServer community, we could decide together the best course of action. >>> >>> Needless to say that this is very much work in progress, I'm glad and >>> confident to send this email having it proved a feasible approach to build >>> a microservices-architecture incarnation of our beloved GeoServer. >>> >>> Best regards, >>> -- >>> Gabriel Roldán >>> >>> _______________________________________________ >>> Geoserver-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> > > -- > Gabriel Roldán > -- Gabriel Roldán
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
