-
Notifications
You must be signed in to change notification settings - Fork 30
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
A modified Apache 2.0 license cannot be called apache anymore #27
Comments
Thanks for the feedback. I will forward this to our legal department. |
@glenfarclas17 great! FWIW, if you wonder why I discovered this issue in the first place: I maintain a decently popular tool to detect licenses at https://github.com/nexB/scancode-toolkit ... it was tripped to report a plain Apache 2.0 license (though with a lower score) in these scan results while scanning your code in this repo. (and based on what I can see, the same likely applies to the five other repos you have using this license) For reference, I recall dealing with a vaguely similar issue here palantir/blueprint#2602 that was eventually resolved here palantir/blueprint#2638 And do not hesitate to pass my contact info to your legal department if they need to discuss this. |
The gemspec file now lists license as 'NonStandard'. The title of the LICENSE.txt file 'Modified Apache 2.0 License' is accurate. |
THis is still a violation of the Apache trademark. Please re-open and fix this issue. |
Your use of a modified Apache license is IMHO misleading (it trips license detection tools for instance) ... and I am not sure your notice complies with the license modification conditions at http://www.apache.org/foundation/license-faq.html#mod-license
[...]
Your notice starts with
Could you avoid to call this Apache 2.0 in your notices because it is modified and no longer the standard Apache? This would promote clarity. (and as a side note your notice requires extra work for license detection tools like the one I maintain to make sure it is not mis-qualified as a standard Apache 2.0)
Thank you for you kind consideration!
The text was updated successfully, but these errors were encountered: