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

Can you please include a copy of the AGPLv3 with the code base? #8030

Open
willtop43 opened this issue Jan 25, 2024 · 2 comments · May be fixed by #8033
Open

Can you please include a copy of the AGPLv3 with the code base? #8030

willtop43 opened this issue Jan 25, 2024 · 2 comments · May be fixed by #8033

Comments

@willtop43
Copy link

willtop43 commented Jan 25, 2024

CKAN version

Describe the bug

A clear and concise description of what the bug is.

It is awesome you have chosen the AGPLv3 for CKAN. However, the AGPLv3 requires that a copy of the license be provided with the source (Section 4). The link in the README is not quite sufficient. I know this seems trivial, and I don't think CKAN (as author and copyright holder) is necessarily obligated* to include the license. However, anybody downstream who clones the CKAN repo and distributes it would be in violation of the license if they don't download a copy of the AGPLv3 and include it in the code base.

*I don't know if this is 100% correct because I am not a lawyer and this is definitely not legal advice.

Can you please include a copy of the AGPLv3 in the code base?

Thanks in advance.

~willtop43

@wardi
Copy link
Contributor

wardi commented Jan 30, 2024

This already exists as LICENSE.txt

@wardi wardi closed this as completed Jan 30, 2024
@willtop43
Copy link
Author

Thanks for replying. The LICENSE.txt does not have a full copy of the AGPLv3. Without it, anyone downstream distributors would violate the AGPLv3 unless they get a copy themselves and include it in the code base. Why not do them a favor and include a copy of AGPLv3 with ckan??

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

Successfully merging a pull request may close this issue.

2 participants