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
[package.json] Custom License #67
Comments
An Apache-2.0 default license would allow a few more people to use VizHub examples at work. as I understand it, MIT is silent on patent grants, while Apache-2.0 explicitly grants a patent license to users. If you the author have no patents, then Apache-2.0 is a way of signaling to paranoid users that you don't plan to use secret patents to sue them later. |
outside of the "people who work at companies with lawyers" cohort, MIT is friendly and fine. it is also much more concise than Apache-2.0. |
@micahstubbs Thanks for the insight! Maybe the default should be changed, as the desire is to make it as permissive as possible. |
yea, my experience with similiar goals led me to In my case, the goal was "find the most permissive widely-used OSI approved license and use that" where OSI-approval is a proxy for being a well-defined license. https://opensource.org/licenses |
Ideas for how to do this:
|
This is becoming important as people are starting to port things from Observable (ISC Licensed) to VizHub (MIT Licensed). |
New idea for how to approach this: use the https://docs.npmjs.com/cli/v6/configuring-npm/package-json#license VizHub can read that and display the license where it currently says "MIT License". The lookup table from License code to full form is here https://www.npmjs.com/package/spdx-expression-parse |
If we use the It seems that the best approach to this would be to add an additional section of the settings panel with a dropdown for licenses. Let's add a menu there with the following set of options: MIT, ISC. |
@curran do you have a case for old vizz which requires a license change? |
Good call out. It's true there is no strong use case for changing the license on existing vizzes. |
Maybe a simple implementation based on |
The license field in Some nice documentation about it: https://docs.npmjs.com/cli/v6/configuring-npm/package-json#license |
@stushurik Please move ahead with the following scope of work for this issue:
Thanks! |
As a visualization author, I want to specify which license the code is released under, so that I may change it from the default MIT License.
The text was updated successfully, but these errors were encountered: