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. 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. 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. Thanks for both starting this off Gabriel, and doing so with open communication. -- 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 >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
