-
Notifications
You must be signed in to change notification settings - Fork 205
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
incorrect docs license grant #50
Comments
Thanks @onlyjob. @thaJeztah @moxiegirl I'm sorry for the ping. Even though the indications are pretty clear, do you have any pointer or advice on how to get this right? Can't seem to find a guideline to follow on another repository (under |
@abronan I'm sorry, but I'm really bad at this licensing stuff, so I'm not really sure I can help out here. Maybe @moxiegirl know examples in the other repos. Also, I see @onlyjob is quite active in reporting similar issues (which I think is great); @onlyjob do you have some pointers/examples to help out? |
Thank you. in order to pass copyright compliance review I file those bugs for software I package for Debian... Basically there are only few things to do:
The only thing that looks like documentation in libkv repository is
Here is the sample text I drafted:
|
Just realized I still need to choose the license for the documentation, I'll see what is common on other projects under |
Thanks so much, @onlyjob! I think that's making things a lot clearer. @abronan think you can work with that? I think option 1 is sufficient for now, we can always add option 2 if needed, wdyt? @moxiegirl should we check the other repos as well? |
@thaJeztah @abronan Let me check with Legal on this. I'm sure we have someone to advise. @onlyjob thanks for pointing this out. |
@moxiegirl Any news on that to make sure this is not a blocker for anybody packaging |
@abronan Last week, I sent an email and got a reply that a Lawyer would be in touch. I'll kick that tire again today and come back at you. |
Once we have that response, perhaps we should capture some guidelines / examples in a document, as I think there are plans to move some packages to separate repos |
thanks for the update @moxiegirl! @thaJeztah yes good idea! |
Unfortunately there is a problem, see #59 (comment) |
@onlyjob Sorry should have waited for your feedback first. We'll look into that and fix asap, thanks! |
Thanks, @abronan. |
Creative commons instruct to use the following attribution text:
Adding "to end users" to attribution text is harmful because text of the license is not using such term. As result due to absence of "end users" definition nobody can use documentation... This is silly and perhaps the opposite of what was intended... :( |
Similar to moby/spdystream#57
is an incorrect grant of license.
Please clearly specify scope of the license (which files), license name (e.g. "CC-BY-SA-4.0") and URL of the license. Also please commit complete text of the license.
Thanks.
The text was updated successfully, but these errors were encountered: