-
Notifications
You must be signed in to change notification settings - Fork 144
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 basic wording for licensing and open the debate up to PRs. #173
Conversation
Could we determine the most used licenses on npm (by querying the license field in package.jsons in all packages), and report those statistics here? That would serve as a recommendation without making anyone worried that we were giving legal advice. |
I think that is an excellent idea. Let me see what data the NPM folks have on that. I have an owed favor. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add also the note of the "license" field in package.json. Wdyt? 😁
Do we recommend/discourage using a LICENSE file? |
Recommend, alongside the SPDX field. Both are required. |
Just an update. I have reached out to npm and got a response. I am continuing the conversation. |
( in order of popularity )
|
to clarify; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Issue 160 licensing
In order to get the ball rolling with some actual prose. This may serve as a starting point. I'm not making any recommendations either for or against individual licenses. Rather I'm saying that we
don't want
and do want
I think it is not likely we actually would come across a project we want to support that has no license.