-
Notifications
You must be signed in to change notification settings - Fork 260
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
Relicense translations under CC0 #1977
Comments
I agree. 👍 |
Don't care. |
I agree. |
I agree. 🇧🇬 |
I agree. |
Agree |
I also only speak Spanish and English, not French or Italian. However, using Google I may have translated for French or Italian at some point. If that matters. |
I agree. |
3 similar comments
I agree. |
I agree. |
I agree. |
I've now identified and reached out to everyone on either their GitHub or Discord account, mostly by @'ing them.
|
I agree. |
I agree |
When we were relicensing the
As such, I'd argue that we can tick their checkbox in this issue as well, especially since in their answer they provided the general statement
|
In the same issue as linked above @steamb23 also stated his approval:
It would be great to get your approval steamb23, though I'd argue once more, that their agreement on the previous occasion might be enough for this issue as well. |
I agree with that interpretation for both, I've ticked them too. |
I Hollow_666 / Yankshuru (a.k.a. WilliamFS on Discord), agree |
I agree |
yeah sure @pStyl3 is sigma i agree for everything |
No objections from me, go ahead! 👍 |
I am happy to (re)license my contributions to any translation under any version of the CC0! |
Zamix agreed via PM on Discord:
|
Kyo-- has agreed via PM on Discord:
|
When will release new localizations (Turkish) ? |
The Turkish translation will be included in the next release, which will probably happen later this week. |
Timeframe going forwardSimiliar to when we relicensed the masterlists to CC0, we have decided to once again set a deadline, until which past translators are able to state their opinion regarding relicensing their translations of the LOOT application to Creative Commons Zero (CC0), so if they agree or disagree with our proposed change. This deadline will be the 31st of December 2024. As before, even after that date past translators will continue to be able to state their opinion, however once the deadline has been reached, we will start the process to edit, change and/or remove the translations from everyone we haven't been able to get in contact with. How exactly we do this will then be decided on a translation by translation basis. It goes without saying that we would prefer to get the approval of the remaining past translators. @ThePotatoChronicler If you can find the time, please have a look at the above described issue. |
I agree, and I apologize for the delay ❤️ |
Thanks a lot! |
I agree, Sorry for the delay. |
@4lbi3 Thank you & no problem. Would you be able to get in contact with nicola89b regarding this? |
Hello. Suppose as in previous times need to write agree. I agree. |
The GPL isn't a great fit for non-code content, and like we did for the masterlists (see loot/loot.github.io#61) I think it would be a good idea to relicense the translations under the Creative Commons Zero 1.0 Universal license, effectively putting them into the public domain. This will also make future contributions more manageable if we get a wider pool of contributors through Weblate (see #1973).
I ran
git blame resources/l10n/<lang>/LC_MESSAGES/loot.po --porcelain | grep "^author " | sort -u
to get the current Git authors for each language translated. I've listed them below, with tickboxes to indicate agreement like we did for the masterlists. I also then went through the Git commits for each file to see who's been listed asLast-Translator
,Language-Team
or mentioned as a source in the commit messages.Sita http://forums.nexusmods.com/index.php?/user/259002-sita/- the only remaining line is theLanguage: fr
line, so no consent needed.[email protected]
, WilliamFS on Discord)<[email protected]>
, @Kyo-70?)@Freso- only changed two links from HTTP to HTTPS, consent not neededIf you've been mentioned above, please indicate your agreement or disagreement in a comment so that I can update the list. Also, sorry if you didn't want to be asked about this - one effect of this change will be that we shouldn't need to do it again.
The text was updated successfully, but these errors were encountered: