Firefox/Input: Difference between revisions

Revision as of 18:54, 1 July 2014

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

Product Manager: Matt Grimes (:Matt_G)
Project Manager, architect, dev, QA, deployer: Will Kahn-Greene (:willkg), Ricky Rosario (:r1cky)
Dev (Product-embedded Input feedback forms): Firefox for Android: :margaret, Firefox OS: Larissa Co, Firefox Desktop: Gregg Lind

Input development happens on IRC in #input on irc.mozilla.org

Project details

code: https://github.com/mozilla/fjord
code docs: https://fjord.readthedocs.org/
public mailing list: https://mail.mozilla.org/listinfo/input-dev
IRC: #input on irc.mozilla.org
sprints: https://sumo-ernest.herokuapp.com/project/input
bugs: bugs are in the Input product. Create a new bug

Mission

Goals

Become the primary feedback mechanism for Mozilla products.
Find solutions to specified user feedback needs to make Mozilla's products better.
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

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

Search syntax

Input has several places where you can specify a search query. These queries use the following syntax:

+ signifies AND operation
| signifies OR operation
- negates a single token
" wraps a number of tokens to signify a phrase for searching
* at the end of a term signifies a prefix query
( and ) signify precedence

Examples:

crash - searches for responses with the word "crash"
crash + -sync - searches for responses with the word "crash" excluding results with the word "sync"
crash + sync - searches for responses with both "crash" and "sync"
"norton antivirus" crash - searches for responses with the phrase "norton antivirus" and the word "crash"

Feedback URLs

Generic url

https://input.mozilla.org/feedback - Input will guess the locale based on HTTP headers and the product based on the user agent
https://input.mozilla.org/%LOCALE%/feedback - Input will guess the product based on the user agent

Product urls

https://input.mozilla.org/%LOCALE%/feedback/%PRODUCT%/%VERSION%/ - Feedback for specified product, version and locale

For example:

Source/Campaign

If you're writing an email, blog post, tweet, whatever and link to Input feedback form, you should specify the utm_source and utm_campaign querystring parameters. For example:

   https://input.mozilla.org/feedback/firefox?utm_source=wiki&utm_campaign=wiki_example

@@ Line 14: / Line 14: @@
 * '''code docs:''' https://fjord.readthedocs.org/
 * '''public mailing list:''' https://mail.mozilla.org/listinfo/input-dev
+* '''IRC:''' #input on irc.mozilla.org
 * '''sprints:''' https://sumo-ernest.herokuapp.com/project/input
 * '''bugs:''' 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]