970216 - Add a "Top 100" progress bar

Status: RESOLVED FIXED

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

Description

[Rosana Ardila]

In order to achieve the goal of this year of maintaining the Top 100 articles localized a progress bar would be very helpful.

Right now we have the "Top 20" and ideally we could have some stages:

Top 20, Top 50, and finally Top 100. This would motivate the localizers and also help as a psychological help for those aiming to reach the Top 100. There are some successes on the way.

Ideally we could find a good UI to solve this in one single progress bar.

Let me know if you have any questions.

Thanks,

- Rosana

Comment 1

[Rosana Ardila]

bumping this! we need this fast ;)

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

(In reply to Rosana Ardila from comment #1)
> bumping this! we need this fast ;)

it's in the next sprint right now.  s=2014.5

Comment 3

[Ricky Rosario [:rrosario, :r1cky]]

We have a list of questions we want to try out for new features requested. This is the perfect bug to try it out....

1. What current problem does this solve?
2. What would users/contributors see?
3. What would users/contributors do? What would happen as a result?
4. How does this affect mobile views of the site?
5. How does this affect localizers and the non-en-US part of the site?
6. Who is responsible for this change?
7. Will this require verification on the stage server?
8. Is there anything else we should know?
8. How do we know it was successful?


Let's talk about the problem and these questions and then decide on a good solution. Moving to the backlog until then.

Comment 4

[Rosana Ardila]

sorry Ricky, didn't mean to upset the devs, but I think this needs some UX work, that's why I was bumping it. I already sent Bram an email, so I hope he can help us.

Comment 5

[Rosana Ardila]

1. What current problem does this solve?
We want to target the Top 100 articles, right now we only have top 100 or all
2. What would users/contributors see?
a progress bar as described in the first comment
3. What would users/contributors do? What would happen as a result?
It would help us track the top 100 articles and motivate contributors 
4. How does this affect mobile views of the site?
I don't know, this one is for Kadir
5. How does this affect localizers and the non-en-US part of the site?
gives more clarity on the goals
6. Who is responsible for this change?
Rosana/Ibai
7. Will this require verification on the stage server?
I assume
8. Is there anything else we should know?
This will probably need an extra graphic on the locale metrics with the top 100 besides the top 20 and All
8. How do we know it was successful?
we need to see if we can reach and maintain the top 100 articles in the top locales by the end of the year

Comment 6

[Ricky Rosario [:rrosario, :r1cky]]

moving metadata back to where it was before comment 4....

(In reply to Rosana Ardila from comment #5)
> 1. What current problem does this solve?
> We want to target the Top 100 articles, right now we only have top 100 or all

Where does 100 come from? Why not any other number? What percent of total KB traffic does the Top 20 vs Top 100 cover?

> 8. Is there anything else we should know?
> This will probably need an extra graphic on the locale metrics with the top
> 100 besides the top 20 and All

OK, so we need to track historical values of the metric not just the current value?

Comment 7

[Rosana Ardila]

(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #6)
> moving metadata back to where it was before comment 4....
> 
> (In reply to Rosana Ardila from comment #5)
> > 1. What current problem does this solve?
> > We want to target the Top 100 articles, right now we only have top 100 or all
> 
> Where does 100 come from? Why not any other number? What percent of total KB
> traffic does the Top 20 vs Top 100 cover?
This comes from analyzing the SUMO traffic. To have the best coverage we need to cover the Top 100 artciles in the 15 top locales, the top 20 isn't enough and going for all articles is too much since we keep adding more with the new products.

> 
> > 8. Is there anything else we should know?
> > This will probably need an extra graphic on the locale metrics with the top
> > 100 besides the top 20 and All
> 
> OK, so we need to track historical values of the metric not just the current
> value?
Yes, and this would be displayed in a graphic: https://bugzilla.mozilla.org/show_bug.cgi?id=974956

Comment 8

[Ibai Garcia [:ibai]]

The top 12 locales cover 90% of the market and
The top 100 articles per locale cover something like 99% of the traffic to that locale. You could say to take 95 or 103 articles and probably we will have a very similar coverage. 100 is rounder and easier to communicate.

Comment 9

[Ricky Rosario [:rrosario, :r1cky]]

This should be 2pts for the current % in the overview section of the l10n dashboard.

Comment 10

[Kadir Topal [:atopal]]

> 4. How does this affect mobile views of the site?
>> I don't know, this one is for Kadir

No impact, since we don't support localization on mobile yet.

Comment 11

[Ricky Rosario [:rrosario, :r1cky]]

will do today.

Comment 12

[Ricky Rosario [:rrosario, :r1cky]]

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

We didnt get UX feedback per comment 4, so for now we are going with this:
http://cl.ly/image/3E253f0x392G

We can start a new bug if we want a nicer visualization (like a stacked progress bar).

Comment 13

[Rosana Ardila]

Thank you Ricky! This should work just fine.

A better UX improved progress bar is certainly a nice to have high on my list.

Comment 14

[Ricky Rosario [:rrosario, :r1cky]]

Landed on master:
https://github.com/mozilla/kitsune/commit/66ae5b42752bf3f7fd15189b954e14797d5ba90b

Comment 15

[Ricky Rosario [:rrosario, :r1cky]]

Deployed to prod now.