640233 - Allow more than three versions/channels to be displayed on front page

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[Robert Kaiser]

With the new development model upcoming, we might need to display data of multiple channels on the crash-stats front page - even right now, we are already omitting FF 3.5 there (though that's lower priority, of course).

Allowing more than 3 channels on the front page will definitely need some UI work and concepts of how to present them.

Comment 1

[Laura Thomson :laura]

We talked about this briefly in this week's Socorro meeting.    Some questions:
- I'm assuming we'll want all four of the channels on the home page?
- (Tangential but important) How will we detect each of the four channels from the version?  (We already know pre is nightlies, b is beta, etc). 
- Should the homepage default to showing the newest release in each channel?  
- I'd like to get rid of expiry dates for releases, too.

Going to cc chowse for his feedback and possibly a mock of how we might do this without becoming too crowded.

Comment 2

[Chris Howse [:chowse]]

If we're only showing 4 channels (nightly, experimental, beta, release), this may not require significant changes:

* Showing 4 data series on the chart shouldn't be too overwhelming. If one
  data series happens to dominate, or the data series tend to overlap too much,
  we can make their display toggleable (see
  http://people.iola.dk/olau/flot/examples/turning-series.html)

* While it's starting to get a little cramped, I don't think 4 columns in
  the Top Crasher block is too much. If this truncates the signatures too 
  much, there are a few workarounds:

  * Layout out the channels in a 2x2 grid. This risks pushing the lower 2
    channels below the fold, which defeats the readability.

  * Make each column into a horizontal sliding panel. At any given moment,
    only a single column is shown, with the remainder being 'collapsed'.
    Moving the mouse over a column causes it to expand and the others to
    collapse (imagine http://nclud.com/ but with less cover flow). This hides
    information, but it makes it easier to switch to the channel you want.

  * Show 2 columns at a time, but make the panel scrollable horizontally.

Comment 3

[chris hofmann]

I think there will be the need for more than 4 channels.

There are 4 channels as part of the "normal" development cycle, but we will continue to have maintainence projects going on as well.

By the end of 3 or 4 months we will need easy navigation to do analysis on

  -- mozilla-central (thing on the way to becoming firefox 8
  -- experimental (thing on the way to becoming firefox 7)
  -- beta (thing on the way to becoming firefox 6)
    --- (maybe a second beta if the first one didn't go well)
  -- final RC(s)
  --  firefox 5 (in use by 10's of millions)

  -- firefox 3.6.x (still in maintenence mode)

  and hopefully 3.5.x will be retired by then.


The summary of the top crash list that are on the home page for each releases really isn't useful and I suspect that  some analysis of the web logs would show that no one navigates to the individual lists of crashes from that page.

this is a good opportunity to confirm that,and  get rid of those summaries.

Comment 4

[Chris Howse [:chowse]]

Attachment: 5-Channel Front Page Mock-up

Based on comment #3 and a talk with Rob Kaiser earlier today, it looks people aren't finding the top crash list useful, and it makes it harder to get directly to the reports they want.

I've attached an updated version of the front-page which replaces those lists with links to the most frequently used reports for each channel. This design assumes 5 active channels (nightly, aurora, beta, release, previous release), but could accommodate more with some changes (at the expense of clutter).

This is a short-term change to have something functional for the new releases. If you notice any missing or incorrect details in this design, let me know before this goes to development. If you have any suggestions on what would be useful to you for a landing page, please email those to me. Laura has provided me with the workflows put together during the all-hands, and I'm digging into those now.

Comment 5

[Chris Howse [:chowse]]

Oh, and to clarify: the colors of the headings will match up with the lines in the Crashes/ADU graph.

Comment 6

[chris hofmann]

yeah, this looks nice and is heading in the right direction.  basically we want the home page to be this kind of navigation to an increasing number of reports that look at the data in different ways, and the new release cycle requires that we will have more release channels to look at.  so basically its a race to figure out which axis of the matrix will grow fastest :-)   

I'm hoping the report axis of the matrix will grow faster as we start to produce all kind of iteresting ways to look at the data.  so maybe having a listing of the reports on the left makes sense then just links to the releases to fill out the matrix would condense the space used and redundancy.

That might look something like

                        Nightly    Aurrora   Beta   Final  Maint1 Maint2 Maint
Top Crashers             7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Top Changers             7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Top Plugins              7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Top Crashes by URL       7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Top Crashes by Domain    7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Top Crashes by Top Site  7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Module Analysis          7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Addon Analysis           7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Malware Analysis         7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Release Comparison Rpt   7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
Frankenbuild Report      7.0a1      6.0a2    5.0    4.0.1   4.0   3.6.15 3.5.4
...
...
...

Comment 7

[Laura Thomson :laura]

+1 for what chofmann says.  (Switching columns and rows)

Comment 9

[Chris Howse [:chowse]]

Attachment: Landing Page Concept (Short Term)

OK, here are two concepts to handle the growth of reports and releases:

SHORT TERM

* Remove the ADU/user chart.

* Provide a grid of releases and their related reports, with the 4 release
  channels on the top row and maintenance releases on the following rows.

* Use a few interaction heuristics to make it easy to spot out a release first,
  and then hone in on the most common reports.

This design should be pretty easy to implement, and should still be usable for <12 releases and <10 reports.

Comment 10

[Chris Howse [:chowse]]

Attachment: Landing Page Concept (Longer Term)

LONGER TERM

* Move the choice of release into a bar on the left. Only show reports for
  the selected release. Using a cookie, the last selected release could be
  remembered across page visits.

* Break the list of reports into sensible groups.

Comment 11

[Robert Kaiser]

(In reply to comment #9)
> * Remove the ADU/user chart.

Ugh, we are actually looking at that one and really want to see it...

Comment 12

[Chris Howse [:chowse]]

Attachment: Landing Page Concept (Short Term 2)

Landing with ADU returned. Also, laying versions out in columns associated w/ their channel.

Comment 13

[Robert Kaiser]

(In reply to comment #12)
> Created attachment 526418 [details]
> Landing Page Concept (Short Term 2)

I like that one!

Comment 14

[Laura Thomson :laura]

lonnen is going to implement the last mock.

Comment 15

[Lonnen :lonnen]

Attachment: (v1) implement the mock

Here's a patch that implements the mock with some minor revisions discussed with Chowse and Laura outside of IRC.

Comment 16

[Lonnen :lonnen]

(In reply to comment #15)
> Created attachment 528163 [details] [diff] [review]
> (v1) implement the mock
> 
> Here's a patch that implements the mock with some minor revisions discussed
> with Chowse and Laura outside of IRC.

err. outside of bugzilla. Specifically, they were to leave the dates where they are instead of moving them inside the cashes panel, and allowing the user to choose up to 4 versions in the admin panel to display, instead of using the channels.

Comment 17

[Lonnen :lonnen]

Attachment: (v1.1) implement the mock

The previous patch got mangled somewhere, so I remade it.

Comment 18

[Robert Helmer [:rhelmer]]

Comment on attachment 528163 [details] [diff] [review]
(v1) implement the mock

>Index: application/controllers/admin.php
>===================================================================
>--- application/controllers/admin.php        (revision 3104)
>+++ application/controllers/admin.php        (working copy)
>@@ -92,8 +92,8 @@
>             (isset($_POST['update_featured']) && $_POST['update_featured'] == 't')
>         ) {
>             $featured = 't';
>-            if ($this->branch_model->getFeaturedVersionsExcludingVersionCount($product, $version) >= 3) {
>-                client::messageSend("There are already 3 featured versions of this product. Set 1 of the featured products to not be featured, then try again.", E_USER_WARNING);
>+            if ($this->branch_model->getFeaturedVersioneExcludingVersionCount($product, $version) >= 4) {
>+                client::messageSend("There are already 4 featured versions of this product. Set 1 of the featured products to not be featured, then try again.", E_USER_WARNING);
>                 $featured = 'f';
>             }
>         }


s/Versione/Versions/


>Index: js/socorro/dashboard.js
>===================================================================
>--- js/socorro/dashboard.js        (revision 3104)
>+++ js/socorro/dashboard.js        (working copy)
>@@ -1,33 +1,7 @@

(...)

>+  var colors = chartOpts['colors'];
>+  $('h4').each(function(){
>+    $(this).css('color',colors.shift())
>+  })  
> });

>Index: js/socorro/daily.js
>===================================================================
>--- js/socorro/daily.js        (revision 3104)
>+++ js/socorro/daily.js        (working copy)
>@@ -1,5 +1,6 @@
>+var chartOpts;
> $(document).ready(function() {
>-  var chartOpts = {
>+  chartOpts = {

Hmm so dashboard.js depends on daily.js being executed first, right? Could there be cases where that wouldn't happen (thinking of http://hsivonen.iki.fi/script-execution/)?

Comment 19

[Robert Helmer [:rhelmer]]

(In reply to comment #18)
> Comment on http://hsivonen.iki.fi/script-execution/
(...)
> Hmm so dashboard.js depends on daily.js being executed first, right? Could
> there be cases where that wouldn't happen (thinking of
> attachment 528163 [details] [diff] [review])?

This might be a bug from the bugzilla 4.0 upgrade.. above is supposed to say "thinking of http://hsivonen.iki.fi/script-execution/" and the comment is on attachment 528163 [details] [diff] [review]. See if this comment works :)

Comment 20

[Robert Helmer [:rhelmer]]

(In reply to comment #19)
> (In reply to comment #18)
> > Comment on attachment 528163 [details] [diff] [review]
> (...)
> > Hmm so dashboard.js depends on daily.js being executed first, right? Could
> > there be cases where that wouldn't happen (thinking of
> > http://hsivonen.iki.fi/script-execution/)?
> 
> This might be a bug from the bugzilla 4.0 upgrade.. above is supposed to say
> "thinking of attachment 528163 [details] [diff] [review]" and the comment is on
> http://hsivonen.iki.fi/script-execution/. See if this comment works :)

OK bugzilla is doing the wrong thing above ^ somehow it's reversing those links, going to track that down elsewhere. Sorry for any confusion.

Comment 21

[Robert Helmer [:rhelmer]]

(In reply to comment #20)
> OK bugzilla is doing the wrong thing above ^ somehow it's reversing those
> links, going to track that down elsewhere. Sorry for any confusion.

BTW this is bug 652663, I'll stop commenting about this here now.

Comment 22

[Lonnen :lonnen]

I don't think it will be a problem. The behavior change noted in that post is related to script tags dynamically inserted into the dom with JS. The scripts affected in the patch are in the page when it is loaded, and so will run in order. They both add jquery onready listeners, but those will fire in the order added.

Comment 23

[Robert Helmer [:rhelmer]]

Comment on attachment 528199 [details] [diff] [review]
(v1.1) implement the mock

Looks good to me, r+ with the s/Versione/Versions/ in admin.php fixed.

Comment 24

[Lonnen :lonnen]

Attachment: v2 fixed: spelling mistake

Fixed that spelling error.

Comment 25

[Lonnen :lonnen]

Fixed in 3112