-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
License? #38
Comments
You're right, there's no license yet. I'm thinking of adding one specifically for translations for now. It's gonna be a libre one. By the way, let me know, if you do have a suggestion on what license to choose and how it's best to make it so that it applies to translations only. |
I'm gonna do it in a couple of days. |
GPLv3-or-later? |
I thought about GPL. It would automatically force me to apply it to the whole extension as well, as far as I understand. And I have not yet decided if it's the way it should be. |
If so, what is the problem there? This interpretation sold me on AGPLv3+ https://opensource.google/documentation/reference/using/agpl-policy Edit: Also https://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement |
Perhaps I'm misunderstanding you? I'm saying that I have not yet decided how I want to license the extension's (not the translations') code, so I'm keeping it "all rights reserved" for now. Using GPL-licensed code (including translations) prohibits this. |
Also CC0 maybe |
@WofWca CC0 is the worst license there is. |
Ok, what would you suggest, besides GPL/AGPL? |
I have added CC0 for now, but this doesn't mark the end of discussion, it can still be changed. |
I think we can agree BSD-2 does that. |
How about LGPLv3-or-later? Would you agree to it? |
Sure. It can be upgraded later on. |
There is no license here or on Weblate.
This seems to be in error(?)
The text was updated successfully, but these errors were encountered: