> 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 ------------------------------------------------------------------------------ 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
