Features/Desktop/IdentityIntegration: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "{{FeatureStatus |Feature name=Identity Integration |Feature stage=Draft |Feature health=OK }} {{FeatureTeam |Feature product manager=Dan Mills |Feature feature manager=Dietrich A...")
 
No edit summary
Line 2: Line 2:
|Feature name=Identity Integration
|Feature name=Identity Integration
|Feature stage=Draft
|Feature stage=Draft
|Feature status=In progress
|Feature version=Firefox 10
|Feature health=OK
|Feature health=OK
|Feature status note=planning, requirements gathering
}}
}}
{{FeatureTeam
{{FeatureTeam
Line 9: Line 12:
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature open issues and risks=Jetpack performance and unit test results are unknown. Jetpack localization API is not implemented yet.
|Feature overview=Ship the Identity features as a Jetpack-based add-on bundled with Firefox Nightly by the end of the year.
|Feature overview=Ship the Identity features as a Jetpack-based add-on bundled with Firefox Nightly by the end of the year.
|Feature users and use cases=This is an experimental approach to new feature development in the browser.
|Feature users and use cases=This is an experimental approach to new feature development in the browser.
|Feature dependencies=* Jetpack localization API
|Feature dependencies=* Jetpack localization API
* Infrastructure for running unit tests bundled with add-ons
* Infrastructure for running unit tests bundled with add-ons
|Feature requirements=Integrate the Identity features in Firefox itself.
|Feature non-goals=* Ship Jetpack runtime inside the Firefox core
|Feature non-goals=* Ship Jetpack runtime inside the Firefox core
* Ship the Identity features inside the Firefox core
* Ship the Identity features inside the Firefox core
|Feature implementation plan=More detail once scope of work is determined, but this is the high-level plan:
* Acquire a project branch to work on
* Bundle add-on with Firefox, check into project branch
* Determine the delta from a landable state (perf, unit tests, etc)
* Scope work required to get to landable state (file bugs, get estimates)
* Re-evaluate feasibility
* Coordinate work between Identity, Firefox, Jetpack and Platform teams to get to landable state
}}
}}
{{FeatureInfo
{{FeatureInfo

Revision as of 23:05, 16 August 2011

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

Status

Identity Integration
Stage Draft
Status In progress
Release target Firefox 10
Health OK
Status note planning, requirements gathering

{{#set:Feature name=Identity Integration

|Feature stage=Draft |Feature status=In progress |Feature version=Firefox 10 |Feature health=OK |Feature status note=planning, requirements gathering }}

Team

Product manager Dan Mills
Directly Responsible Individual Dietrich Ayala
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=Dan Mills

|Feature feature manager=Dietrich Ayala |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

Jetpack performance and unit test results are unknown. Jetpack localization API is not implemented yet.

Stage 1: Definition

1. Feature overview

Ship the Identity features as a Jetpack-based add-on bundled with Firefox Nightly by the end of the year.

2. Users & use cases

This is an experimental approach to new feature development in the browser.

3. Dependencies

  • Jetpack localization API
  • Infrastructure for running unit tests bundled with add-ons

4. Requirements

Integrate the Identity features in Firefox itself.

Non-goals

  • Ship Jetpack runtime inside the Firefox core
  • Ship the Identity features inside the Firefox core

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

More detail once scope of work is determined, but this is the high-level plan:

  • Acquire a project branch to work on
  • Bundle add-on with Firefox, check into project branch
  • Determine the delta from a landable state (perf, unit tests, etc)
  • Scope work required to get to landable state (file bugs, get estimates)
  • Re-evaluate feasibility
  • Coordinate work between Identity, Firefox, Jetpack and Platform teams to get to landable state

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=Jetpack performance and unit test results are unknown. Jetpack localization API is not implemented yet. |Feature overview=Ship the Identity features as a Jetpack-based add-on bundled with Firefox Nightly by the end of the year. |Feature users and use cases=This is an experimental approach to new feature development in the browser. |Feature dependencies=* Jetpack localization API

  • Infrastructure for running unit tests bundled with add-ons

|Feature requirements=Integrate the Identity features in Firefox itself. |Feature non-goals=* Ship Jetpack runtime inside the Firefox core

  • Ship the Identity features inside the Firefox core

|Feature functional spec=` |Feature ux design=` |Feature implementation plan=More detail once scope of work is determined, but this is the high-level plan:

  • Acquire a project branch to work on
  • Bundle add-on with Firefox, check into project branch
  • Determine the delta from a landable state (perf, unit tests, etc)
  • Scope work required to get to landable state (file bugs, get estimates)
  • Re-evaluate feasibility
  • Coordinate work between Identity, Firefox, Jetpack and Platform teams to get to landable state

|Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap `
Secondary roadmap `
Feature list `
Project `
Engineering team `

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}

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=` }}