Enable Tajik localization in prod#15784
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15784 +/- ##
==========================================
- Coverage 79.07% 79.07% -0.01%
==========================================
Files 160 160
Lines 8360 8359 -1
==========================================
- Hits 6611 6610 -1
Misses 1749 1749 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@peiying2 are we OK to enable this locale in production? Thanks |
|
@peiying2 following up here (apologies if I've missed a response in another channel) - can you confirm if we should add Tajik localization in production? |
|
The translations don't look too bad: https://www-dev.allizom.org/tg/?xv=legacy @flodolo I know you're not PM for this locale, but have added it versions ago to the product — maybe you'd be able to facilitate the discussion to enable it for wwwmo prod, too? Thanks. |
|
Our internal documentation says that the threshold is 85%. @peiying2 is out this week, and possibly the next as well. Since this isn't time-sensitive, I would wait until she's back, or check back at the end of next week. |
|
@janbrasna not sure if you or others are working on this. The community is pretty active even though it has not met the threshold yet. Let's go ahead and enable it on production. |
|
@alexgibson |

One-line summary
Adds
tgto allowed locales in settings to stop 404ing in prod.Significant changes and points to review
Following up from #15021, this is pending approval from l10ns.
This locale is still listed on the global root home page and offered to crawlers, but returns 404 as it is not explicitly allowed. (The reason is explained in both the previous PR and the linked issue.)
After an inquiry during the previous PR into the commitment of keeping Tajik version of wwwmo up to date, the community got very active the following months, and went from ~20% to currently 60%+ of translated content, with the usual key pages as home, products, browsers, vpn etc. above the threshold for enabling the locale. So the question is, whether also the Tajik locale wouldn't be a worthwhile addition, given its recent activity.
Issue / Bugzilla link
#15010
Testing
(in prod mode, with Debug=False & Dev=False)
http://localhost:8000/ (with Accept-Locale unset)
http://localhost:8000/404-locale/
http://localhost:8000/tg/