-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
Any chance of switching to an Apache or MIT license? #59
Comments
👍 Our company can't use GPL licensed software, and colorize is included in the Spinach gem, which we use heavily. If the colorize license can't be updated to something non-GPL/LGPL, we potentially have to remove spinach from our environment which we would very much like to avoid since we already have a significant amount of work done for spinach. |
#47 - already requested, never addressed. |
We're coming up on a year, and this is still an issue. It is becoming a blocker for us -- we will have to remove colorize from our product soon if this is not addressed. @fazibear Rails is often used for commercial projects. It comes with a more permissive license for that reason, and is why MIT, Apache, and the ruby license are the norm in the ruby ecosystem. Is it your goal to block commercial use? Can you provide some context and some of your reasoning? |
Experiencing the same issue. Any chance of making the switch or providing a commercial license option? |
There's another gem providing similar functionality that you can switch to: It's licensed under the MIT license and I've seen projects switching to it. |
One interpretation of GPL 2.0 has made it so that I am discouraged from using this gem. The Apache and MIT licenses encourage using libraries with less copy-left implications. Any chance of shifting?
The text was updated successfully, but these errors were encountered: