Input Addon Developers

From MozillaWiki
Revision as of 22:20, 24 August 2011 by Adesai (talk | contribs) (Created page with "{{FeatureStatus |Feature name=Input for Addons Developers |Feature stage=Feature Inbox |Feature status=In progress |Feature health=OK }} {{FeatureTeam |Feature product manager=Aa...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Please use "Edit with form" above to edit this page.

Status

Input for Addons Developers
Stage Feature Inbox
Status In progress
Release target `
Health OK
Status note `

{{#set:Feature name=Input for Addons Developers

|Feature stage=Feature Inbox |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=` }}

Team

Product manager Aakash Desai
Directly Responsible Individual Aakash Desai
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Aakash Desai

|Feature feature manager=Aakash Desai |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

input.mozilla.com allows Firefox users to submit feedback for the browser, but not for the rest of their browsing experience (i.e. Add-ons). What we've seen over the past year on input.mozilla.com are the following:

1. Users do submit feedback about add-on compatibility issues as they see them on any build of Firefox. 2. Users do submit feedback about add-on functionality issues as they see them on any build of Firefox.

Further, AMO does not offer an in-product feedback service for add-ons developers who do want feedback. For a feature like Input that is already in product and easy to use, a fit between the two makes sense.

2. Users & use cases

  • End-users will be able to submit feedback about compatibility and functionality of their add-on.
  • Add-ons developers, who check that they want feedback enabled, will be able to receive anonymous praise, issues and ideas from their userbase straight into their developer hub.

3. Dependencies

  • AMO service calls if feedback is wanted by add-on developer
  • Firefox client developer resources to add the necessary AMO service calls and show the praise/issue/ideas buttons
  • Input's ElasticSearch node location and access information for AMO WebDev to add the data to the Developer Hub in a pretty way.

4. Requirements

Firefox Client

  • If an Add-on Developer has explicitly stated they want to received feedback, the praise/issue/idea buttons should show on their detail view on the add-ons manager.
  • On click of any of these buttons, the corresponding input.mozilla.com/feedback submission page should load with the add-on's name pre-loaded onto the comment field.

input.mozilla.org

  • On submission, the comment should show within Input's main dashboard under the requisite product/version/language/feedback_type.

addons.mozilla.org

  • On submission, the comment should show within the add-on developer's developer hub on AMO.

Non-goals

  • Offer praise/issues/ideas for all add-ons without their knowledge.

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

8. Reviews

Security review

`

Privacy review

`

Localization review

Needs to be contacted

Accessibility

`

Quality Assurance review

Needs to be contacted

Operations review

`

Stage 4: Development

9. Implementation

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=input.mozilla.com allows Firefox users to submit feedback for the browser, but not for the rest of their browsing experience (i.e. Add-ons). What we've seen over the past year on input.mozilla.com are the following:

1. Users do submit feedback about add-on compatibility issues as they see them on any build of Firefox. 2. Users do submit feedback about add-on functionality issues as they see them on any build of Firefox.

Further, AMO does not offer an in-product feedback service for add-ons developers who do want feedback. For a feature like Input that is already in product and easy to use, a fit between the two makes sense. |Feature users and use cases=* End-users will be able to submit feedback about compatibility and functionality of their add-on.

  • Add-ons developers, who check that they want feedback enabled, will be able to receive anonymous praise, issues and ideas from their userbase straight into their developer hub.

|Feature dependencies=* AMO service calls if feedback is wanted by add-on developer

  • Firefox client developer resources to add the necessary AMO service calls and show the praise/issue/ideas buttons
  • Input's ElasticSearch node location and access information for AMO WebDev to add the data to the Developer Hub in a pretty way.

|Feature requirements=Firefox Client

  • If an Add-on Developer has explicitly stated they want to received feedback, the praise/issue/idea buttons should show on their detail view on the add-ons manager.
  • On click of any of these buttons, the corresponding input.mozilla.com/feedback submission page should load with the add-on's name pre-loaded onto the comment field.

input.mozilla.org

  • On submission, the comment should show within Input's main dashboard under the requisite product/version/language/feedback_type.

addons.mozilla.org

  • On submission, the comment should show within the add-on developer's developer hub on AMO.

|Feature non-goals=* Offer praise/issues/ideas for all add-ons without their knowledge. |Feature functional spec=` |Feature ux design=` |Feature implementation plan=* Extend upon the add-on already created: https://addons.mozilla.org/en-US/firefox/addon/alert-the-developer/ and add an AMO service call to only show the buttons when the feature is specifically enabled by developers. |Feature security review=` |Feature privacy review=` |Feature localization review=Needs to be contacted |Feature accessibility review=` |Feature qa review=Needs to be contacted |Feature operations review=` |Feature implementation notes=* Feedback buttons in Add-ons Manager: https://bugzilla.mozilla.org/show_bug.cgi?id=681794

  • AMO bug link needed

|Feature landing criteria=` }}

Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap User Engagement
Secondary roadmap `
Feature list `
Project `
Engineering team Desktop front-end

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=User Engagement |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=Desktop front-end }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}


Retrieved from "https://wiki.mozilla.org/index.php?title=Input_Addon_Developers&oldid=342917"