We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@blond @zxqfox do we need to force MPL-2.0 here too, or this is not so important?
The text was updated successfully, but these errors were encountered:
@tadatuta?
Sorry, something went wrong.
I don't see any reason not to use MPL-2.0 in any of our repos.
Can we use package.json-fields to describe authority and licenses instead of putting LICENSE-file in each repo since package.json has license field?
package.json
LICENSE
license
@zxqfox and don't forget about README =)
No branches or pull requests
@blond @zxqfox do we need to force MPL-2.0 here too, or this is not so important?
The text was updated successfully, but these errors were encountered: