-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
License clarification #637
Comments
My gut feeling is that we mean Apache for any code in this repo and that CC license for the documents. I'll ask for clarification internally. |
Any update on this? |
If I remember correctly, I added the LICENSE file because I wanted to copy the pylint config file to https://github.com/dseomn/pepper-music-player/blob/main/third_party/google-styleguide/pylintrc following Google's guidelines for third_party imports. I don't think I knew about that line in README.md at the time. But it's also been a while and I'm not sure how accurate those memories are. |
The initial README added with commit 51ce2f4 committed on May 20, 2015 refers to CC-BY-3.0 Line 9 in 51ce2f4
whereas the Apache-2.0 license was added with commit f704c35 on Jan 3, 2020. So I assume that files initially added before commit f704c35 from Jan 3, 2020 is licensed unter CC-BY-3.0 as it seems there was no explicit re-licensing or dual-licensing action. However, IANAL! A short statement / clarification from Google's lawyers would be appreciated. |
We've always said the style guides are licensed under CC-By 3.0 in our README file. We use other licenses for code snippets, and list those in the respective file headers, but the guides are the dominant source in this repo, so list that in the LICENSE file. Fixes google#637.
The
LICENSE
file in the project says it's an Apache license, but in theREADME.md
, it says:This seems to conflict. What does the Apache license cover?
The text was updated successfully, but these errors were encountered: