Papercuts Proposal

Goals:

Anyone must be able to submit the issues that hurt their daily use of Firefox OS, regardless if the annoyance is user- or developer-facing, or is an enhancement, defect or poor performance.
The Product team must be able to identify a subset of those issues as higher priority than the rest.
The high priority papercuts should be used as contribution opportunities for onboarding partners and volunteer contributors.
The engineers should expand their role to include the stewardship of contributions, allowing the output of the project to scale beyond individual employees, in a way that mitigates the impact on short-term core code delivery.

Proposal:

Add a new keyword "papercut" to Bugzilla.
Product team will triage issues with the "papercut" keyword regularly, changing the priority field to P1 for the items they deem important.
All high priority papercut issues must have an engineering mentor, assigned during functional team triage sessions.

Implementation:

Propose to Eng Managers, UX, EPMs and PMs (maybe we need a "b2g-feature-drivers" list, release drivers is just too big for stuff like this now!)
File bug to get "papercut" keyword added to Bugzilla.
Product team schedules triage of bugs with keyword "papercut".
Dev engagement team trains each functional team on the Mentored Bugs program.
Functional teams add papercut bug triage to their pre-existing weekly triage sessions.
Communication: Email dev-gaia, dev-b2g, and announce at Gaia weekly meeting and weekly Mozilla project meeting.

Measuring success (each 12 week release cycle):

Track percentage of high priority papercuts have mentors
Track percentage of the employed team were mentors
Track percentage papercut bugs fixed by non-employees, and whether mentored or not

FxOS Dashboards