Licensing issues
rhblind opened this issue · 4 comments
This library is GPL v2 licensed. When bundled in a front end application this will trigger clauses in the license which will force us to GPL license our frontend application, as we are effectively redistributing the source code by transferring it to the clients browser.
Is this intentional, or would it be possible to evaluate alternate licenses in able to let people use this library in front end applications?
Other than that, thanks for the great library!
Sorry for getting to this late. I actually hadn't considered the frontend case, since it was intended initially for the backend. What kind of license would help? LGPL?
Hi thanks for reply. Any kind of license which doesn't require the user to open source the project if the library is redistributed in it. I usually use Apache v2.0 or MIT licenses, but you should choose a license based on your intent with the library.
The project is currently listed as LGPL, but I noticed an issue in the project.json causing it to be parsed wrong by some tools.
The license type field should be "LGPL-3.0-only" or "LGPL-3.0-or-later" instead of a descriptive text string.
(https://spdx.org/licenses/). NPM's website is showing the package license as "unknown" as a result.
Fixed (at last!) by using LGPL-2.0-or-later