On Mi, 2007-02-28 at 01:11 +0100, Fabio Mino wrote:
> Hi all,
> i downloaded qooxdoo two weeks ago and i'm very impressed: great work
> I started using it (i'm trying to convert a Visual Basic project to a web
> application), but now i have a doubt: is it possibile to use qooxoo for a
> commercial project?
>
> I read the two licenses (LGPL and EPL) and if i understand well, the answer
> is NO :(
The answer is YES if you met the following condition:
Your project is USING qooxdoo in its supplied form. E.g. You are doing
some webapp that uses qooxdoo classes to build up it's interface or you
are using your own UI classes that (by inheritence) depend on qooxdoo
classes. You can use qooxdoo without having the need to also change your
own source code to something like EPL, LGPL or the dual licensing
scheme. You need to supply the qooxdoo source package with you
application (or at least give your customers the possibility to get it)
- if you don't supply your webapp (because it's server based) of course
there's no need to e.g. provide some download link inside of the app -
although of course we would be happy for some mentioning of "made with
qooxdoo + link" on the about page...)
If you try to build a webapplication UI framework where you are changing
qooxdoo itself and try to sell the resulting, expanded qooxdoo, you can
still do that provided that the license you put the resulting entity
under is LGPL, EPL or the dual licenensing thing (which for most people
means that they in effect CAN'T sell it, because everybody has the right
to request the source code and give it away themself for free thereby
undermining any wish to commercially exploit it).
To reiterate in other words: Your own code and your own classes can be
used as you wish, we don't force any license on you. But changes to
qooxdoo itself MUST be supplied under the same Open Source licenses. If
you change qooxdoo by using e.g. some code that is LGPL only, you are
free to do so and use the whole of qooxdoo under the terms of the LGPL.
If you have a piece of code exclusively under the EPL you can also use
it and use the resulting entity under the terms of the EPL.
Most people who really change something in qooxdoo itself don't want to
administer their own patches or fork, but tend to be interested that
their changes go back to the main project. We have the additional
request that every code that goes into qooxdoo proper must comply to
BOTH EPL and LGPL (or be compatible with both like stuff licensed under
the BSD license) because we want the whole of qooxdoo be able to be used
under both licenses.
The reason for the complicated dual licensing thing is that we want to
give pure EPL and pure LGPL projects the possibility to use qooxdoo but
unfortunately the two licenses are (although similar in spirit)
incompatible in wording.
Hope this helps
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
