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

CC0 license #23

Open
matiasdahl opened this issue Jul 20, 2018 · 2 comments
Open

CC0 license #23

matiasdahl opened this issue Jul 20, 2018 · 2 comments

Comments

@matiasdahl
Copy link

I am currently working on a backend component (still WIP) based on this template that I would like to release under the MIT license. However, I have had trouble finding information whether this is possible. In other words: can I release a project under the MIT license even if it is a derived work from a template released under the CC0?

I tried to find some information related to this, but did not find anything conclusive. Below are some comments/links I found.

  • It seems CC0 is not approved by the OSI. They also recommend At this time, we do not recommend releasing software using the the CC0 public domain dedication.
  • I probably do not understand all the issues related to this correctly (and IANAL). However, the MIT license specifically grant the right to sublicense the code. However, part 3 (Public License Fallback) in the CC0 text mentions that the fallback license is "non sublicensable". However, according to gnu.org, the CC0 (and the Public License Fallback) are compatible with the GNU GPL. Related discussion.
@matiasdahl
Copy link
Author

Sorry, I filed this issue for the wrong template.

The template I used was akka-http-quickstart-scala, but both of these templates are released under the CC0.

@johanandren
Copy link
Member

This seems to have fallen between the cracks, I'm not sure about the legalese around the licenses, but for the record all intentions with the templates (and their licensing as CC0/public domain) is to allow anyone use the templates as a starting point for their Akka and Akka HTTP based apps in whatever way they want, regardless if those apps are OSS or proprietary.

Anything useful will likely anyway quickly diverge from the getting started app so much that the origins does not really matter.

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