Closed Jayman2000 closed 2 years ago
I would update the notice to be:
For the purposes of this DCO, Creative Commons interprets "open source license" to be equivalent to "open content license" or "public domain declaration" for use with open content.
I'll also loop in Legal
Additional context: Using CC0 for public domain software - Creative Commons
Description
The Developer Certificate of Origin requires pull requests to be submitted under an “open source license”. At least one of Creative Commons’s repos is available under CC0. CC0 is a public domain dedication, not a license. Even if it was, it's not clear whether or not it would be an open source one since CC0 tries to waive copyright. See:
Reproduction
cc-licenses-data
repo.Expectation
I would expect that part (a), (b) or (c) would have me certify that my contribution is dedicated to the public domain using CC0 because that repo is dedicated to the public domain under CC0. I would also expect part (d) to have me certify “that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or ” CC0.
Additional context
I originally submitted a fix for this problem in creativecommons/cc-licenses-data#47, but I was told that it would be better to have the issue fixed here. The DCO itself doesn’t allow modifications, so my proposed solution was to add the following sentence above the DCO:
Resolution