-
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
Add a LICENSE #123
Comments
This issue probably needs a vote, as it covers content written by many authors. |
I'd vote for a CC license, but I'm not an author. Should we invite every post author to this issue? |
Yeah, we should do that actually, so we can put our hand over our heart and say it's "this license", and advertise it in the blog footer, README.md, etc. |
Long overdue(!) but I've seen this discussion on some Guile mailing list. CC BY-SA seems like a good fit, since it's compatible with GPLv3 and Wikipedia at the same time. It also got updated to be one-way compatible to GPLv3. It's only drawback(?) is that it's not FDL compatible. Perhaps a freer CC0 license would suffice if people don't like the CC BY-SA? |
So we have no license in this repository. The repository contents are purely authored but LUG people, so we can choose one ourselves.
Since it's not really code we should probably use some form of Creative Commons, no? Perhaps Creative Commons 4.0 BY-SA? That requires attribution and sharing under the same terms, and allows for commercial use (as long as the result is attributed to us and shared under CC-BY-SA as well. This is similar to the GPL for code, which is not against commercial use).
We would also need an item in
README.md
listing the license terms.The text was updated successfully, but these errors were encountered: