-
Notifications
You must be signed in to change notification settings - Fork 65
Add LICENSE file #97
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
Comments
Sounds good to me!
…On Thu, Jun 8, 2017 at 20:42 Phil Freeman ***@***.***> wrote:
I noticed this repo has never had a LICENSE file which is ... not ideal.
Since this package appears as a dependency of several others, I think it's
important for it to have a clear license.
The line "license": "MIT" was added to bower.json fairly early on (commit
e36352c
<e36352c>),
which I interpret to mean that this library has been MIT-licensed
implicitly since then. I suggest we adopt the MIT license with a copyright
notice assigning copyright to "the purescript-react contributors" or
something along those lines.
cc @andreypopp <https://github.com/andreypopp> @joneshf
<https://github.com/joneshf> @ethul <https://github.com/ethul> Does that
sound good?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#97>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAVYy3HnJOlZ2yGGLunqThXtXPTEkAsSks5sCJUMgaJpZM4N0x9S>
.
|
Merged
Same. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed this repo has never had a LICENSE file which is ... not ideal. Since this package appears as a dependency of several others, I think it's important for it to have a clear license.
The line
"license": "MIT"
was added tobower.json
fairly early on (commit e36352cb21a), which I interpret to mean that this library has been MIT-licensed implicitly since then. I suggest we adopt the MIT license with a copyright notice assigning copyright to "the purescript-react contributors" or something along those lines.cc @andreypopp @joneshf @ethul Does that sound good?
The text was updated successfully, but these errors were encountered: