Hello, the Fedora project migrates its translation platform to Weblate [1].

How does Weblate differ from Zanata from my pov? Any change in workflow?

This tool directly interact with your git repository, and requires us to know:

[mandatory] which branch is your development branch?

master is our development branch.

[mandatory] have you merged latest translation from Zanata and locked the project?

I am merging now, I hope. I completely forgot how Zanata works I am afraid, so I do not know how to lock the project.

[info] Weblate will handle updates when pot file changes, don't edit po files for this [2]
[optional] what is the license of translation? (please use a code from https://spdx.org/licenses/)

Where should this be?

[optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate)

Yes, I need to explain that some terms must not be translated but at most quoted as they are protocol specific terms.

[optional] do you need us to activate any specific checks? (this is a setting per component [3])

I do not know, guidance would be appreciated.

[optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page)

Why wouldn't I ?

Please note:

For github and gitlab hosted projects, Weblate open pull request. For other git hosting, you'll have to add a key to allow commits.

For pagure as well?
Why a key is needed? Can I just get a patch/PR and commit myself?

In Weblate's vocable, one project is a group of component. Each component is a translation file. You can have many projects or many components or both.

I have no idea what this means for me.

You can change your mind over time, just reach trans@lists.fedoraproject.org

By changing my mind, you mean changing something about the above answers?

[1] https://communityblog.fedoraproject.org/fedora-localization-platform-migrates-to-weblate/
[2] https://docs.weblate.org/en/latest/admin/continuous.html#avoiding-merge-conflicts
[3] https://docs.weblate.org/en/latest/user/checks.html#translation-checks

How does Weblate differ from Zanata from my pov? Any change in workflow?

Zanata had a push/pull mechanism handled by developers.
Weblate will interact with your repository by committing changes. This will looks like this: https://pagure.io/fedora-cheat-cubes/commits/master
I asked Weblate team to support Pull Requests for Pagure too: https://github.com/WeblateOrg/weblate/issues/3346 once done, it will looks like this: https://github.com/ibus/ibus-anthy/pull/16

I am merging now, I hope. I completely forgot how Zanata works I am afraid, so I do not know how to lock the project.

easy, open https://fedora.zanata.org/project/view/gss-ntlmssp
go to settings, and at the bottom of the page you can make the whole project read-only

[info] Weblate will handle updates when pot file changes, don't edit po files for this [2]
[optional] what is the license of translation? (please use a code from https://spdx.org/licenses/)

Where should this be?

I assume it is: LGPL-3.0-or-later

[optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate)

Yes, I need to explain that some terms must not be translated but at most quoted as they are protocol specific terms.

Please provide an example. I assume @rluzynski may help you to add comments in your code that will be automatically added in you pot and displayed in Weblate.

[optional] do you need us to activate any specific checks? (this is a setting per component [3])

I do not know, guidance would be appreciated.

If nothing bothered you in the past, then nothing more than the generic checks will be applied.
Checks is a whole world in itself, don't worry for now. Ask if something bothers you, and I'll tell you if a check may help.

[optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page)

Why wouldn't I ?

This only makes sense if you want us to translate a lot of files (like when translating websites or man pages). I think you don't have this workflow.

I asked Weblate team to support Pull Requests for Pagure too: https://github.com/WeblateOrg/weblate/issues/3346 once done, it will looks like this: https://github.com/ibus/ibus-anthy/pull/16

ok, a PR will work, I do not want to give out direct commit access.
I will wait to enable weblate until this support is available.

easy, open https://fedora.zanata.org/project/view/gss-ntlmssp
go to settings, and at the bottom of the page you can make the whole project read-only

Done.

[info] Weblate will handle updates when pot file changes, don't edit po files for this [2]
[optional] what is the license of translation? (please use a code from https://spdx.org/licenses/)
Where should this be?

I assume it is: LGPL-3.0-or-later

Well I know what the license needs to be, I do not know where you want the string placed though. Or where you just asking what the license is for your own use ?
LGPL-3.0-or-later is the correct license anyway.

Yes, I need to explain that some terms must not be translated but at most quoted as they are protocol specific terms.

Please provide an example. I assume @rluzynski may help you to add comments in your code that will be automatically added in you pot and displayed in Weblate.

If I recall correctly the French translators wanted to translate "Negotiate" which is the name of a flag and I did not agree that the term should be translated in all cases, but it was quite a while ago I might be wrong on what was the actual term that shouldn't have been translated.

fine, I'll let you know when upstream support is provided..

Thank you.

project migrated to github, please reopen there if still an issue