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

Expand guidance in README about licensing #37

Open
larsvilhuber opened this issue Dec 21, 2022 · 1 comment
Open

Expand guidance in README about licensing #37

larsvilhuber opened this issue Dec 21, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@larsvilhuber
Copy link
Contributor

> INSTRUCTIONS: Most data repositories provide for a default license, but do not impose a specific license. Authors should actively select a license. This should be provided in a LICENSE.txt file, separately from the README, possibly combined with the license for any code. Some data may be subject to inherited license requirements, i.e., the data provider may allow for redistribution only if the data is licensed under specific rules - authors should check with their data providers. For instance, a data use license might require that users - the current author, but also any subsequent users - cite the data provider. Licensing can be complex. Some non-legal guidance may be found [here](https://social-science-data-editors.github.io/guidance/Licensing_guidance.html). For multiple licenses within a data package, the `LICENSE.txt` file might contain the concatenation of all the licenses that apply (for instance, a custom license for one file, plus a CC-BY license for another file).

@larsvilhuber larsvilhuber self-assigned this Dec 21, 2022
@larsvilhuber
Copy link
Contributor Author

Also clarify that the LICENSE.txt needs to be created by the author, and adapted. Link to guidance.

The code is licensed under a MIT/BSD/GPL [choose one!] license. See [LICENSE.txt](LICENSE.txt) for details.

@larsvilhuber larsvilhuber added the enhancement New feature or request label Jun 6, 2024
@larsvilhuber larsvilhuber added this to the V1.2 milestone Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant