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

please fix docs license #57

Closed
onlyjob opened this issue Sep 6, 2015 · 7 comments · Fixed by #58
Closed

please fix docs license #57

onlyjob opened this issue Sep 6, 2015 · 7 comments · Fixed by #58

Comments

@onlyjob
Copy link

onlyjob commented Sep 6, 2015

Docs released under Creative commons.

Is an improper grant of license. A license version should be mentioned in the proper format like "CC-BY-SA-4.0" with a link to the full text of the license ideally accompanied by full text of the license committed to repository.

Also it would be nice to mention scope of the license (i.e. which docs?).

Thanks.

@onlyjob
Copy link
Author

onlyjob commented Sep 7, 2015

Also this could be interpreted that README.md is under CC (any version?) while the rest of the spdystream is unser Apache-2.0... Please clarify.

@onlyjob
Copy link
Author

onlyjob commented Oct 31, 2015

Any progress please?

dmcgowan added a commit to dmcgowan/spdystream that referenced this issue Nov 2, 2015
fixes moby#57

Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
@onlyjob
Copy link
Author

onlyjob commented Nov 2, 2015

Thanks! :)

@onlyjob
Copy link
Author

onlyjob commented Nov 3, 2015

Sorry for being pedantic but attribution is still a little bit ambiguous. It says "Code and documentation copyright..." and then it mention license only specifically to code: "Code released under the Apache 2.0 license.".

Perhaps it would be best to drop "Code" and "Code and documentation" so it reads at least

Copyright 2013-2014 Docker, inc.
Released under the Apache 2.0 license.

Please note that the text of the Apache-2.0 license itself (in the very end) recommends to use very specific text of license grant. If possible please consider applying Apache-2.0 license as per instructions in the license. Cheers.

@dmcgowan
Copy link
Member

dmcgowan commented Nov 3, 2015

Not quite sure I understand the ambiguity. The statement is saying the code is covered by the Apache license and code and documentation (which currently there is none besides code documentation) are copyright. I am not an expert on any of these things and only following the language from other Docker repositories. If you notice inconsistencies between this project and others then I will gladly rectify. However if you find an issue with how we handle licensing in general, then it is probably something I would need to escalate. Normally I would just point to the https://github.com/docker/spdystream/blob/master/LICENSE from the Readme. If you find something lacking in the License that is a different story, if it is just the Readme then I will glady remove the existing language and just put "See LICENSE file".

@onlyjob
Copy link
Author

onlyjob commented Nov 4, 2015

Copyrighted materials without explicit license are non-free (i.e. "All Rights Reserved").
Technically speaking, current license grant makes non-code non-free (e.g. non distributable, not modifiable etc.). Please do not justify incorrect wording of license grant by proliferation of bad practice in the other repositories. FYI there were another bad case of license grant in docker/libkv#50 as well as docker-archive/classicswarm#1280 so Docker repositories do not shine in that regards. IMHO it would be best to apply license properly, as the text of the license instruct, without unnecessary improvisations.
Thanks.

@dmcgowan
Copy link
Member

dmcgowan commented Nov 6, 2015

Apparently this issue was already escalated and resolved in libkv. I followed what was used there which was vetted by individuals more knowledgeable than I am about licenses. Thank you for your concern. If you see any further inconsistencies feel free to open up a new 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

Successfully merging a pull request may close this issue.

2 participants