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

[Sleeping] Remove license files from the repository #9

Open
santisoler opened this issue Jul 13, 2020 · 6 comments
Open

[Sleeping] Remove license files from the repository #9

santisoler opened this issue Jul 13, 2020 · 6 comments

Comments

@santisoler
Copy link
Owner

Creative Commons make available all license texts on their GitHub repository: https://github.com/creativecommons/creativecommons.org

All translations are available in HTML files, while the English version of the license text is also available in plan text.
We should consider not hosting our own license texts and pointing to their files instead.
Until creativecommons/cc-legal-tools-app#8 is fixed, we could start removing only the English version while keeping the translations.

@santisoler santisoler added the help wanted Extra attention is needed label Jul 13, 2020
@cyb3rko
Copy link
Contributor

cyb3rko commented Jul 13, 2020

So if I understood right you want to remove those license texts from your repository which are officially published by CC?

@cyb3rko
Copy link
Contributor

cyb3rko commented Jul 13, 2020

And the correct repository I think is https://github.com/creativecommons/cc-licenses.

@santisoler
Copy link
Owner Author

So if I understood right you want to remove those license texts from your repository which are officially published by CC?

Yes! It's better to link to the original files that hosting our own. I haven't though about it before because I didn't know CC hosts the license text in plain text until last week. I obtained the license file from https://choosealicense.com/licenses/cc-by-4.0/ , but it's better to point people to the source.

And the correct repository I think is https://github.com/creativecommons/cc-licenses.

No, that repository is where the issue I open has been moved to. But the license texts live inside https://github.com/creativecommons/creativecommons.org , under docroot/legalcode.

@cyb3rko
Copy link
Contributor

cyb3rko commented Jul 13, 2020

Yes! It's better to link to the original files that hosting our own. I haven't though about it before because I didn't know CC hosts the license text in plain text until last week. I obtained the license file from https://choosealicense.com/licenses/cc-by-4.0/ , but it's better to point people to the source.

Ok, I totally agree, this solution just makes sense 😉.

No, that repository is where the issue I open has been moved to. But the license texts live inside https://github.com/creativecommons/creativecommons.org , under docroot/legalcode.

You're right...

@santisoler santisoler removed the help wanted Extra attention is needed label Apr 27, 2021
@santisoler santisoler changed the title Remove license files from the repository [Sleeping] Remove license files from the repository Apr 27, 2021
@deobald
Copy link

deobald commented Apr 6, 2023

Given that the only files in docroot/legalcode are HTML, it seems unlikely GitHub will properly recognize them (though maybe that's changed since I last tried). If that is still the case, I doubt I'm the only person who greatly appreciates this repo of plaintext CC licenses that GitHub does recognize. :) It would be a shame to lose it.

@santisoler
Copy link
Owner Author

Hi @deobald! Thanks for showing our appreciation for this repo. I agree that Creative Commons is not currently offering a proper alternative to the things we have in this repo, so I don't have any plans of shutting it down in the near future.

I opened this Issue to state the idea that having Creative Commons offering plain text versions of their licenses sounds much better than having them in a non-offiicial repository in GitHub: proper maintenance, better support for translations, more discoverability, official support, etc.

But until CC don't make this repo obsolete, I'll keep it alive and running. BTW, if that eventually happens, I'll probably keep this repo alive, put a note pointing people to the official versions and archive it (no new commits, issues or PRs).

So, you can all relax about the future of this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants