Clarify license for the project and individual packages

[mbrukman]

First, thank you for building and sharing this project with us!

Disclaimer: I am not a lawyer, and this is not legal advice; I just have some questions as this project's licensing is confusing.

There's no LICENSE file in the root of the repo, but the top-level package.json says this project is MIT-licensed:

noya/package.json

Line 6 in 6fa07b1

"license": "MIT",

So maybe it would be worthwhile to include the license from https://choosealicense.com/licenses/mit/ to clarify it, and GitHub will also add a badge to the repo to clarify that it's MIT-licensed for every visitor.

---

Having said that, some packages say they're "unlicensed", e.g.,

noya/packages/canvaskit/package.json

Lines 1 to 6 in 6fa07b1

	{
	"name": "canvaskit",
	"version": "1.0.0",
	"main": "src/index.ts",
	"license": "UNLICENSED"
	}

which the NPM docs suggest using when you don't want to grant any rights to use packages:

Finally, if you do not wish to grant others the right to use a private or unpublished package under any terms:

{
  "license": "UNLICENSED"
}

This seems to be in conflict with the MIT license above: if some of the modules are unlicensed, and they're required, it's unclear how someone might use this project, if they can't use these modules.

Could you please clarify the overall license for the project, and the licensing for each individual module?

Thank you!

[dabbott]

Hi! Thanks for the comment. I'll try to get the license sorted out soon.

It will very likely be Apache 2.0. We may dual license MIT or something else.