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

Licensing #32

Closed
agh opened this issue Mar 16, 2015 · 3 comments
Closed

Licensing #32

agh opened this issue Mar 16, 2015 · 3 comments

Comments

@agh
Copy link

agh commented Mar 16, 2015

https://github.com/aws/amazon-ecs-agent/blob/master/agent/agent.go#L1-L3

It seems a little unusual to see 'All Rights Reserved' as well as the Apache 2.0 boilerplate in the header of all the files which were released. I'm curious what effect it has upon consumers of the code, and anything contributed back to the project via Pull Request or similar.

This ambiguity has come up with other projects recently, see -

GoogleWebComponents/google-sheets#12

IANAL. Any clarification which you can supply would be much appreciated!

@hyandell
Copy link
Contributor

Hi Alex,

Looking at the GoogleWebComponents issue, I believe that's for the situation in which an Apache 2.0 licensed project contains files that only say "All rights reserved. ". I've double checked ecs-agent, and I can't see any files that fit that pattern.

If you do find any files that say All rights reserved, but don't have an Apache 2.0 license header, please let us know as we may not have intended to publish that file on GitHub.

Thanks,

Hen

@agh
Copy link
Author

agh commented Mar 19, 2015

Hi Hen,

That wasn't quite my point; you are correct that the HTML files just say "All Rights Reserved".

What my question was - in the case of files where both statements are made what is the legal impact? To my "I am not a lawyer" eye, it seems like stating that 'All Rights Reserved' conflicts with the later statement it is Apache 2.0 licensed because by applying that license, you are giving people rights to deal in and modify/use the software.

It seems really rare to see both statements, in the same project or file, hence my confusion and curiosity.

Sorry if this question was unclear when originally submitted. Please let me know if it remains unclear.

Thanks,
-Alex

@hyandell
Copy link
Contributor

Obviously, as I'm not a lawyer, and additionally not your lawyer, I can't give you legal advice about "What's the legal impact" for your project or use case.

But, I can clarify a few items:

  • Is it common to put All Rights Reserved, before subsequently granting rights?
    ** Searching GitHub: For large corporations it appears to be common.
  • Does it mean the software isn't under Apache License 2.0?
    ** We fully intend that the terms of the Apache License 2.0 apply to this software.

Apologies that I can’t provide legal advice, but hopefully this helps :)

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

2 participants