[Users] I wonder Geoext license

[Yves Moisan]

> 
> You are right Eric. Ext Core only dontains Ext.data.Connection, and 
> GeoExt.data.* components require higher levels of Ext.data.*, which are 
> part of ExtJS.

I did a bit of searching about Ext 3.0 licensing and my understanding is
that everything but core will be under the same dual-licensing as Ext
2.2.  Is that what everyone understands ?  

I want to be clear on the implications at customer premisses.  We
recently had a case where we woke up to the fact the Google API can't be
used behind a firewall, so we don't want to find out a particular web
app deployed at customer X violates the GPL v3 and we have to buy a
"developer" license.  Or rather we want to know beforehand.  

What does it mean for a particular customer instance where there won't
be any developers anyhow ?  I need clear guidelines to make sure what we
deploy at the customer premisses is clear of all EULA's/Terms of all the
different pieces our solution, and for that matter any typical
GeoExt/MapFish/OpenLayers solution, contains.  There are many strings in
the software stack, especially when one starts using the
sphericalMercator types ...  

Maybe a "legal" doc section (on the OSGeo site ?) could be started to
give people general guidelines and point them to attorneys in the case
they're in doubt.  That page could contain a series of possible software
combinations both on the server side and the client side and data used
(OSM, Google ...).  Maybe just a list of the licenses used by the
different OSGeo projects (regular or in incubation) *including* their
dependencies and a list of data providers with their terms of use would
be a start.  It's so easy adding a Google layer (especially since
everyone wants it on their sites) that people forget about the
strings ...  Maybe some jurisprudence can be slowly accumulated there so
people can have comparisons they can make with their particular customer
settings?  

Yves