-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change license
in package.json
#1140
Comments
Ah yeah, thanks for catching @KiwiKilian. Which tools do you use to check for license automatically? |
Currently this one: https://github.com/RSeidelsohn/license-checker-rseidelsohn |
Also see #1141 as slightly related. |
Going to release an update with the changes we discussed, thanks for the feedback! I noticed the FSL license doesn't have a SPDX license identifier which npm docs mention should use |
I think it's fine, as it's the current proposed SPDX identifier, see spdx/license-list-XML#2458. Thank you for your thoughtful consideration! |
Thanks for including the thread, I enjoyed the discussion and further threads linked there. I think it's fair to add a license section on the website to explain the choice. Hopefully the adoption doesn't become problematic as a result of this change |
Description
The new license should be reflected within
package.json
like this:This is important for automated license checking to work.
Reproducible example or configuration
No response
OpenAPI specification (optional)
No response
System information (optional)
No response
The text was updated successfully, but these errors were encountered: