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
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: