Closed GoogleCodeExporter closed 9 years ago
Definitely yes. We'll use dual licensing, if necessary. Can you help us to
solve this
issue ?
Original comment by hdar...@gmail.com
on 16 Nov 2007 at 2:11
Awesome news! :)
Sure - its just a simple matter of saying that the project is licensed under
either LGPL or (say) BSD / Apache /
Artistic. (Apache 2.0 is the easiest http://apache.org/licenses/ but pick any
suitable one:
http://people.apache.org/~cliffs/3party.html)
See : http://dojotoolkit.org/book/dojo-book-0-9/introduction/licensing
to change the license you just need the permission of all the committers to
agree to the new license terms.
Original comment by james.st...@gmail.com
on 16 Nov 2007 at 3:05
LGPL v3 is compatible with the Apache licence, as you could see on the graphic
in
this page:
http://www.gnu.org/licenses/quick-guide-gplv3.html
Hope it helps.
Original comment by jrd...@gmail.com
on 29 Nov 2007 at 3:22
Unfortunately it doesn't help as things don't work the other way around.
Here's a list of all the licenses which are allowed at the Apache Software
Foundation
http://people.apache.org/~cliffs/3party.html
i.e. Apache projects can't touch anything *GPL at all. The same is true of the
company I work - and I know of lots of other companies who explicitly disallow
the
use of *GPL due to its viral nature.
So Apache folks like me can't touch Tatami - so we'd have to create a Tatami
like
open source project to provide GWT wrapping of DOJO using DOJO's Apache license
if we
wanted to use GWT and DOJO.
Which kinda means we'd not be able to work with Tatami at all and would have to
clone
it - just because you chose to use a different license to DOJO itself which
seems odd.
Original comment by james.st...@gmail.com
on 29 Nov 2007 at 3:30
Original comment by rdunk...@gmail.com
on 11 Dec 2008 at 3:02
Original comment by rdunk...@gmail.com
on 18 Dec 2008 at 6:35
Original issue reported on code.google.com by
james.st...@gmail.com
on 16 Nov 2007 at 12:19