-
Notifications
You must be signed in to change notification settings - Fork 130
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
Open Source License #151
Comments
The package.json adds "MIT". I am not a license pro, but isn't that enough? |
mm im not sure honestly, i think it would be best to add to the repo a LICENSE file, e.g
And then no one would have any doubts and it will be clear immidiatly to anyone who visits this repo :) |
Interesting topic. I just read about SPDX: To my understanding, the license referred to in the package.json's license field is the one to adhere to. A complete text file does not seem to be required. That at least is my understanding... |
I see, then sorry for the trouble! I'm just used to finding packages and looking at the top of the repo for the license, but if that is the case then great. Thanks for the quick response btw :) |
I am not the project holder nor developer. I just added my thoughts, because the interests me, too! Please don't take my word for anything! I hope that the project owner still can add some clarifying information! |
I would be happy to add the LICENSE file if that provides additional clarity for folks. The package.json does not contain a license holder, but does cite @taylorbf as the author. IANAL, but although what you're allowed to do with the package ought to be pretty clear, the copyright holder(s) is less clear. I would nominate @taylorbf from 2019 onward, but don't know the whole history of the project. If the license were ever tested, I suspect that all contributors would implicitly hold the copyright for their own contribution. Along the same lines of clarifying this for folks, it would probably be good to enhance the CONTRIBUTING doc to specify that all contributors assign their copyright to the project. It's easy enough to do this and may have some benefits, because for the project to be adopted by some larger open source initiative, it makes life easier because it does not require seeking out permission from every single code contributor from the library's beginning. |
This great project does not have a license, which makes it illegal to use in other projects...
Would be great if you add a open source license :)
The text was updated successfully, but these errors were encountered: