explicit dataset licenses #7
Merged
Conversation
This file contains 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
|
@davidlmobley @mrshirts we need to be explicit about licensing. If you review and agree to this PR then I will take this as consensus on how to move forward. This will also allow me to review PR #6 by asking for an explicit license there. |
|
blocks #6 |
davidlmobley
approved these changes
Oct 31, 2017
|
Yes, this is fine. I'll make sure mine are CC0 or CC-BY. |
|
Thanks! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Make explicit that datasets are distributed under an open license (a recommended license conforming to the Open Definition 2.1
The GMX dataset was explicitly put under the CC0 (public domain) by adding a License field to the description.
The wiki page on Contributing: Licenses was also updated.