Thanks Neil. I'll wait for you to detail the last two bullet points a bit more. As far as the "Add a weekly average to the line graphs" request, there's something already there. It's hard to see because annoyingly there's a deployment annotation in front of it, but if you look in the bottom left corner you'll see a little textbox. It has a 1 in it, which means it's averaging 1 data point at a time. If you change it to 7, it will average out the points weekly. It's much easier to see this if you zoom into the middle of the graph so the annotation gets out of the way.

Some notes inline. By the way, did you and @violetto get a chance to meet about this?

In general, this task seems like it could be broken down and prioritized so we can get to each item more quickly

• Make it possible to show and hide individual series on the line graphs. When showing data for both VisualEditor and Wikitext, the "success by experience of user" graph has 14 lines, which makes it impossible to read.

Yes! Btw, this change would be fairly self-contained in dashiki, if you want I can show you around the code.

• Show descriptions on the dashboard. The config page on Meta has some, but they aren't shown. I'm happy to add the descriptions myself if you can show me how.

There are actually descriptions that should show up in a tool-tip when you hover over the title of each section. However that tooltip library has some weird layout bug that makes it not show up most of the time. I can point you to that code too.

• Add a VE adoption metric. Blocked on deciding exactly how we want to operationalize this.

Are you actively following up on this? Without this, is the dashboard less useful overall or should the other things be broken out and done separately?

• Decide whether there would be a significant performance saving to getting rid of most per-wiki metrics, given that we still want a global number. If so, I will make list of top projects we want to track.

For now, let's leave this out and worry about it later. It's good enough for me if you keep this in mind when adding new metrics to track.

• Labels on the X axis of the "failures by user type" graph cut off if the window is narrow (for example, 1080px).

We should break this out as a separate task and fix it 'cause it's just a resizing bug.

• Visualize the edit funnel with a Sankey diagram rather than a sunburst chart. I can work on this if you think it's a fairly accessible issue.

This would be harder than the first two bullet points but not too hard. I'm happy to show you roughly how to accomplish this.

@Milimetric: I think I've arrived at a more-or-less final list of requests (ordered by priority).

The VE adoption metric is definitely important to us; it's tracked for a handful of wikis on one of the Limn dashboards, but we would like it globally available with per-project breakdowns. Breakdowns by user experience would be nice to have as well, but they are less important. At this point, we're most interested in Wikipedias since VE has so far been designed primarily with them in mind, so we can leave out other projects if that's helpful.

It sounds like the other tasks are fairly straightforward ones which I could take a stab at myself; should I schedule some time next week so we can talk through the code?

About @violetto, I honestly don't want to waste her firepower on a dashboard that's going to be used by at most a dozen people. Perhaps she could help with Wikistats 2.0, into which I hope we'll eventually fold this dashboard, instead?

Next week we're all at Wikimania. If you're coming, we can catch up quickly there and schedule something for afterwards. So anything after July 20th works for me. We'll prioritize this card after that meeting then.

Agreed that Wikistats 2.0 would be a great use of @violetto's time, let's talk about that, May.

Sounds good to me, I'll be at Wikimania.

I'll be at Wikimania as well. I'll definitely catch up with you guys there!

Suggestions for how to get at these improvements, in case someone wants to work on them before we prioritize:

All visualizers use TimeseriesData, which is defined here: https://github.com/wikimedia/analytics-dashiki/blob/master/src/app/data-converters/timeseries-data.js

• Make it possible to show and hide individual series on the line graphs. When showing data for both VisualEditor and Wikitext, the "success by experience of user" graph has 14 lines, which makes it impossible to read.

• https://github.com/wikimedia/analytics-dashiki/tree/master/src/components/visualizers/dygraphs-timeseries
• wrap the dygraphs-timeseries component in something like a filtered-timeseries-data component
• example of project selector: https://vital-signs.wmflabs.org/#projects=dewiki,frwiki/metrics=Pageviews
  • Add a VE adoption metric (specifically, the number of edits tagged "VisualEditor" as a proportion of total edits in a given period). This one is particularly useful to have per-wiki breakdowns.

• So once your data is going to a convention-based path here: http://datasets.wikimedia.org/limn-public-data/metrics/failure_rates_by_type/visualeditor/
• Then you can add a config section here: https://meta.wikimedia.org/wiki/Config:VisualEditorAndWikitext and your metric will just work (assuming it's using one of the available comparison types [timeseries, sunburst, or stacked-bars])
  • Show descriptions on the dashboard. The config page on Meta has some, but they aren't shown. I'm happy to add the descriptions myself if you can show me how.

• Best way is just to replace the broken semantic-ui popup widget thing. You can do this globally here: https://github.com/wikimedia/analytics-dashiki/blob/master/src/app/ko-extensions/global-bindings.js#L88
  • Visualize the edit funnel with a Sankey diagram rather than a sunburst chart. I can work on this if you think it's a fairly accessible issue.
  • Improve the averaging selector by moving the box out of the graph area (probably to the top bar, next to the graph title and time range) and surrounding it with the text: "Averaging: [BOX] day(s)"

• just style the input[type=text] box underneath dygraph-timeseries elements with top: 0 or something (in styles.css): https://github.com/wikimedia/analytics-dashiki/blob/master/src/layouts/compare/01_styles.css

Change 231424 had a related patch set uploaded (by Milimetric):
[WIP] Add filters above timeseries graphs in the compare layout

https://gerrit.wikimedia.org/r/231424

@Neil_P._Quinn_WMF, see the patch attached to probably get more clarity about the stuff we were talking about last week. It's the start of the work needed for "Make it possible to show and hide individual series on the line graphs." Baha is going to take it from here, after he reads up a bit, but the skeleton is done so it's useful to see how dashiki works.

Change 231424 merged by Milimetric:
Add filters above timeseries graphs in the compare layout

https://gerrit.wikimedia.org/r/231424

Change 237621 had a related patch set uploaded (by Bmansurov):
Correctly show comparison descriptions in a popup

https://gerrit.wikimedia.org/r/237621

Change 237636 had a related patch set uploaded (by Bmansurov):
Make the roller input easier to read

https://gerrit.wikimedia.org/r/237636

Change 237621 merged by Milimetric:
Correctly show comparison descriptions in a popup

https://gerrit.wikimedia.org/r/237621

Change 237636 merged by Milimetric:
Make the roller input easier to read

https://gerrit.wikimedia.org/r/237636

These last two improvements by Baha have been deployed.

Nice.

Closing.