Bug #15357

Clarify how the review process of Weblate influences git commit

Added by Anonymous 2018-03-02 10:29:39 . Updated 2019-06-27 17:16:41 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.11
Start date:
2018-03-02
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:
309

Description

We might want to switch from our current setup:

- a user proposes a translation
- once another user votes for the translation it get committed

to latest Weblate’s feature of translation states.

This might be needed in order to be able to build a staging website. (It’ll also involve having weblate use two Git repositories, one to store all translations, one to store only the reviewed translations -> we’ll have to see how to make this happen, likely we’ll have to query it’s database directly and add the corresponding commits.)

However, it seems that these translation states always commit and modify the PO files. And the states are only stored in Weblate’s DB. This is what we want to verify.
Doc: https://docs.weblate.org/en/latest/workflows.html#translation-states

Subtasks

Related issues

Related to Tails - Bug #15365: Check if voting mechanism in Weblate WRT validity of strings Resolved 2018-03-02

History

#1 Updated by Anonymous 2018-03-02 10:54:28

#2 Updated by Anonymous 2018-03-02 10:55:12

  • Target version set to Tails_3.7

#3 Updated by Anonymous 2018-03-13 15:51:18

  • related to Bug #15356: Automate adding new components to Weblate added

#4 Updated by Anonymous 2018-03-13 15:51:27

  • related to deleted (Bug #15356: Automate adding new components to Weblate)

#5 Updated by Anonymous 2018-03-13 15:51:31

  • related to Bug #15365: Check if voting mechanism in Weblate WRT validity of strings added

#6 Updated by bertagaz 2018-05-10 11:09:06

  • Target version changed from Tails_3.7 to Tails_3.8

#7 Updated by Anonymous 2018-06-12 14:25:58

As we have a working script to extract suggestions, we can very easily stick to our current setup. In particular as the translation states are only stored in the DB → and thus here again we would have to modify our current script to extract these states instead of the suggestions.

#8 Updated by intrigeri 2018-06-26 16:27:41

  • Target version changed from Tails_3.8 to Tails_3.9

#9 Updated by Anonymous 2018-09-03 17:55:40

  • Target version changed from Tails_3.9 to Tails_3.10.1

Won’t be able to do this in the next 48 hours (release of 3.9)

#10 Updated by intrigeri 2018-10-24 17:03:31

  • Target version changed from Tails_3.10.1 to Tails_3.11

#11 Updated by Anonymous 2018-11-02 18:49:11

  • Assignee set to hefee

I’m not sure we need this anymore, but just to be safe, I let you look into it.

#12 Updated by hefee 2018-12-02 13:22:00

  • Status changed from Confirmed to Resolved

#13 Updated by intrigeri 2019-06-27 17:16:42

  • Assignee deleted (hefee)