-
Notifications
You must be signed in to change notification settings - Fork 123
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
Consider using CC0 for this project #37
Comments
Public Domain licenses are great, and CC0 might be the best one I know of. Still, OSI's Review Committee's reason for not approving CC0 (yet) may be worth looking into and addressing:
(lloydde from Hacker News posted such a quote there. I was just following the link and copying quotes.) |
We have looked at and considered CC0. See FAQ. We are not proposing that CC0 is incorrect or trying to set a policy. We are exploring a different approach. It may work, it may not. Rather than specifying the license that DoD project should use, we wanted to create a framework where the individual project owner could choose the appropriate license for themselves. The suggestion to move contribution details into CONTRIBUTIONS.md is valid and we will get to that shortly. There is also an alternate suggestion at #33,#34 that may be closer to what you are suggesting. Closing as addressed in FAQ. |
The goal of this license as it stands is:
There is already an existing license that achieves this, has been thoroughly reviewed, and enjoys widespread adoption. Namely, the CC0 license.
Additionally, the CC0 makes many disclaimers about the published material so as to limit liabilities that the publisher assumes by making publication. Specifically, this addresses issue #36.
Note: CC0 does NOT satisfy the current requirement of DOSA 1.0draft in using a Developer’s Certificate of Origin. No problem. Instead, this requirement should be discussed in CONTRIBUTORS.md.
The text was updated successfully, but these errors were encountered: