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

Add license #5

Closed
Sohalt opened this issue Oct 6, 2020 · 6 comments
Closed

Add license #5

Sohalt opened this issue Oct 6, 2020 · 6 comments

Comments

@Sohalt
Copy link

Sohalt commented Oct 6, 2020

It would be nice to know under what license the published material may be reused (if at all).

@stefan-hoehn
Copy link
Contributor

hi @Sohalt As you can see here all devoxx4kids material should be licenced under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Hope that helps,
Stefan

PS: I'm curious what you intend to use it for, though? :-)

@Sohalt
Copy link
Author

Sohalt commented Oct 6, 2020

Thank you, that's helpful!
Can you maybe add a LICENSE file to the repository nonetheless? This will allow GitHub to show the license directly in their interface making it easier for people finding the project on GitHub.

PS: I'm curious what you intend to use it for, though? :-)

I'll be giving a workshop on teaching Sonic Pi and am looking for existing material to reference and share. Thanks for your work! It looks really solid.

@stefan-hoehn
Copy link
Contributor

I looked into it right away when you were pinging me. Unfortunately, there seems to be no easy way in this case. github usually allows you to add a LICENSE file and then choose the the right license but it doesn't support that one. So I looked for the license text that I could just copy paste (e.g. I found this here: https://github.com/matthewmccullough/Creative-Commons-4.0-Markdown/blob/master/licenses/by-nc-sa.markdown) but I am not sure if that would be the right approach as the official page would ask you to just link to the license: https://creativecommons.org/licenses/by-nc-sa/4.0/

So maybe the best way is to just mention it in the Readme or does it make send to just copy the link into the LICENSE.md ?

@Sohalt
Copy link
Author

Sohalt commented Oct 7, 2020

I think creating a LICENSE file would still be the best way. You can find the license text on the Github run choosealicense.com https://choosealicense.com/licenses/cc-by-sa-4.0/ and the creative commons organization are using it themselves on Github (and Github properly recognizes it): https://github.com/creativecommons/taaccct

@stefan-hoehn
Copy link
Contributor

Ok, great for researching and finding it! I have added the license file.

@Sohalt
Copy link
Author

Sohalt commented Oct 7, 2020

Thanks for handling this so quickly!

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