Firefox/Input/Needs: Difference between revisions

From MozillaWiki
< Firefox‎ | Input
Jump to navigation Jump to search
(Created page with 'LegNeato, Beltzner and Stuart * stuart: help users and make our products better (feature requests, bug reports, undiscoverable features) * LegNeato: For betas, we want different …')
 
No edit summary
 
Line 8: Line 8:
* behavior, demographics, feature feedback, grow user base
* behavior, demographics, feature feedback, grow user base
* ex. "What addons do you use more often?", "What are your most used features in firefox?", "Want to follow us more? Join one of our mailinglists"
* ex. "What addons do you use more often?", "What are your most used features in firefox?", "Want to follow us more? Join one of our mailinglists"
Metrics
* '''Unidentified'''
Labs
Labs
* user usage data to analyze and offer to proposees (usually labs and ux)
* user usage data to analyze and offer to proposees (usually labs and ux)

Latest revision as of 00:16, 15 June 2010

LegNeato, Beltzner and Stuart

  • stuart: help users and make our products better (feature requests, bug reports, undiscoverable features)
  • LegNeato: For betas, we want different type of feedback vs normal releases. Generally, we care if a problem happened in the previously released update. That is, regressions are most important.
  • Beltzner: a better way (than bugzilla, hendrix and even reporter) for all users to express a problem; a way for us to communicate to beta users what specific things we're looking for feedback on; and better tools for them to provide it; a way for us to pivot and search through that feedback in a more structured way based on OS, arch, etc; a way for us to get performance metrics and system configuration data from the field

Evangelism

  • Find issues, find broken websites

Marketing

  • behavior, demographics, feature feedback, grow user base
  • ex. "What addons do you use more often?", "What are your most used features in firefox?", "Want to follow us more? Join one of our mailinglists"

Labs

  • user usage data to analyze and offer to proposees (usually labs and ux)

QA

  • learn identifiable issues, collect problems and triage them into bug reports on bugzilla, educate community into becoming more useful testers

Support

  • learn identifiable issues, link people to already defined issues, grow *involved* user base