tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2020-05-26T10:31:51Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/17723/var/lib/weblate/scripts/save-suggestions.py fails with > AttributeError: 'No...2020-05-26T10:31:51Zemmapeel/var/lib/weblate/scripts/save-suggestions.py fails with > AttributeError: 'NoneType' object has no attribute 'set_target'Since some days, save-suggestions script is failing because something is missing, but it is not clear to me what.
I tried to find the error, but the site is giving 503's all the time and also I don't even know the language that is causi...Since some days, save-suggestions script is failing because something is missing, but it is not clear to me what.
I tried to find the error, but the site is giving 503's all the time and also I don't even know the language that is causing the error.
The language for the guilty file would be nice, and also the string that is causing trouble.
The complete message is:
> 2020-05-26 03:21:05,847 - saveSuggestions(ERROR): Got an exception for wiki/src/about/contact.*.po(0)
> Traceback (most recent call last):
> File "/var/lib/weblate/scripts/save-suggestions.py", line 89, in <module>
> update_unit(translation, unit, s.target)
> File "/var/lib/weblate/scripts/save-suggestions.py", line 60, in update_unit
> pounit.set_target(target) # update po file with first suggestion
> AttributeError: 'NoneType' object has no attribute 'set_target'
> Traceback (most recent call last):
> File "/var/lib/weblate/scripts/save-suggestions.py", line 89, in <module>
> update_unit(translation, unit, s.target)
> File "/var/lib/weblate/scripts/save-suggestions.py", line 60, in update_unit
> pounit.set_target(target) # update po file with first suggestion
> AttributeError: 'NoneType' object has no attribute 'set_target'https://gitlab.tails.boum.org/tails/tails/-/issues/17836[trans platform] Divide reviewers in language groups2021-04-02T13:31:47Zemmapeel[trans platform] Divide reviewers in language groupsVery few contributors make changes on languages that are not their main translation language.
Following the principle of least privilege, we can create Review roles per language, so we can give reviewer status to more contributors.
Thi...Very few contributors make changes on languages that are not their main translation language.
Following the principle of least privilege, we can create Review roles per language, so we can give reviewer status to more contributors.
This groups could also be used to send emails to reviewers of each language on #17650
Example: A new group wants to start translating a language we don't speak at all, and we have no reference about them. It will feel more comfortable to only give them review status on their language, while we try to find someone to check they are translating what the documentation says.emmapeelemmapeelhttps://gitlab.tails.boum.org/tails/tails/-/issues/17671[Weblate] permission issues in staging repo2022-02-23T14:15:10Zhefee[Weblate] permission issues in staging repo_Originally created by @hefee on [#17671 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17671)_
I saw the seconfd time, that the directory
`~weblate/repositories/vcs/staging/config/chroot_local-includes/usr/share/d..._Originally created by @hefee on [#17671 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17671)_
I saw the seconfd time, that the directory
`~weblate/repositories/vcs/staging/config/chroot_local-includes/usr/share/doc/amnesia`
is `d-w-------`
I now removed the
`~weblate/repositories/vcs/staging/config/chroot_local-includes/usr/share/doc`
and run `git reset --head` and for now the permission of this directory
seems fine:
total 12
4 drwxr-sr-x 3 weblate weblate 4096 May 2 14:23 .
4 drwxr-sr-x 15 weblate weblate 4096 May 2 14:23 ..
4 drwxr-sr-x 2 weblate weblate 4096 May 2 14:23 amnesiahttps://gitlab.tails.boum.org/tails/tails/-/issues/18454Activate Russian on our website2021-10-05T11:16:34Zsajolidasajolida@pimienta.orgActivate Russian on our websiteRussian has been super active in the past months. Core pages stats:
- March: 8%
- April: 24%
- May: 33%
- June: 39%
It's now the most translated non-activated language (far ahead of zh_TW with 20%) and it as much translated than severa...Russian has been super active in the past months. Core pages stats:
- March: 8%
- April: 24%
- May: 33%
- June: 39%
It's now the most translated non-activated language (far ahead of zh_TW with 20%) and it as much translated than several languages that are activated on our website (Portuguese 37%, German 41%).
I think that we should activate it soon in order to:
- Bring Russian to our many Russian users. In 2019, Russian was the 3rd locale use behind English (76%) and German (7%).
- Keep these people motivated!
Steps to make this work:
- [x] Activate Russian in the production website. (puppet-tails!68)
- [x] Add Russian to the bundled offline documentation. (tails!551)
- [x] Add a Russian entry to the Donate button (#18528).emmapeelemmapeelhttps://gitlab.tails.boum.org/tails/tails/-/issues/17649Adapt Weblate permissions to a better translation workflow2022-02-18T10:59:29ZZen FuAdapt Weblate permissions to a better translation workflow_Originally created by @zen on [#17649 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17649)_
After having used Weblate for some months, some changes to groups and
permissions might be needed to reach a better tran..._Originally created by @zen on [#17649 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17649)_
After having used Weblate for some months, some changes to groups and
permissions might be needed to reach a better translation workflow for
translators and reviewers.
This issue will be used to track such discussions and modifications.
To be discussed:
* Add “Define author of translation upload” to translators. It means,
when you upload a po file, you should be able to give an author for it.
This is good for attribution, because sometimes you add files somebody
else has translated. This permission should be for translators, not for
reviewers. You don’t need to upload a translation while you review.
Also, every change decided here would have to be implemented in tails/sysadmin#17338.
### Subtasks
- [x] tails/sysadmin#17515 - Remove “Overwrite existing translation with upload” (not needed
when reviewing strings). Many translators have asked for the possibility of uploading translations, most notably the Chinese translators. As the rendering of the pages is very slow, it makes sense to give this possiblity to
translators. They should be able to upload a .po file and add as suggestion.
- [x] tails/#17836 - Have different groups for each language (so, for example, Italian reviewers
can only delete Italian suggestions).Translation Platform in Productionemmapeelemmapeelhttps://gitlab.tails.boum.org/tails/tails/-/issues/11763Adjust contributors documentation for translators2020-05-15T16:10:26ZAnonymousAdjust contributors documentation for translators_Originally created by @Anonymous on [#11763 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11763)_
You’ll need to test how everything works and while doing that, document
all your steps in our translation document..._Originally created by @Anonymous on [#11763 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11763)_
You’ll need to test how everything works and while doing that, document
all your steps in our translation documentation. You might want to
create a new mdwn file for that.
This includes:
- how to request one enables a language on the production website (we
have <https://tails.boum.org/contribute/how/translate/team/new/> but
it’s not Weblate-ready)
Parent Task: tails/tails#15085
### Related issues
- **Related to** tails/tails#13286
- **Blocks** tails/tails#16899Tails_4.0drebsdrebshttps://gitlab.tails.boum.org/tails/tails/-/issues/17871Allow translators to access the Machine translation suggestions2020-08-21T21:36:59ZemmapeelAllow translators to access the Machine translation suggestionsAt the moment translators have no access to machine translation suggestions while translating:
<img src="/uploads/ce4652d1fecd9bf95beabcd5518d5930/machine-translation-missing.png" width="400">
This makes their work less comfortable, an...At the moment translators have no access to machine translation suggestions while translating:
<img src="/uploads/ce4652d1fecd9bf95beabcd5518d5930/machine-translation-missing.png" width="400">
This makes their work less comfortable, and makes the translation less consistent.
We should review the permissions translators have and allow them to access the 'Machine translation' tab in Weblate, as my user with more privileges has:
<img src="/uploads/e16679b118e89cac83225067057895ed/machine-translation-on.png" width="400">Translation Platform in Productionemmapeelemmapeelhttps://gitlab.tails.boum.org/tails/tails/-/issues/15191Automate keeping the list of Core pages up-to-date in Weblate2020-05-15T14:43:30ZemmapeelAutomate keeping the list of Core pages up-to-date in Weblate_Originally created by @emmapeel on [#15191 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15191)_
To integrate the translation platform on our working system, we need to
automate the
adding of the files in
wiki/..._Originally created by @emmapeel on [#15191 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15191)_
To integrate the translation platform on our working system, we need to
automate the
adding of the files in
wiki/src/contribute/l10n\_tricks/core\_po\_files.txt to the list at
<https://translate.tails.boum.org/#list-core>
from the weblate shell:
```
from weblate.trans.models import ComponentList
corepages = ComponentList.objects.all()[0]
# Find out if all the core pages are on the core pages component list in weblate
corefiles = open("/var/lib/weblate/repositories/vcs/tails/index/wiki/src/contribute/l10n_tricks/core_po_files.txt", "r")
for page in corefiles.readlines():
compos = corepages.components.filter(filemask__contains=page[2:-2])
if (compos.count() == 0):
page
```
Gives a list of the lines that cannot be found in the component list in
weblate.
Feature Branch: https://salsa.debian.org/hefee/puppet-tails:hefee/update_core_pagesZen FuZen Fuhttps://gitlab.tails.boum.org/tails/tails/-/issues/16979Clarify how to enable a new language on our translation platform2020-05-15T12:54:54ZintrigeriClarify how to enable a new language on our translation platform_Originally created by @intrigeri on [#16979 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16979)_
- “You need to run this script with argument \`—modify\`”: I’m
confused. Previously I’m instructed to run th..._Originally created by @intrigeri on [#16979 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16979)_
- “You need to run this script with argument \`—modify\`”: I’m
confused. Previously I’m instructed to run that script without any
argument. If I have to pass `--modify`, let’s just add it to the
copy’n’pasteable command line and drop this sentence?
- “You need to \[…\] to actually create the missing po files and
commit those files”: ambiguous English grammar, this could mean
either that the script with `--modify` will add+commit the files, or
that I have to do it myself once the script has run.
I’m happy to rephrase the doc (or let u do it) once you’ve clarified
what you meant :)
Parent Task: tails/tails#15086Tails_3.16intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/17063Cleanup translate-server.git2020-05-15T12:53:02ZhefeeCleanup translate-server.git_Originally created by @hefee on [#17063 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17063)_
As discussed translate-server.git should only hold private parts. (see
https://gitlab.tails.boum.org/tails/tails/-/iss..._Originally created by @hefee on [#17063 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17063)_
As discussed translate-server.git should only hold private parts. (see
https://gitlab.tails.boum.org/tails/tails/-/issues/17063#note_6159). Everything else should end up in blueprints.
Parent Task: tails/tails#15085
### Related issues
- **Related to** tails/tails#16995
- **Related to** tails/tails#15086intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18936Contact person from Localization Lab to make progress on researching paid tra...2022-05-30T07:11:41ZintrigeriContact person from Localization Lab to make progress on researching paid translatorsdisojdisojhttps://gitlab.tails.boum.org/tails/tails/-/issues/18285Deactivate Farsi on our website2021-09-06T13:39:34Zsajolidasajolida@pimienta.orgDeactivate Farsi on our websiteOur website was translated into Farsi in 2015 but we never had a team of people to keep the translations updated and the translation coverage continuously dropped since then. It's now at 19% of core page, which is really not a lot:
## A...Our website was translated into Farsi in 2015 but we never had a team of people to keep the translations updated and the translation coverage continuously dropped since then. It's now at 19% of core page, which is really not a lot:
## All the website
- de: 26% (1854) strings translated, 14% strings fuzzy
- es: 53% (3718) strings translated, 4% strings fuzzy
- fa: 19% (1376) strings translated, 12% strings fuzzy
- fr: 85% (5946) strings translated, 4% strings fuzzy
- it: 34% (2413) strings translated, 7% strings fuzzy
- pt: 18% (1277) strings translated, 9% strings fuzzy
## Core pages of the website
- de: 44% (933) strings translated, 23% strings fuzzy
- es: 90% (1908) strings translated, 4% strings fuzzy
- fa: 19% (416) strings translated, 15% strings fuzzy
- fr: 85% (1787) strings translated, 7% strings fuzzy
- it: 67% (1406) strings translated, 15% strings fuzzy
- pt: 39% (823) strings translated, 14% strings fuzzy
Unless there's an active Farsi team on Weblate, I think that we should disable it from our website (and builds).
For the record, I proposed something difference 1 year ago thinking that the translation platform would be "ready for production" earlier.
https://lists.autistici.org/message/20200512.150200.12d986e0.en.html
[This](https://gitlab.tails.boum.org/tails/tails/-/boards?scope=all&utf8=%E2%9C%93&milestone_title=Translation%20Platform%20in%20Production) is taking much longer than expected and I prefer if we'd stop advertise such a poorly translated language on our website without waiting any longer.Zen FuZen Fu2021-06-06https://gitlab.tails.boum.org/tails/tails/-/issues/18934Discuss the future of our Translation platform2022-04-28T06:57:26ZintrigeriDiscuss the future of our Translation platformOnce sysadmin#17782 is done, it'll be a good time to have a conversation about several topics that are related to each other.
[[_TOC_]]
Strategy building
=================
Goal: decide on high-level strategic goals that will inform th...Once sysadmin#17782 is done, it'll be a good time to have a conversation about several topics that are related to each other.
[[_TOC_]]
Strategy building
=================
Goal: decide on high-level strategic goals that will inform the roadmap.
Past and present
----------------
Goal: ensure we're on the same page regarding the past, so we can then focus on the future.
Process: read this section and add your comments on the pad.
### Long story short
1. 2015: prototyping Weblate for Tails
2. 2017Q4: we got a 11k€ grant approved to implement this in production.
- Stated goals:
- lower the technical barrier for new translators to help
- get translations into other languages such as Spanish, Arabic, Chinese, Russian
- For various reasons, this project did not succeed within the planned timeline & budget.
3. 2018: we negotiated an extra 8.5k€ from Tails unrestricted funds for a new team to finish the bulk of the work
4. June 2019: hefee & intrigeri complete their part of the work, release it to a wild, unsuspecting word, and hand over to Zen Fu for maintenance
5. 2019: we realize that what we deployed is not exactly ready for prime time and is a PITA to maintain
6. 2019-2022:
- Most of the dev/sysadmin capacity on this team is spent on fixing bugs, upgrading Weblate, and finally on making the backend easier to maintain & upgrade. All of which took significantly longer than anticipated, but eventually succeeded.
- The Translation Platform uses about half of our sysadmin capacity over the last 2.5 years. This has made us put other sysadmin projects on the backburner, which in turn blocks improving other areas of Tails.
- emmapeel is asked to be patient until the aforementioned backend work is done, before we can give her workflow and UX improvements proposals the attention they deserve. We understand this has been frustrating.
### Impact on translations and translators
- A few new translators for existing languages (https://translate.tails.boum.org/manage/users/?q=&sort_by=-profile__translated), yeah!
- OTOH, a few new translators have _hundreds_ of pending suggestions waiting to be reviewed, which suggests the translator/reviewer ratio is not right.
- We lost some historical translators but that's probably not related to the translation platform.
- In the last 12 months, 3 languages that were already activated on our website are improving, 2 are regressing
| Language | 2021-02: core pages | 2022-03-15: core pages | 2021-02: full website | 2022-03-15: full website |
| ------ | ------ | ----- | ----- | ------ |
| de | 44% | 29% ↓ | 26% | 20% ↓ |
| es | 90% | 69% ↓ | 52% | 44% ↓ |
| fr | 81% | 91% ↑ | 79% | 94% ↑ |
| it | 60% | 70% ↑ | 31% | 35% ↑ |
| pt | 39% | 56% ↑ | 18% | 24% ↑ |
- Languages activated on our website in the last 12 months:
- 1 new (Russian), which has seen no activity on Weblate since months
- 1 removed (Farsi)
- We lack recent qualitative data from existing translators, that could help prioritize the next steps.
- For example: survey users to know how they feel compared to the old setup, or what they find difficult about using the translation platform.
- According to https://gitlab.tails.boum.org/tails/summit/-/wikis/2021/Team_reports#translation-platform, "Translators report it's much easier to use than the previous (Git-based) system".
- Gathering and relaying such information is part of the "Community management" role on this team.
- emmapeel reported such data on GitLab issues where she proposed UX and workflow improvements. It's not clear if the UX data that backs these proposals is still up-to-date.
### Backend maintenance
It is now vastly easier to maintain and upgrade the Weblate application.
### Team health
We lack recent self-evaluation of the different roles on the team.
What we know:
- Zen Fu reached the biggest milestones the team had set wrt. the backend. There's something to learn from the fact it took more work and a greater lead time than planned, which impacted emmapeel and other sysadmin projects.
- Since a year or so, emmapeel has not been as active as initially planned in Tails in general, and on this team in particular. We're aware of various reasons for this. We would understand if the "please hold on and be patient" moto had been a big demotivating factor.
- In 2021 we clarified decision making on this team, in an attempt to address tensions between emmapeel and hefee.
- hefee is happy to help Zen Fu occasionally, in a "Helper" capacity. Zen Fu is fine with this.
Where do we want to be in 2 years?
----------------------------------
XXX
Resources:
- [tier-1 languages](https://tails.boum.org/contribute/how/translate/#tier-1-languages)
- sajolida's email sent on 2022-03-10 (`id:de4dba82-0e0e-5299-e381-a3f3b17155d8@pimienta.org`)
Understanding capacity
----------------------
Goal: understand what the actual capacity of the team actually looks like
- General time commitments of the folks participating in the team
- Amount of necessary maintenance "KTLO" ("keeping the lights on) work
Roadmapping
===========
This is informed by:
- the strategy decided above
- the KLTO work:
- upgrading Weblate regularly (sysadmin#17890)
- anything else?
Potentially useful links:
- ["Translation Platform in Production" milestone](https://gitlab.tails.boum.org/groups/tails/-/boards?scope=all&milestone_title=Translation%20Platform%20in%20Production)
- [All Translation platform issues](https://gitlab.tails.boum.org/groups/tails/-/issues?scope=all&state=opened&label_name[]=C%3ATranslation%20Platform)
Team's needs
============
What skills and capacity does the team lack to execute the roadmap?
Misc
====
- What's the future of hefee on the translation platform team? Is the hand-over finished? Does it still make sense that hefee is a member of the team? Or formalize a "Helper" status like the FT is introducing (not formally a team member, not part of meta/self-organization/decision-making, the team can delegate them some work)?
Related issues
==============
Blocked by:
- [x] sysadmin#17782
- [x] tails#18307
- [x] Gathering data about the benefits of the containerized setup (tails/tails#18308)Tails_5.0intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15085Document our translation platform infrastructure2020-05-15T14:42:51ZAnonymousDocument our translation platform infrastructure_Originally created by @Anonymous on [#15085 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15085)_
### Subtasks
- [x] tails/tails#11760
- [x] tails/tails#11761
- [x] tails/tails#11763
- [x] ta..._Originally created by @Anonymous on [#15085 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15085)_
### Subtasks
- [x] tails/tails#11760
- [x] tails/tails#11761
- [x] tails/tails#11763
- [x] tails/tails#12333
- [x] tails/tails#13286
- [x] tails/tails#15086
- [x] tails/tails#15087
- [x] tails/tails#15089
- [x] tails/tails#16899
- [x] tails/tails#17063
### Related issues
- **Related to** tails/tails#15359Tails_4.1https://gitlab.tails.boum.org/tails/tails/-/issues/16844Don't use the same working copy in Weblate as in update_weblate_git.py2020-05-15T12:59:27ZintrigeriDon't use the same working copy in Weblate as in update_weblate_git.py_Originally created by @intrigeri on [#16844 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16844)_
`update_weblate_git.py` assumes ownership of its working copy during
some of the time it’s running. If Weblate tri..._Originally created by @intrigeri on [#16844 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16844)_
`update_weblate_git.py` assumes ownership of its working copy during
some of the time it’s running. If Weblate tries to pull or commit during
that time, all kind of bad things™ can happen.
Presumably, `update_weblate_git.py` could have its own working copy and
merge from the Weblate’s one before it sync’s with the canonical
(“main”) Git repo.
Feature Branch: https://salsa.debian.org/hefee/puppet-tails/tree/hefee/16844-different-working-directory
### Related issues
- **Related to** tails/tails#16874
- **Blocks** tails/tails#15087Tails_3.16intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/18308Evaluate the practical impact of having containerized Weblate2024-02-05T14:03:29ZintrigeriEvaluate the practical impact of having containerized WeblateAs per our meeting last week, we should evaluate the impact with these 2 criteria:
- lowering the maintenance cost
- non-root folks can help with the "backend" part
We said we wanted to do it twice:
- after the 1st post-containerizat...As per our meeting last week, we should evaluate the impact with these 2 criteria:
- lowering the maintenance cost
- non-root folks can help with the "backend" part
We said we wanted to do it twice:
- after the 1st post-containerization upgrade (probably only applicable to the maintenance cost criterion)
- after using it to do a few upgrades and folks had enough time to contribute to the platform without being root
# Notes about 1st post-containerization upgrade (3.11 to 4.9)
For [this upgrade](sysadmin#17782) the following steps had to be repeated 10 times (one for each intermediate version, as they can't be skipped):
- Update `settings.php` with the new version.
- Fix any issues with our custom scripts, for example:
- Account for any changes in Weblate/Django API.
- Make sure hardcoded Python paths are correct.
- Check for important changes in the image (eg. changes in the base image).
- Bump the container image version.
- Run Puppet.
- Watch database migrations being applied in the container's log.
This is considerably less work than in the previous setup in which we had to, on top of the above, also handle Python module dependency resolution as well as versions and repositories pinning via Puppet-managed calls to `pip`. The previous setup also didn't implement purging of old/unneeded Python packages, leaving old dependencies behind in the `/usr/local/lib/python3*` directories. This could've been implemented but there were other pressing issues (such as the shutdown of the Pypi API which made automation even more difficult, the speed of Weblate releases, etc) and we decided to solve several issues at once with the move to a containerized service.
After some preparation, the actual upgrade process took around 5h, counting creation of backups (which i did a total of 3 times because of mistake and over-caution), doing all of the 10 upgrades and then checking that the system was working correctly and fixing small bits. I used a local copy of the Puppet code repo plus some simple tooling to automate some of the steps, because I wanted to be able to revert or restart the upgrade process without having to deal with the production repo during the process.
The [next upgrade](sysadmin#17890) will need some adaptation to our custom scripts because there's a change in the base image which affects Python paths. Shouldn't be much work, though, and the dev/test server is serving as an important tool to make such work significantly smoother.
# Notes about 2nd post-containerization upgrade (4.9 → 5.3)
[This upgrade](sysadmin#18030) was much easier than the last one:
- Setting up a dev env was fairly simple, using the tails/puppet-weblate> module. Performing this step was important to help fix our integration scripts tests and the CI pipeline before deploying to production. It can probably be skipped when the CI is green. I did not use the test env to perform a test upgrade for the last upgrade of this batch (5.2 → 5.3) and just did it directly in prod.
- Some new improvements to the containerized setup made upgrading easier:
- There's no need to maintain hardcoded Python paths anymore (puppet-weblate@3c090df9308a7a66b32c7e7780a20e09a288a44b, puppet-weblate@fb0509322ac8d5d2b06ef6d863f18c0cfd3ede78)
- Moved to a separate settings override file (puppet-weblate@fb0509322ac8d5d2b06ef6d863f18c0cfd3ede78)
- Upgrading can now be almost as easy as updating the versions in Puppet and deploying:
- Upgrade example: puppet-weblate@f0c817dc7cf806044b38c732276b0f3eab9bb7b7
- Upgrade instructions: puppet-weblate@6ae3c5898fec78b41f66401a4bf93f2efbb8eb35
- I still had to go through more than one upgrade, but that's because there was a major version upgrade in between:
- The first one (4.9 → 5.0) took long because of database upgrade (~1h30m)
- The next ones (5.0 → 5.2 and 5.2 → 5.3) were fast and only needed an update to the container image version.
- I could've done only 2 upgrades instead of 3, but the image for 5.3 was released yesterday, right after I had already upgraded to 5.2. The good news is that the last upgrade took about 5 min to complete and about 2 min downtime.
Overall, the move to a containerized setup had a significant impact in upgrades and maintainability of our Weblate setup.
It's hard to evaluate impacts in external contributions because the Translation Team is not functional anymore as a team.
# Next steps
- [x] Upgrade Weblate to latest
- [x] Describe the experience in this issueZen FuZen Fuhttps://gitlab.tails.boum.org/tails/tails/-/issues/19999Find out how translation teams are doing2024-02-14T14:55:30ZZen FuFind out how translation teams are doingIn the stand-up of Sep 25th 2023 we discussed that having more info about how translation teams are doing could help make better decisions for the future.
Here are some questions we thought:
- What language team(s) are you part of?
- W...In the stand-up of Sep 25th 2023 we discussed that having more info about how translation teams are doing could help make better decisions for the future.
Here are some questions we thought:
- What language team(s) are you part of?
- When was the last time you did translation work? How often do you do it nowadays?
- Do you perceive the team is functional?
- Does your team split translation work from review work? Why?
- Extra space for notes. maybe they want to tell us something!
To do:
- [x] Build a survey
- [x] Check with GA what can be improved
- [x] Share with tails-l10n and team lists with a deadline
- [x] Analyse results
- ~~Consider changes to the role of the Translation Platform maintainers (see [this comment](https://gitlab.tails.boum.org/tails/tails/-/issues/20047#note_221680) for context).~~ → Moved to tails#20202Zen FuZen Fuhttps://gitlab.tails.boum.org/tails/tails/-/issues/19416get validator rights for french2023-02-09T16:37:21Zconan FutureBoyget validator rights for frenchI've asked for validator rights for french, a month and a half ago. Got vouched by a present validator, and got not rights so far.
https://lists.autistici.org/message/20230118.210400.45d255f4.en.html
I try the request here.I've asked for validator rights for french, a month and a half ago. Got vouched by a present validator, and got not rights so far.
https://lists.autistici.org/message/20230118.210400.45d255f4.en.html
I try the request here.Zen FuZen Fuhttps://gitlab.tails.boum.org/tails/tails/-/issues/10037Help Weblate maintainers to add the package to Debian2020-05-15T17:23:21Zsajolidasajolida@pimienta.orgHelp Weblate maintainers to add the package to Debian_Originally created by @sajolida on [#10037 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/10037)_
ask weblate dev to put weblate in debian and to package the one missing
module which is not in debian
..._Originally created by @sajolida on [#10037 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/10037)_
ask weblate dev to put weblate in debian and to package the one missing
module which is not in debian
### Related issues
- **Related to** tails/tails#10038
- **Related to** tails/tails#16974drebsdrebshttps://gitlab.tails.boum.org/tails/tails/-/issues/17072Improvement comments in puppet scripts for Weblate2020-05-15T12:51:12ZAnonymousImprovement comments in puppet scripts for Weblate_Originally created by @Anonymous on [#17072 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17072)_
Hi hefee,
I am currently reviewing the design doc, and I see some issues in the
puppet script comments. I cannot ..._Originally created by @Anonymous on [#17072 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/17072)_
Hi hefee,
I am currently reviewing the design doc, and I see some issues in the
puppet script comments. I cannot commit there and I’m too lazy to set up
a clone and make a pull request. Can you please changes those comments?Tails_4.0intrigeriintrigeri