-
Notifications
You must be signed in to change notification settings - Fork 35
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
Explicit license for the templates #20
Comments
Typically I use CC-BY or CC-BY-SA. I think that might be better for the templates; the spec is under a specification license which I'm not sure would apply to vector artwork templates? IANAL though. Whatever is easiest for you. |
The content of the specification is CC0 + Open Web Foundation Agreement Version 1.0. I'm unsure of what to do with supporting resources. I'm asking my friends working on real specifications what they would do. |
After chatting with someone else, what is generally preferred for resources is CC0. @mairin I don't know how you feel about releasing your resources under that, but welcome your feedback. |
CC0 is totally cool with me. :-) On June 23, 2016 3:47:48 PM EDT, Terin Stock [email protected] wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Cool, I'll make a thread to track who's signed their resources as CC0, then
|
Could you please add an explicit license to the templates in assets/ ?
This would make it easier to use them in the context of some free software / culture projects.
From issue #8 I understand that the author is @mairin , whose permission is probably required.
My personal opinion is that keeping them under the same terms of the specs is probably the most practical choice.
The text was updated successfully, but these errors were encountered: