Hi simo,
simo schrieb:
On Wed, 2007-02-28 at 11:54 +0100, Dietrich Streifert wrote:
Hi Jens,
Thank you for your elaborately answer.
So let's get to a practical example:
I'm going to develop a web application which uses qooxdoo as UI/AJAX
framework and as building system. I'm creating my own widget/class
hierarchie which inherits from qooxdoo classes. This web application
will be sold and deliverd to a customer which installs the web
application on his webservers. The customer will get the web
application as a compiled/optimized/obfuscated JavaScript file (built
by the qooxdoo build system) with additional html files and a backend
(java/php/perl).
What do I need to do in order to fullfill the EPL/LGPL license of
qooxdoo?
Is it enough to add something to the web applications license file
like:
"This software was created using the qooxdoo AJAX framework
http://www.qooxdoo.org which is dual licenced
under the LGPL license http://www.gnu.org/licenses/lgpl.html and EPL
license http://www.eclipse.org/legal/epl-v10.html.";
Do I additionally have to supply the customer with the qooxdoo source
code or is it enough to point the customer to the qooxdoo web site
where he is able to download the code?
Hi Dietrich,
the LGPL license is quite clear on this point, you have to give the user
the source code. You can do that on premises by including it on the
package (this is usually the best idea as it frees you from any other
obligation), or you can give a written offer valid for three years where
you state you will give the source as soon as it is requested at no
additional cost.
Yes but we have additionally qooxdoo under EPL license which seem to be
less restrictive. So then I will give the customer a copy of the qooxdoo
sdk which I've downloaded from sourceforge. Is this sufficient? Or do I
have to give my sourcecode as well to the customer?
I see you plan to offer obfuscated code, pay attention that the LGPL
license requires that you make it possible for the customer to
substitute your version of the LGPL licensed library with another (a new
version with maybe fixed bugs for example). So you must distribute your
code in a way that make it possible for the user to easily do that.
This does not meant you must also offer any warranty if the code breaks
if the user changes the LGPL library, but you can't prevent it, nor
legally, nor technically.
As I said I'm planing to use the qooxdoo build system which optimizes
local variables and strings and leads by using it to "obfuscated" code.
The result of the qooxdoo build is combining qooxdoo with my code. So
how would the customer ever be able to "replace" the qooxdoo part with
a new version? Does everybody who uses the qooxdoo build system
automatically violate LGPL?
Simo.
--
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
