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

License? #38

Closed
Tracked by #42
comradekingu opened this issue Apr 5, 2022 · 14 comments · Fixed by #41
Closed
Tracked by #42

License? #38

comradekingu opened this issue Apr 5, 2022 · 14 comments · Fixed by #41

Comments

@comradekingu
Copy link
Contributor

There is no license here or on Weblate.
This seems to be in error(?)

@WofWca
Copy link
Owner

WofWca commented Apr 6, 2022

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.
I'm impressed and thankful that there are already people translating it, just after a couple of hours. I guess I'll hide the project on Weblate until it's set up properly to not waste anyone's resources.

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.

@WofWca
Copy link
Owner

WofWca commented Apr 6, 2022

I'm gonna do it in a couple of days.

@comradekingu
Copy link
Contributor Author

GPLv3-or-later?
AGPLv3+ is probably not compatible with distribution in the Chrome store.

@WofWca
Copy link
Owner

WofWca commented Apr 6, 2022

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.
I'm thinking of going for Unlicense or MIT or something like this for now, to maybe change it later.

@comradekingu
Copy link
Contributor Author

comradekingu commented Apr 6, 2022

If so, what is the problem there?
MIT has some permanent effects, so it isn't good for that. Unlicense is a crayon license that draws in public domain and all sorts of non-achieved ends, but actual problems.

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

@WofWca
Copy link
Owner

WofWca commented Apr 7, 2022

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.
What do you think would be a problem with Unlicense?

@WofWca
Copy link
Owner

WofWca commented Apr 8, 2022

I'm thinking of going for Unlicense or MIT or something like this

Also CC0 maybe

@comradekingu
Copy link
Contributor Author

@WofWca CC0 is the worst license there is.
For various different reasons why content doesn't and can't enter the public domain, when worked on in a collaborative fashion, it instead ensures a lot of headache.

@WofWca
Copy link
Owner

WofWca commented Apr 8, 2022

Ok, what would you suggest, besides GPL/AGPL?

@WofWca WofWca reopened this Apr 11, 2022
@WofWca
Copy link
Owner

WofWca commented Apr 11, 2022

I have added CC0 for now, but this doesn't mark the end of discussion, it can still be changed.

@comradekingu
Copy link
Contributor Author

I think we can agree BSD-2 does that.

@WofWca
Copy link
Owner

WofWca commented Apr 17, 2022

How about LGPLv3-or-later? Would you agree to it?

@comradekingu
Copy link
Contributor Author

Sure. It can be upgraded later on.

@WofWca
Copy link
Owner

WofWca commented Apr 18, 2022

046e929

@WofWca WofWca closed this as completed Apr 18, 2022
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