|
# Notes for "[Moving translations to Weblate](202209MeetingMovingToWeblate)"
|
|
# Notes for "[Moving translations to Weblate](202209MeetingMovingToWeblate)"
|
|
|
|
|
|
* Facilitator: emmapeel
|
|
|
|
* Who: tpa, applications, web
|
|
|
|
* Duration: 1h
|
|
* Duration: 1h
|
|
* Description: We will build together the plan for moving to weblate, what is needed, how our translation service is going to change
|
|
* Description: We will build together the plan for moving to weblate, what is needed, how our translation service is going to change
|
|
* Priority: medium
|
|
* Priority: medium
|
|
|
|
|
|
|
|
# Moving Tor Project translations to Weblate
|
|
|
|
|
|
|
|
## Why are we moving to weblate
|
|
|
|
|
|
|
|
Volunteers have been complaining about Transifex being proprietary
|
|
|
|
|
|
|
|
Fluent is not supported at all in Transifex, while there is preliminary support in Weblate
|
|
|
|
|
|
|
|
We need to support Fluent translations because of Tor Browser (desktop?)
|
|
|
|
|
|
|
|
We can choose to self-host Weblate if we want, eventually (moving translation memory and configuration should be feasible)
|
|
|
|
|
|
|
|
Weblate has offered to host us, we have 10k maximum strings, currently we need 8-9k
|
|
|
|
|
|
|
|
### Hosting
|
|
|
|
|
|
|
|
There is already a Tor Project namespace on Weblate, managed by emmapeel:
|
|
|
|
https://hosted.weblate.org/projects/tor/
|
|
|
|
|
|
|
|
The development pace of Weblate is currently very fast and several dependencies are not packaged yet in Debian. Tails has been self-hosting and finding it difficult to keep up with updates, so this is why emmapeel is in favor of using the hosted version. In addition, from experience the hosted version is almost always up to date with the latest release.
|
|
|
|
|
|
|
|
## Repository changes
|
|
|
|
|
|
|
|
- mirror repos in gitlab
|
|
|
|
|
|
|
|
- stop the 'one branch per project' thing? is it useful?
|
|
|
|
|
|
|
|
- difficult to use the tor browser repo, because the branches are not fixed and need to be changed.
|
|
|
|
|
|
|
|
|
|
|
|
Tor Browser team would like to move to using two branches for translations: base-browser and tor-browser
|
|
|
|
|
|
|
|
base-browser: only security level and new identity
|
|
|
|
|
|
|
|
tor-browser: all the rest we already have
|
|
|
|
|
|
|
|
these repositories are automatically cloned when we build Tor Browser in tor-browser-build (we could even always get the latest translations for nightly builds but we need to "freeze" a commit hash when releasing an alpha/release for reproducibility - but it takes a few second and we can just add it to the release preparation, we already have a translation update step)
|
|
|
|
|
|
|
|
emmapeel wants to be able to review the strings before they are made available to translators on Weblate, having a separate repository (like currently) would permit this -- PieroV confirms this would not affect their workflow in a negative way
|
|
|
|
|
|
|
|
The reason we want this is because often when features are added, very often the strings are not yet mature, and we absolutely agree that we want to avoid wasting translator's time in translating "beta" strings
|
|
|
|
|
|
|
|
Gitlab provides easy access for emmapeel to create repositories, so we dont need to be limited to one repo like now
|
|
|
|
|
|
|
|
|
|
|
|
## Fluent
|
|
|
|
|
|
|
|
support in weblate is not so mature yet, we should communicate our needs and help weblate to give better support
|
|
|
|
|
|
|
|
Security level and new identity should be easy enough to move to Fluent and use more features than branding (e.g., attributes, aliases)
|
|
|
|
|
|
|
|
Henry said that Mozilla suggested not to use aliases, though, because they do not work in all languages
|
|
|
|
|
|
|
|
|
|
|
|
## Timeline
|
|
|
|
|
|
|
|
emmapeel is already starting to move things to Weblate and people are already starting to translate there, but the reviewer teams are not yet set up so that would be the next step
|
|
|
|
|
|
|
|
Tor Browser 12.0 is scheduled for mid November (IIRC), and we (apps team) would really love to move everything to Fluent for that version.
|
|
|
|
|
|
|
|
## Needs from TPA
|
|
|
|
|
|
|
|
ability for emmapeel to create new translation projects on our Gitlab
|
|
|
|
|
|
|
|
assitance for setting up CI in the new projects
|
|
|
|
|
|
|
|
|
|
|
|
## Next steps
|
|
|
|
|
|
|
|
let's sync using tickets for the various things needed to make this happen
|
|
|
|
|
|
|
|
we should also sync via IRC
|
|
|
|
|
|
|
|
emmapeel and ggus will make an announcement of tor-project that we are starting to move to weblate
|
|
|
|
|
|
|
|
emmapeel will start working on building the language reviewer teams on Weblate
|
|
|
|
|
|
|
|
once we complete the move from Transifex, we should make a blog post
|
|
|
|
|
|
|
|
speak about weblate on l10n hangouts
|
|
|
|
|
|
|
|
what licensing for the translations? Tor is BSD 3, TBB is more MPL (probably same as Firefox?). We can default to the upstream license for each project, and check that MPL 2.0 is good for Tor Browser.
|
|
|
|
|
|
|
|
|
|
|
|
- Community management
|
|
|
|
|
|
|
|
- Reviewers
|
|
|
|
|
|
|
|
- QA checks
|
|
|
|
- Further communications |
|
|
|
\ No newline at end of file |