Relicense project as CC0 #371
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 👍 👍 |
Member
|
Thanks for the suggestion, @konklone and @leahbannon ! I'll definitely take this back to the team, and we'll discuss. 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I understand that this requires discussion and review, but I thought I'd kick it off with a pull request.
This relicenses the project to be dedicated to the international public domain -- or as close to that ideal as people have figured out how to do, at least. This is a hybrid license -- it uses the CC0 public domain dedication to waive copyright internationally, while acknowledging that the work is already in the public domain inside the US.
This is an approach advocated by a wide swath of civil society, and is the default LICENSE file of 18F (a technology team housed inside the General Services Administration), as laid out by 18F's open source policy.
The public domain is great, and the best place for taxpayer-funded work. I'm not totally sure of how direct the relationship is between this project and the Department of Defense, but since the current license says "(c) 2012 Department of Defense", it seems that from at least a licensing perspective, the work is a government product.