Closed Bug 623360 Opened 9 years ago Closed 9 years ago
Add a dashboard for "Suggestions" on Major Releases
Major release users can submit suggestions to us in Firefox 4.0. The dashboard to host this information should be much like the themes dashboard on the betas except for a few notable additions: * Version differentiation per Product (i.e. Firefox, Mobile) * Differentiate by Locale
Notes: * The page title: "Popular Ideas". "Common Ideas" seemed a little demeaning, especially if coming right off the feedback page. Perhaps "Frequent Ideas", or something that couldn't be interpreted as speaking to the quality (rather than quantity) of the suggestions? * Like on the main page, only a single locale can be checked. Once it is checked, the remaining choices vanish until it is unchecked. * The navigations choices at the top are "Experience", "Broken Sites", and "Ideas" to reflect the same options on the feedback page. The choices are out of order in the mock-up.
> Perhaps "Frequent Ideas", or something that couldn't be interpreted as speaking to the quality (rather than quantity) of the suggestions? WFM! > Like on the main page, only a single locale can be checked. Once it is checked, the remaining choices vanish until it is unchecked. Dave says this is too hard. So, the locale stuff should be replaced with Platforms using the current buttons that we have on the beta dashboard. > "Experience" That sounds odd and the use of "Trends" in the mock-ups doesn't really work either. Hrm, what about "Ratings" ?
Assignee: chowse → nobody
Target Milestone: 3.1 → 3.3
So we have something to ship with Fx4, I'll make this page basically a copy of the beta themes page, and shove the release data into our existing clustering algorithm. Due to its limited scalability, I'll have to reduce the amount of data we feed the algorithm. Aakash suggested by days, but since the problem size increases directly with the number of opinions (only indirectly with time), I might also just give it an upper bound of opinions.
For the record, we commented out the clustering job which was part of the production push script and made it stall indefinitely instead of creating clusters, then moving on. That means, if clustering needs to be run as part of a push, we need to specifically request it now, otherwise it won't run until the next time the cron job hits -- which I think is every 4 hours.
I added release clustering to the cron job. This adds two more clustering steps and therefore won't be the most performant thing on the planet, but that's what the distributed clustering project is for. r? davedash: http://github.com/fwenzel/reporter/commit/6450b89
Status: NEW → ASSIGNED
Added: http://github.com/fwenzel/reporter/commit/b1ed59d Themes will be empty until it's reclustered.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.