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
Migrate translations to Weblate #17907
Comments
Do you know if there is an easy way to do this? (So that editing is disabled for everyone) Or do we need to do an announcement, wait as long as possible and then just ignore everything afterwards? |
It's possible to disable that for each resource on Transifex in the settings |
Regarding enabled features we can take a look at https://docs.weblate.org/en/latest/workflows.html: I think there would be two possibilities: same as before (review)
This way, people can translate and (possibly a separate group of users?) can review those strings. Nevertheless both reviewed and unreviewed strings would be used in Matomo. Migrating existing review status is not impossible using both APIs, but seems like a lot of work. VotingI have seen this method work in quite a few FOSS projects before:
This means that again anyone with an account can edit the translation (and if there wasn't one before, it is used immediately), but if two people disagree on which translation to use, both can be created as suggestions and everyone can vote on the better translation. Other settings:Project wide:Access:I would stay with "Public" (except for the premium-plugins): This allows anyone (without an account) to see the translation strings and suggest changes. Anyone with an account on hosted.weblate.org can edit translations. Workflow:
Per Component settings:Basic/Translation
|
GlossaryI think the glossary is quite important to keep things consistent. Thankfully the glossary in Weblate seems to be quite user friendly and especially is its own component so that all features work on glossary strings. The existing entries in all languages can be exported as a CSV from here: One could write a simple program to convert those, but I can't find a way to upload translation files in transifex. Maybe this is something we could ask the support. |
Sounds fine. Maybe there is a possibility to trigger this through API? If so we could use a simple GitHub action to trigger it |
I think a |
Feel free to enable the push on commit then. Regarding the translation workflow: I'm tempted to go with the voting model as you suggested |
We used to use Transifex for our translation management, but decided to move on to Weblate in the future.
This issue is about to gather and keep track on the tasks we need to do in order to finish the Migration
Setup a project on Weblate --> https://hosted.weblate.org/projects/matomo/
Look through & improve available configurations, filters & validations on Weblate and document the final settings in Confluence
Setup all resources on Weblate
Matomo open source plugins
Third Party Plugins
LiveTab https://github.com/tsteur/piwik-livetab-pluginPremium Plugins
Create a Webhook on GitHub to automatically push changes to Weblate in all repos
Post an Update on Transifex that we are going to move to Weblate
Make sure Matomo supports empty translation files (so containing only
{}
)--> comment by @sgiehl: checked out the weblate PR including many "empty" translation files and Matomo still worked correctly
Update
\Piwik\Plugins\LanguagesManager\API::getAvailableLanguages
to only use languages that are considered "complete enough". use list of supported languages from config #17930Freeze all resources on Transifex so no new translations can be added on 29th of August
Sync all translations to github and maybe download all locally (to ensure nothing gets lost)
Create missing languages on Weblate and upload the files from Transifex
Remove the translation update github actions, as Weblate will create PRs automatically
Remove all translation related commands or change them to use Weblate instead of Transifex
Update developer documentation at https://developer.matomo.org/guides/translations#getting-translations-for-your-plugin Document translations on Weblate developer-documentation#523
Create a blog post about the changes in translation workflow and publish it on social media
Look into WP-Matomo translations (either export all of them and create a PR to merge them or move them to Weblate too)
Close down Transifex project before 20th September
Update internal confluence with new process
Update target of https://translations.matomo.org/ redirect
Update https://matomo.org/translations to directly link to Weblate, instead of requiring to send an email
Update README and mention the usage of Weblate (Required by Weblate) Prepares Weblate migration #17927
The text was updated successfully, but these errors were encountered: