Firefox/Input: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(minor tweaks)
No edit summary
Line 10: Line 10:


Contact us on IRC via [irc://mozilla.org/%23input #input on irc.mozilla.org]
Contact us on IRC via [irc://mozilla.org/%23input #input on irc.mozilla.org]
== Project details ==
* code: https://github.com/mozilla/fjord
* code docs: http://fjord.readthedocs.org/
* public mailing list: https://mail.mozilla.org/listinfo/input-dev
* sprints: http://scrumbu.gs/projects/input/ (NB: We're not sprinting right now. 2013-03-26)
Bugs are in the '''Input''' product. [https://bugzilla.mozilla.org/enter_bug.cgi?product=Input&rep_platform=all&op_sys=all Create a new bug]


== Mission ==
== Mission ==
Line 32: Line 43:
# Feedback should be fun to write!
# Feedback should be fun to write!
# Collecting feedback should be in accordance with Mozilla's privacy policies.
# Collecting feedback should be in accordance with Mozilla's privacy policies.
== Project details ==
* code: https://github.com/mozilla/fjord
* code docs: http://fjord.readthedocs.org/
* sprints: http://scrumbu.gs/projects/input/
Bugs are in the '''Input''' product. [https://bugzilla.mozilla.org/enter_bug.cgi?product=Input&rep_platform=all&op_sys=all Create a new bug]

Revision as of 16:42, 26 March 2013

The purpose of Firefox Input is to collect actionable feedback from our user base across each channel of our software development process. The application collects feedback and offers a set of analysis methods for looking at the resulting data.

Team

  • PM: Cheng Wang (:cww)
  • Dev (Web Piece): James Socol (:jsocol), Will Kahn-Greene (:willkg)
  • Dev (Client Piece): Android: :margaret, B2G: Larissa Co, Desktop: Gregg Lind
  • QA: TBD
  • Metrics: TBD

Contact us on IRC via #input on irc.mozilla.org


Project details

Bugs are in the Input product. Create a new bug


Mission

Goals

  1. Become the primary feedback mechanism for Mozilla products.
  2. Find solutions to specified user feedback needs to make Mozilla's products better.
  3. Promote the benefits of an open feedback system.

How we want to get to those goals:

  • Provide low-bar submission methods for defined needs from user feedback.
  • Experiment with our data to find new ways to visualize and propagate data (deal with scale inherently).
  • Construct methods to use Input as a feedback loop for QA, localization and marketing.

Principles

  1. Feedback sent to Mozilla should be constructive, direct and actionable.
  2. Feedback should allow drivers to make decisions that deliver a better value proposition to our users.
  3. Submissions should take no more than 5 steps to submit.
  4. Feedback should be fun to write!
  5. Collecting feedback should be in accordance with Mozilla's privacy policies.