Firefox/Input: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Projects in the planning stage: add 12 Factor App project)
(→‎Projects and Roadmap: updating roadmap)
Line 52: Line 52:
=== Projects in the planning stage ===
=== Projects in the planning stage ===


* 2015q1?: [[Firefox/Input/12 Factor App|12 Factor App]]
* 2015q1?: Thank you page overhaul
* 2015q1?: Thank you page overhaul
* 2015q1?: Infrastructure for supporting contributors
* 2015q1?: Infrastructure for supporting contributors
Line 60: Line 59:
=== In progress projects ===
=== In progress projects ===


* 2014q4: [[Firefox/Input/Feedback form overhaul|Feedback form overhaul]]
* 2014q4: [[Firefox/Input/Multiple Products|Multiple Products]]
* 2014q4: [[Firefox/Input/Support aboutsupport|Support aboutsupport]]
* 2014q4: [[Firefox/Input/Support aboutsupport|Support aboutsupport]]
* 2014q4: [[Firefox/Input/Gradient Sentiment|Gradient Sentiment]]
 
* 2014q4: [[Firefox/Input/Heartbeat|Heartbeat v2]]
* 2015q1: [[Firefox/Input/12 Factor App|12 Factor App]]
* 2015q1: [[Firefox/Input/Gradient Sentiment|Gradient Sentiment]]


=== On-hold projects ===
=== On-hold projects ===
Line 74: Line 72:
* 2014q3: [[Firefox/Input/Reduce Contributor Pain|Reduce Contributor Pain v1]]
* 2014q3: [[Firefox/Input/Reduce Contributor Pain|Reduce Contributor Pain v1]]
* 2014q3: [[Firefox/Input/Dashboards for Everyone|Dashboards for Everyone v1]]
* 2014q3: [[Firefox/Input/Dashboards for Everyone|Dashboards for Everyone v1]]
* 2014q4: [[Firefox/Input/Feedback form overhaul|Feedback form overhaul]]
* 2014q4: [[Firefox/Input/Multiple Products|Multiple Products]]
* 2014q4: [[Firefox/Input/Heartbeat|Heartbeat v2]]


=== Abandoned projects ===
=== Abandoned projects ===


* Product Dashboards -- abandoned because User Advocacy is building dashboards that pull from Input and other sources and they're better equipped to build and maintain them
* Product Dashboards -- abandoned because User Advocacy is building dashboards that pull from Input and other sources and they're better equipped to build and maintain them

Revision as of 16:28, 16 December 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

Interested in contributing to Input? Get Involved!

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 and using feedback should be in accordance with Mozilla's privacy policies.

Using Input

Projects and Roadmap

Projects in the planning stage

  • 2015q1?: Thank you page overhaul
  • 2015q1?: Infrastructure for supporting contributors
  • 2015q1?: Input Site Style Overhaul
  • 2015q1?: Reduce the abuse

In progress projects

On-hold projects

Completed projects

Abandoned projects

  • Product Dashboards -- abandoned because User Advocacy is building dashboards that pull from Input and other sources and they're better equipped to build and maintain them