Extension Manager:Projects:Embedded Add-on Preferences: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (clearing in prep for migration to new feature page format)
mNo edit summary
Line 1: Line 1:
{{FeatureStatus
|Feature name=Simple options for add-ons embedded in the main UI
|Feature stage=Landed
|Feature version=Firefox 7
|Feature health=OK
}}
{{FeatureTeam
|Feature feature manager=Dave Townsend
|Feature lead engineer=Geoff Lankow
|Feature qa lead=Henrik Skupin
|Feature ux lead=Jennifer Boriss
|Feature additional members=Mossop, mfinkle (available reviewers)
}}
{{FeaturePageBody
|Feature overview=Add-on developers should be able to create a series of simple preference options that can be embedded in the detail view of their add-on similar to mobile.


* Documentation: [https://developer.mozilla.org/en/Extensions/Inline_Options Developer documentation] on MDC
|Feature users and use cases=* Display preferences in the add-on's detail view
* Expose this to normal add-ons and add-ons developed through the SDK
|Feature requirements=* Developed UI must pass UI review
* Feature should be covered by automated tests
|Feature non-goals=* Remove the need or support of full add-on preferences dialogs
|Feature implementation notes=* {{bug|653637}}
}}
{{FeatureInfo
|Feature priority=P1
|Feature roadmap=Add-ons
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}

Revision as of 20:06, 8 July 2011

Please use "Edit with form" above to edit this page.

Status

Simple options for add-ons embedded in the main UI
Stage Landed
Status `
Release target Firefox 7
Health OK
Status note `

{{#set:Feature name=Simple options for add-ons embedded in the main UI

|Feature stage=Landed |Feature status=` |Feature version=Firefox 7 |Feature health=OK |Feature status note=` }}

Team

Product manager `
Directly Responsible Individual Dave Townsend
Lead engineer Geoff Lankow
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Henrik Skupin
UX lead Jennifer Boriss
Product marketing lead `
Operations lead `
Additional members Mossop, mfinkle (available reviewers)

{{#set:Feature product manager=`

|Feature feature manager=Dave Townsend |Feature lead engineer=Geoff Lankow |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Henrik Skupin |Feature ux lead=Jennifer Boriss |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Mossop, mfinkle (available reviewers) }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Add-on developers should be able to create a series of simple preference options that can be embedded in the detail view of their add-on similar to mobile.

2. Users & use cases

  • Display preferences in the add-on's detail view
  • Expose this to normal add-ons and add-ons developed through the SDK

3. Dependencies

`

4. Requirements

  • Developed UI must pass UI review
  • Feature should be covered by automated tests

Non-goals

  • Remove the need or support of full add-on preferences dialogs

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=Add-on developers should be able to create a series of simple preference options that can be embedded in the detail view of their add-on similar to mobile.

|Feature users and use cases=* Display preferences in the add-on's detail view

  • Expose this to normal add-ons and add-ons developed through the SDK

|Feature dependencies=` |Feature requirements=* Developed UI must pass UI review

  • Feature should be covered by automated tests

|Feature non-goals=* Remove the need or support of full add-on preferences dialogs |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* bug 653637 |Feature landing criteria=` }}

Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap Add-ons
Secondary roadmap `
Feature list Desktop
Project `
Engineering team Desktop front-end

{{#set:Feature priority=P1

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

Team status notes

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

{{#set:Feature products status=tbd

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


Retrieved from "https://wiki.allizom.org/index.php?title=Extension_Manager:Projects:Embedded_Add-on_Preferences&oldid=326907"