[Incubator] Application for the library "GeoServerPHPClient"tobecome a OSGeo Community project

Jody Garnett jody.garnett at gmail.com
Wed Feb 13 10:00:25 PST 2019

I was more meaning the GeoServer GitHub, once reason to consider recruiting
gsconfig, geoserver-rest-client and others is to make it easier to find
these libraries (and perhaps easier for these libraries to attract
Jody Garnett

On Wed, 13 Feb 2019 at 09:07, Ian Turton <ijturton at gmail.com> wrote:

> On Wed, 13 Feb 2019 at 14:55, Jody Garnett <jody.garnett at gmail.com> wrote:
>> There is probably no reason not to do both?
>> As for joining the GeoServer GitHub ... the GeoFence project did it
>> (moving from GeoSolutions to GeoServer GitHub). So we can check email
>> archive to see how they did it ... probably just asked.
>> There is a difference in license AGPL vs GPL to consider between the
>> projects.
> The difference is that one (GeoFence) is a plugin that is added to
> GeoServer  and so makes sense to be part of the GeoServer project and the
> other is a project that uses the GeoServer API and as such should be a
> standalone project in the same way as GeoManager
> <https://github.com/geosolutions-it/geoserver-manager>,
> geoserver-rest-client
> <https://github.com/marcjansen/geoserver-rest-client>, gsconfig
> <https://github.com/boundlessgeo/gsconfig> and probably dozens of other
> clients. You might as well say that QGis belongs in side geoserver because
> it can handle WMS and WFS requests.
> I see no reason at all to start adding client code to the GeoServer code
> base.
> Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20190213/fc15d8dc/attachment.html>

More information about the Incubator mailing list