hi regine, IANL! But my interpretation is this.
1. client, server and middle war are separate things, to be considered separately 2. if you implement the client, using the qooxdoo SDK, you are free to pick any license you want for the client, BUT if you make changes to the qooxdoo class files, these changes have to be made available TO YOUR CUSTOMERS under the LGPL. 3 if you run the server as a service, so the customer does not get to run his own copy, the you do not have to publish any source even if the server employs GPL components. The only case you would have to license things to you customers would be if you used components licensed under the Avero GPL or Avero LGP hth tobi Tobias Oetiker t...@oetiker.ch 062 775 9902 > On 08.11.2014, at 03:21, Reggaeny <regine.rosew...@hoellenberg.biz> wrote: > > May be, I'm a bit dim-witted. So I will try to put my question a bit more > precise. > > We (that's the start-up I'm working for) are going to develop a software > platform roughly consisting of three components - a server, a middleware > and a client - whereas the client should have a desktop, a browser and a > mobile shape. The platform is to be used in an enterprise / business > environment. > > The actual candidates for the client development are ExtJs (unfortunately > very expensive and limited concerning their licensing policy), Dojo and > qooxdoo. > > We won't have any problem if the client component would be absolutely > open-source in a way that our customers - and qooxdoo - would have unlimited > access to the sources of the client component. The other two components - > means everything that runs on a server - should have to be completely > separated concerning the licensing - means that our customers will have to > buy the server and client components separately - whereas the > server-components could be open-source as well -. > > Is that target strategy limited by the LPGL/EPL licensing or not? > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Coming-from-Sencha-ExtJs-tp7586356p7586367.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
