Skip to content
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

Closed
pombredanne opened this issue Sep 26, 2018 · 4 comments
Closed

A modified Apache 2.0 license cannot be called apache anymore #27

pombredanne opened this issue Sep 26, 2018 · 4 comments

Comments

@pombredanne
Copy link

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

May I re-use (and modify) the Apache License 2.0 itself?¶

[...]

And if you adapt the agreement for your purposes, you have to make sure that the phrase 'Apache License', 'Apache', or any confusingly similar references or parts that specifically refer to the Apache organization do not appear in your version of the license (except to note that your version is derived and differs from the original provided by the ASF).

Your notice starts with

Licensed under the Apache License, Version 2.0 (the "Apache License") ...

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!

@glenfarclas17
Copy link
Contributor

Thanks for the feedback. I will forward this to our legal department.

@pombredanne
Copy link
Author

@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.

@pombredanne pombredanne changed the title A modified Apache 2.0 license cannot be calledd apache anymore A modified Apache 2.0 license cannot be called apache anymore Sep 27, 2018
@glenfarclas17
Copy link
Contributor

The gemspec file now lists license as 'NonStandard'. The title of the LICENSE.txt file 'Modified Apache 2.0 License' is accurate.

@tdunning
Copy link

tdunning commented Jan 9, 2021

THis is still a violation of the Apache trademark.

Please re-open and fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants