819385 - SUMO L10n aggregated dashboard

Status: VERIFIED FIXED

(support.mozilla.org :: Localization, task, P2)

Description

[Rosana Ardila]

In order to know the status of the l10n coverage in detail, a dashboard displaying the aggregated information of various locales would make it easier to understand quickly how each locale is affecting the KPI and which locale needs more attention. Also it would help us assess which locales have almost no activity. Ideally this information could be stored and aggregated so that we can have insights into the activities of the locales over time.

An idea for getting a fast understanding of the status of the locales would be to see in one page the localization dashboard information of various locales together. The information could be displayed by order of traffic showing e.g. the top 10 locales in the first page, 11-20 locales in the second and so on. The display could show the graphs already displayed in the locales dashboards.

Let me know if you have questions.

Thanks,
Rosana

Comment 1

[Kadir Topal [:atopal]]

This should probably be part of our "actionable metrics" dashboard

Comment 2

[Ibai Garcia [:ibai]]

This doesn't really need to be beautiful or visible for everyone... if adding it to the actionable metrics is going to take more time, I will suggest to go for a scrappier solution. The actual Google Doc is almost perfect. Rosana confirm if I'm wrong.

Comment 3

[Rosana Ardila]

I agree with Ibai, it's more important to have this faster rather than beautiful or visible for everyone. Ricky's excel sheet is already a very good first step, we will try to automate it and generate graphs.

If it's a low hanging fruit and can be integrated late with the actionable metrics I would like to see it there. But for the moment let's focus on the first scrappy solution.

Comment 4

[Ricky Rosario [:rrosario, :r1cky]]

Leaving this out of this sprint for now. I'll work with Rosana on figuring out what we want to do.

Comment 5

[Ricky Rosario [:rrosario, :r1cky]]

Q1 is in the past. Moving to the future.

Comment 6

[Ibai Garcia [:ibai]]

What's the status of this?

If it wasn't resolved and it's still needed, we should add it to the Q3 efforts around contributors.

Comment 7

[Andrew Truong [:feer56] [:andrewtruong] [:atruong]]

Bumping for Bug Day

Comment 8

[Ricky Rosario [:rrosario, :r1cky]]

Tentatively putting into the 16th sprint. We should be ready by then.

Comment 9

[Ricky Rosario [:rrosario, :r1cky]]

Actually, let's leave it in the backlog for now. We need some sort of wireframe/mockup/spec/something.

Comment 10

[Ricky Rosario [:rrosario, :r1cky]]

I will work out the UI for this with Rosana while creating the page.

Making it a 3pt to have enough time to figure out the UI, create the page and required API calls to grab data for the graphs.

Comment 11

[Ricky Rosario [:rrosario, :r1cky]]

So far we came up with these options:

* Option A: 3 graphs (top 20 %, all %, # contributors) and you can select the locales to compare (by default: top 10)
* Option B: One graph per locale that shows the 3 series of data (top 20 %, all %, # contributors). We would show 10? graphs at a time, by default they would be the top 10 locales
* Option C: Only one graph with all the data together and options to turn on and off different series and locales.

Comment 12

[Rosana Ardila]

Ricky,

Thanks for updating the details. I'd love to see  option C implemented, but if it takes too much time we can go with A or B.

Comment 13

[Ricky Rosario [:rrosario, :r1cky]]

In a pull request:
https://github.com/mozilla/kitsune/pull/1575

Comment 14

[Ricky Rosario [:rrosario, :r1cky]]

Landed on master:
https://github.com/mozilla/kitsune/commit/2f43095e81d196b6b5ec296acf300c26eb37bc83

Comment 15

[Ricky Rosario [:rrosario, :r1cky]]

This is deployed to prod but it is erroring out on a pyopenssl related error.

Comment 16

[Ricky Rosario [:rrosario, :r1cky]]

Filed bug 908065

Comment 17

[Ricky Rosario [:rrosario, :r1cky]]

This is fixed now.