This project was originally LGPLv+-licensed to encourage its use in a community
that is largely copyleft-phobic. After further reflection, that was a mistake,
as adoption is not the important factor here---software freedom is.
When submitting ease.js to the GNU project, it was asked if I would be willing
to relicense it under the GPLv3+; I agreed happily, because there is no reason
why we should provide proprietary software any sort of edge. Indeed, proprietary
JavaScript is a huge problem since it is automatically downloaded on the user's
PC generally without them even knowing, and is a current focus for the FSF. As
such, to remain firm in our stance against proprietary JavaScript, relicensing
made the most sense for GNU.
This is likely to upset current users of ease.js. I am not sure of their
number---I have only seen download counts periodically on npmjs.org---but I know
there are at least a small number. These users are free to continue using the
previous LGPL'd releases, but with the understanding that there will be no
further maintenance (not even bug fixes). If possible, users should use the
GPL-licensed versions and release their software as free software.
Here comes GNU ease.js.
Growing much closer to releasing. Hopefully in the next couple of days; I just
don't want to rush it. Though, at the same time, I've been noticing projects
popping up with very similar / exact names to this one. A project named "ease"
was added to the npm repository and another "ease.js" is on GitHub, although
it's made no progress. As such, I want to ensure I reserve the name in npm.
I've been testing the new library and work and noticed only a couple minor
issues, primiarly due to misuse of the library. Looking good.
Mike Gerwitz