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
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: --- → 2013Q1
OS: All → Mac OS X
Priority: -- → P2
Hardware: All → x86
Whiteboard: u=sumo-team c=wiki p= s=2013.1
This should probably be part of our "actionable metrics" dashboard
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.
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.
Leaving this out of this sprint for now. I'll work with Rosana on figuring out what we want to do.
Whiteboard: u=sumo-team c=wiki p= s=2013.1 → u=sumo-team c=wiki p= s=2013.2
Whiteboard: u=sumo-team c=wiki p= s=2013.2 → u=sumo-team c=wiki p= s=
Q1 is in the past. Moving to the future.
Target Milestone: 2013Q1 → Future
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.
Bumping for Bug Day
Tentatively putting into the 16th sprint. We should be ready by then.
Actually, let's leave it in the backlog for now. We need some sort of wireframe/mockup/spec/something.
Whiteboard: u=sumo-team c=wiki p= s=2013.16 → u=sumo-team c=wiki p= s=2013.backlog
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.
Assignee: nobody → rrosario
Whiteboard: u=sumo-team c=wiki p= s=2013.backlog → u=sumo-team c=wiki p=3 s=2013.16
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.
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.
In a pull request: https://github.com/mozilla/kitsune/pull/1575
This is deployed to prod but it is erroring out on a pyopenssl related error.
This is fixed now.
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.