Why was the GPL license selected?

3 views
Skip to first unread message

Mikko Rantalainen

unread,
Feb 9, 2010, 9:20:24 AM2/9/10
to js-mindmap
I find js-mindmap interesting but I think it cannot be often used
because of the license. The GPL prevents use of this library with e.g.
practically any other open source license and every closed source
software. In addition, a strict interpretation of GPL licensing terms
makes me think that I couldn't even use this library in a blog message
or CMS unless that blog or CMS is licensed under GPL (e.g. it would
not be legal to blog about this library and embed a live js-mindmap
inside the blog at blogspot.com).

If this is not your intention, I'd suggest changing the license to
e.g. LGPL which prevents closing the source but does not prevent one
from using this library on top of a system with different license.

On the other hand, if this is intentional and the GPL has been
selected on purpose, I'd suggest saying it so on the front page of the
project. I personally find it a bit hard to understand what GPL really
means when applied to a JavaScript library so I'd at least want an
opinion from the author.

Regards,
Mikko

kenneth

unread,
Feb 9, 2010, 9:33:47 AM2/9/10
to js-mindmap
Mostly because I'm not a lawyer. :)

I've switched to MIT license, and added comments to that effect on
homepage.
Haven't updated the license definition in the code yet, but will with
v0.4.
Essentially, it would be nice to get credit, but otherwise do as you
will.

K

On Feb 9, 2:20 pm, Mikko Rantalainen <mikko.rantalai...@gmail.com>
wrote:

Reply all
Reply to author
Forward
0 new messages