On Mi, 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?
Both is OK from my point of view.
Beside all licensing stuff it's even preferable from my point of view to
push people to our website, so if they are really interested in qooxdoo
they'll usually get a newer version than they had when you only supply
your current package.
The only problem that I can see with the LGPL is to make sure that the
customer is able to replace the LGPL lib with a changed version. This
seems to be a bit problematic with the way the qooxdoo build process
works, and I currently don't see a perfect answer.
The LGPL or similar licenses have a well known problem with things like
JavaScript (or even other OO languages) because all the wording with
linking and so on is clearly more suited to old fashioned C programming,
where you have object files that could be relinked and so on - even C++
doesn't really work correctly with the license wording as far as I
remember.
For us, the spirit of language was always the guiding principle: We want
to encourage even commercial use, but we want to prohibit that anybody
changes qooxdoo ITSELF in a closed, proprietary way.
By the way: The customer of your customer (the user of the webapp) is of
course in no way the target of the licensing stuff. The indirect use of
qooxdoo does in no way create an obligation for you to provide anything
(even information) about qooxdoo or it's license to them.
jtl
-------------------------------------------------------------------------
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
