The default bug view has changed. See this FAQ.

[SUMO KPI dashboard] display L10n coverage number

RESOLVED FIXED in 2012Q1

Status

support.mozilla.org
General
P1
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: atopal, Assigned: rrosario)

Tracking

unspecified
2012Q1

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=sumo-team c=kpidash s=2012.5 p=2)

(Reporter)

Description

5 years ago
The definition of this is tbd.
(Reporter)

Updated

5 years ago
Priority: -- → P1
(Assignee)

Comment 1

5 years ago
It is hard to estimate this without a definition. I am assuming it has to do with the number of documents that are ready for l10n that don't have an up to date translation yet. But I have a feeling you will mix in traffic data, which will make it more complicated.

Until we have a definition, *for planning purposes only* I am making it a 2pter like most of the new metrics we have added to the dashboard.
Whiteboard: u=sumo-team c=kpidash s=2012.4 p= → u=sumo-team c=kpidash s=2012.4 p=2
(Reporter)

Updated

5 years ago
Whiteboard: u=sumo-team c=kpidash s=2012.4 p=2 → u=sumo-team c=kpidash s=2012.5 p=2

Comment 2

5 years ago
As you say, we want to weight the amount of translations by locale traffic;

The algorithm of the definition is:

-----
SUMO visits = Total non-en-US SUMO visits for the last 3 months from WebTrends;
Total translated = 0;

For each locale different to en-US {
Total translated = Total Translated + ((Number of updated articles from the English top 50 most visited articles)/50 ) * (Visitors for that locale / SUMO visits));
}
------

There's no need to calculate the visits and the list of articles that we evaluate more than once a quarter if that simplifies the code.
(Assignee)

Comment 3

5 years ago
(In reply to Ibai from comment #2)
> Total non-en-US SUMO visits for the last 3 months from WebTrends;
> Visitors for that locale

Do we have reports setup for that in Webtrends? That is a prerequisite for any of this to happen.

Comment 4

5 years ago
Does this work?

https://analytics.webtrends.com/analytics/spaces/6356/profiles/11794/reports/FRnJo3T7MM6?dateShortcut=91d
(Assignee)

Comment 5

5 years ago
(In reply to Ibai from comment #4)
> Does this work?

Looks promising. But we'll have to figure out how to deal with the mix of .com and .org data there.

> Total translated = Total Translated + ((Number of updated articles from the
> English top 50 most visited articles)/50 ) * (Visitors for that locale /
> SUMO visits));

I am missing something here. I don't see where number of translations comes into play? You are probably implying something in "Number of updated articles from the
English top 50 most visited articles"? This part needs better definition. I am assuming it has to do with newer revisions that are ready for localization but aren't translated yet. But it does get tricky when that revision is no longer the current one, but the current one isn't ready for localization yet.
(Assignee)

Comment 6

5 years ago
To clarify, here is an example of what I was trying to describe.

en-US:
revision #1 - ready for localization
revision #2 - ready for localization
revision #3 - current revision, no ready for localization

es:
current revision is based on revision #1 above

This is out of date. But if es current revision was based on revision #2 then it is up to date.

So we need an algorithm that accounts for stuff like this.

Comment 7

5 years ago
Isn't this implemented for the UI? The localization dashboard already has a differentiation between updated and localized (translated but not updated).

Can we reuse that logic?
(Assignee)

Comment 8

5 years ago
Yeah, we can probably look at how it is done there. I just wanted clarification on what we are trying to measure. If you look at https://support.mozilla.org/es/localization, for example.

There are lists for articles that:
1- need translations
2- need immediate updates
3- need updates

Are we grouping all those together as out of date?

Comment 9

5 years ago
That's correct.

The idea is to get fresh translations. We need to push ourselves into that direction.
(Assignee)

Updated

5 years ago
Assignee: nobody → rrosario
(Assignee)

Updated

5 years ago
Depends on: 678168
(Assignee)

Updated

5 years ago
Target Milestone: --- → 2012Q1
(Assignee)

Comment 10

5 years ago
Landed on prod:

https://github.com/mozilla/kitsune/commit/4f21e8410773baed49e53122f9469190de19dd16
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.