-
Notifications
You must be signed in to change notification settings - Fork 910
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
New license #1203
Comments
Great point @Aspie96! @mwweinberg: What do you suggest we do to address this? Would it be best to copy and paste the ml5.js License into this repository, or would it be sufficient to write something like "Please see our license and code of conduct..." in the LICENSE file. Presumably, we'd probably want to generalize this approach to all of our ml5.js repositories. |
That's a fine point. It would be best to copy and paste the license itself. When that happens, we should probably change the header that reads:
to read:
|
I am quite confused.
The README mentions the new license:
But the repo still contains only the old one.
While if there are contributions the old license must of course be preserved to avoid a VCR kind of fiasco, it's not clear to me which license applies.
Is it the MIT license, which is what GitHub detects and which is in the LICENSE file, a standard way of identifying the license?
Or is it the one mentioned in the document?
The text was updated successfully, but these errors were encountered: