Skip to content
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

Add a LICENSE file please #68

Closed
coopr opened this issue Jun 23, 2018 · 3 comments
Closed

Add a LICENSE file please #68

coopr opened this issue Jun 23, 2018 · 3 comments

Comments

@coopr
Copy link

coopr commented Jun 23, 2018

and thanks!

@coopr
Copy link
Author

coopr commented Aug 14, 2018

Ideally, you'd do this https://help.github.com/articles/adding-a-license-to-a-repository/

In my case, I'm asking for this because the automated process we use depends on a response from Github's API https://developer.github.com/v3/licenses/#get-the-contents-of-a-repositorys-license regarding the license of each package we use - and, for this particular package, Github's API provides no response - because there is no detectable license in this repo.

@arnaud16571542
Copy link
Contributor

arnaud16571542 commented Mar 3, 2019

Hello,
I'm using license-checker (npm) to get and respect open source license for my commercial software. License-checker generate a json file read by my software. The json file containt all mandatory information to display (author, software name, copyright, mandatory licence).
license-checker use information from npm, and also, extract the licence information from a license file (like LICENSE, LICENSE.md)... For faye-websocket-node, extracted information is coming from README.md (the top part)..so, it is not good :).
So a dedicated LICENSE for this project is very welcome. Thank you.

@jcoglan
Copy link
Collaborator

jcoglan commented May 29, 2019

This is fixed by #72. For the record, the next release of this library and all other packages in the Faye project will be under the Apache 2.0 license, and the filename will be changed to LICENSE.md. I am standardising this across all our repos at the moment.

@jcoglan jcoglan closed this as completed May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants