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

Update licensing on the website #27

Closed
aboullaite opened this issue Dec 17, 2020 · 5 comments
Closed

Update licensing on the website #27

aboullaite opened this issue Dec 17, 2020 · 5 comments
Labels
good first issue Good for newcomers

Comments

@aboullaite
Copy link
Contributor

We need to specify/separate the licensing for the code and for raw data.
On the github repo we mentioned MIT license, however on the website it still BY-NC-SA 2.0!
We should probably opt for ODC-ODbL for raw data

@aboullaite aboullaite added the good first issue Good for newcomers label Dec 17, 2020
@soub4i
Copy link
Contributor

soub4i commented Oct 14, 2021

Create a LICENSE file in root project and put the content of MIT Licence.
Please make sure to change:

  • <YEAR> by 2021
  • <COPYRIGHT HOLDER> by DevC Morocco

@aboullaite @yjose Please confirm COPYRIGHT HOLDER

@aboullaite
Copy link
Contributor Author

@MidouWebDev please yourself :)

@aboullaite
Copy link
Contributor Author

Yes! There are 2 licenses here. One for the website and one for the data.
MIT is the license for the website. You need probably to add another one ODC-ODbL for raw data under survey.
The license holder should be Geeksblabla I believe

@bilalix
Copy link
Contributor

bilalix commented Feb 26, 2023

What we can do is:

  • Keeping the MIT LICENSE file in the root level that outlines the terms of the chosen license for the repository as a whole.
  • Add another license file under ./results stating that the data is under ODC-ODbL license.
  • Additionally, in the README file, we can clarify that the code and data are separately licensed, and provide links to the individual licenses for each.

I think this approach covers both data and code sensibly.
I'll create a PR with the changes and we can take it from there.

@bilalix
Copy link
Contributor

bilalix commented Feb 27, 2023

@aboullaite, please feel free to close this issue.
Fixed in PR #97.

@yjose yjose closed this as completed Mar 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants