-
Notifications
You must be signed in to change notification settings - Fork 18
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
Correct license? #3
Comments
@notlee that is a great question. It feels like every colorblind-package is non-commercial because of some coefficients or calculations. How can that be? Were they patented or something? https://github.com/jkulesza/peacock has the same problem. |
Hello @heberleh ! Did you get an answer from HCIRN or one of the original author? Thanks for the reply ;) |
No, nothing new about this. I think there is no problem... But let us know if you find out. |
sorry for not seeing this until now. i think this project was setup with the incorrect license from the start. i had a script that was adding mit to my source files. it's very stupid to have both: Lines 16 to 22 in 20dd5e8
and: Line 12 in 20dd5e8
in the same file. it looks like i didn't know how to properly dual license or bubble up the license of the original source file i was using. based on https://opensource.stackexchange.com/a/7436 it seems like i need to convert this entire project to CC-BY-SA and i don't know how that affects people who have already been assuming it's MIT. any suggestions on how to fix this? |
I updated the license array in package.json and published v0.1.3: Here's what I changed today: |
I think that noone should assume that because a library X is writen with the licence Y means that it does not inherit from one of its dependency a licence more restrictive. We always do... I only saw it because I checked the source code. The licence Y should not have been set at first but everyone makes mistakes 😄 Thanks for updating the licence 😀 |
If the formula was patented, that patent is now expired, as patents last a max of 20 years and the copyright states the code was created in 2000. Copyright is a different thing. You can technically use their methodology since no patent could possibly be valid for it, but any code they wrote is copyrighted so you cannot copy/paste this "color_blind_sims" function verbatim without obeying their license. You could write your own version of the function that does the same thing, as stated, the technique cannot be patented. |
Hey thanks for
skratchdot/color-blind
, looks like a super useful package!I'd love to use it in the project I'm working on but have a question about the
license.
The comment for the Color Blindness Simulation function mentions
non-commercial use without HCIRN permission. As the MIT license allows
commercial uses I think it's incompatible?
Although I found on Matthew Wickline's site this update:
Source: http://colorlab.wickline.org/colorblind/colorlab/engine.js
CC4-BY-SA does allow commercial use, but requires anything which
builds on the project to be distributed with the same license, so I think
this project should also be CC4-BY-SA or a compatible license?
https://creativecommons.org/licenses/by-sa/4.0/
The text was updated successfully, but these errors were encountered: