Confirmed users
6,300
edits
Firefox/Input/Roadmap/2011: Difference between revisions
→Integrate user feedback into product and community development
| Line 26: | Line 26: | ||
'''Outcomes''' | '''Outcomes''' | ||
# Product Drivers – Input will translate spikes (i.e. 1-2 magnitude’s higher than the average over a version) over specific search terms and URLs into a newly filed bug in Bugzilla. The tool would most likely poll for data over a manually-set list of terms. | |||
# SUMO – Support volunteers will be able to find Input’s clustered opinions that are similar to support thread topics using an easy-to-use button per thread. | |||
# RRRT – Input will offer triagers the option to correlate messages per version within “broken”, “sad” and “ideas” feedback types with Bugzilla bug summaries to find matches. (and possibly increment “votes”). Just like SUMO, crash-stats triagers will be able to correlate messages and URLs per version specific feedback types with comments and URLs in crash-stats’ reports over the same version. | |||
# AMO – Add-ons developers should be able to retrieve feedback for their Add-on’s name over the “happy”, “sad”, “ideas” (release and beta versions) feedback types using a simple “see feedback” button in the Developer Hub. Another option will be to create a running list of top suggestions by users that could be solved by the development of add-ons within AMO. | |||
=== Marry Input with Big Data approaches === | === Marry Input with Big Data approaches === | ||