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

tandoor-recipes: missing commons-clause licensing terms #371050

Closed
mweinelt opened this issue Jan 5, 2025 · 1 comment
Closed

tandoor-recipes: missing commons-clause licensing terms #371050

mweinelt opened this issue Jan 5, 2025 · 1 comment
Labels
0.kind: bug Something is broken 1.severity: legal This PR or issue raises or fixes a legal issue, e.g. licensing compliance

Comments

@mweinelt
Copy link
Member

mweinelt commented Jan 5, 2025

The license for tandoor-recipes fails to include the commons-clause license, which would make it unfree.

Beginning with version 0.10.0 the code in this repository is licensed under the GNU AGPL v3 license with a common clause selling exception. See LICENSE.md for details.

https://github.com/TandoorRecipes/recipes#license

Additional context

https://commonsclause.com/

Notify maintainers

@jvanbruegge


Note for maintainers: Please tag this issue in your PR.


Add a 👍 reaction to issues you find important.

@mweinelt mweinelt added 0.kind: bug Something is broken 1.severity: legal This PR or issue raises or fixes a legal issue, e.g. licensing compliance labels Jan 5, 2025
@niklaskorz
Copy link
Contributor

Quoting @ssddanbrown from TandoorRecipes/recipes#238 (comment):

When combined with the AGPLv3, the commons clause is essentially redundant because users can just remove all meaningful requirements/restrictions/limitations it adds as per section 7 of the AGPL (Emphasis mine):

All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.

@mweinelt mweinelt closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken 1.severity: legal This PR or issue raises or fixes a legal issue, e.g. licensing compliance
Projects
None yet
Development

No branches or pull requests

2 participants