« Return to Thread: GPL + Classpath for Dispatch Interfaces?
Re: GPL + Classpath for Dispatch Interfaces?
by Justin Deoliveira-6
::
Rate this Message:
My comment about the web application was without it I don't see any
license unrestrictions being very useful, because without at least some
web support you can't run geoserver.
So the idea was to make web-app, and part of web-core GPL + classpath
and leave all the other web modules GPL. This would give someone at
least something runnable with the plugin system at their disposal, they
would just get a blank UI starting it up.
And yeah, output formats are tricky. If we want to keep WFS/WMS GPL that
means someone would not be able to write a proprietary output format for
geoserver. But if we make those modules LGPL/GPL+Classpath then we might
as well make all of geoserver that.
Jody Garnett wrote:
>> Hmmm... I would prefer to keep the UI pure GPL. Usually my preference is:
>> - LGPL for anything library-sh
>> - GPL for anything that sounds like an application
>>
>> The web UI is application imho. We could have some bits of it in LGPL,
>> like the base page classes and the raw components, but I'm quite -1
>> on having the catalog configuration pages go LGPL.
>
> We are talking GPL+Classpath Exception (not LGPL) but yeah I hear you.
> I think the goal here is to allow modules to provide additional
> configuration UI (not to hand over the catalog configuration pages).
>
>> Moved in a more central place, yes, turned in LGPL, hmmm... don't like
>> that much. I mean, if we follow this line we end up turning LGPL significant
>> portions of GeoServer, at that point we may as well change
>> its license solid
>
> I am a bit confused as to how much of the code base we are talking
> here; for dispatch we only need to relax the GPL on the interfaces we
> are expecting others to implement; not on the implementation that
> wires it all up and makes it sit up and beg for coffee? Same deal for
> output formats...
>
> Jody
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
license unrestrictions being very useful, because without at least some
web support you can't run geoserver.
So the idea was to make web-app, and part of web-core GPL + classpath
and leave all the other web modules GPL. This would give someone at
least something runnable with the plugin system at their disposal, they
would just get a blank UI starting it up.
And yeah, output formats are tricky. If we want to keep WFS/WMS GPL that
means someone would not be able to write a proprietary output format for
geoserver. But if we make those modules LGPL/GPL+Classpath then we might
as well make all of geoserver that.
Jody Garnett wrote:
>> Hmmm... I would prefer to keep the UI pure GPL. Usually my preference is:
>> - LGPL for anything library-sh
>> - GPL for anything that sounds like an application
>>
>> The web UI is application imho. We could have some bits of it in LGPL,
>> like the base page classes and the raw components, but I'm quite -1
>> on having the catalog configuration pages go LGPL.
>
> We are talking GPL+Classpath Exception (not LGPL) but yeah I hear you.
> I think the goal here is to allow modules to provide additional
> configuration UI (not to hand over the catalog configuration pages).
>
>> Moved in a more central place, yes, turned in LGPL, hmmm... don't like
>> that much. I mean, if we follow this line we end up turning LGPL significant
>> portions of GeoServer, at that point we may as well change
>> its license solid
>
> I am a bit confused as to how much of the code base we are talking
> here; for dispatch we only need to relax the GPL on the interfaces we
> are expecting others to implement; not on the implementation that
> wires it all up and makes it sit up and beg for coffee? Same deal for
> output formats...
>
> Jody
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
« Return to Thread: GPL + Classpath for Dispatch Interfaces?
| Free embeddable forum powered by Nabble | Forum Help |
