A while back, we wrote scripts/l10n_completion.py which runs via cron at 3:30am every day. It generates l10n_history.json and l10n_summary.json files based on the current state of translations for strings in the Kitsune web app. These files are used in the localization dashboard as well as in the postatus app (https://postatus.herokuapp.com/) to help us see translation status and address areas of concern. I recently changed the postatus app to show "percent translated" as a float since Kitsune has a gazillion strings and if the change day-to-day was under gazillion / 100, then it wouldn't even register in the postatus app as getting better or worse. I updated the equivalent script in Fjord to show floats (I also added untranslated_words which is helpful). This bug covers updating the script in Kitsune to: 1. save float values rather than integer values for "percent translated" 2. (optional, but would be handy) add untranslated_word counts
I did the changes for Fjord, so I should probably do the changes for Kitsune, too. It's not super hard, but we don't have tests for it and so it takes some eyeballing and double-checking, etc. Given that, I'm going to grab it and do it in my nearest slot of spare time.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
I didn't do this. I'm currently rewriting all this infrastructure and moving it elsewhere. Thus we don't have to rely on flakey server stuff that seems to keep changing and we'll be in a better position to switch to AWS down the line anyhow.
Repurposing this to remove the script altogether. That coupled with the new script that runs on people.m.o fixes this issue. Removing script in a PR: https://github.com/mozilla/kitsune/pull/2710
Summary: fix l10n_completion script to use floats → nix l10n completion infrastructure
Landed in https://github.com/mozilla/kitsune/commit/0c58e9e4411010262bd451b2adb6ef7221d7cb2b Pretty sure it's gone out by now. Closing as FIXED.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.