Identity/BrowserID/Addon: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(A big update to fill in lots of the initial pieces.)
Line 4: Line 4:
|Feature status=In progress
|Feature status=In progress
|Feature health=OK
|Feature health=OK
|Feature version=Beta in Q4
}}
}}
{{FeatureTeam
{{FeatureTeam
Line 22: Line 24:
* l10n needs to happen on on both the site and addon.
* l10n needs to happen on on both the site and addon.
* Content in URL bar being driven by content instead of the user or browser.
* Content in URL bar being driven by content instead of the user or browser.
* Need to address accessibility concerns
|Feature overview=*
|Feature overview=*
|Feature users and use cases=*
|Feature users and use cases=*
Line 29: Line 32:
|Feature requirements=*  
|Feature requirements=*  
|Feature functional spec=*  
|Feature functional spec=*  
|Feature ux design=* Faaborg's Mockups [http://people.mozilla.com/~faaborg/files/projects/accountManager/# Faaborg's Account Sign In mocks]
|Feature ux design=Faaborg's Mockups [http://people.mozilla.com/~faaborg/files/projects/accountManager/# Faaborg's Account Sign In mocks]
|Feature implementation plan=*  
|Feature implementation plan=*  
}}
}}
Line 35: Line 38:
|Feature priority=Q4 Beta Release
|Feature priority=Q4 Beta Release
}}
}}
{{FeatureTeamStatusNotes
{{FeatureTeamStatus
| Feature product status =Signing into the browser concept needs revisited to ensure it matches user expectations.
| Feature products status=Signing into the browser concept needs revisited to ensure it matches user expectations.
| Feature engineering status =  
| Feature engineering status = Lots of work to be done yet.
* An alpha version is available on GitHub at [https://github.com/mozilla/browserid_addon/raw/browserid/addon/dist/browserid_addon.xpi Alpha XPI].
| Feature engineering notes = An alpha version is available on GitHub at [https://github.com/mozilla/browserid_addon/raw/browserid/addon/dist/browserid_addon.xpi Alpha XPI].
* Awaiting performance report from Dietrich.  Initial stats show that bundling the addon incurs a performance penalty, but further review is needed to find out what is due to Jetpack and what is due to BrowserID portion.
* Awaiting performance report from Dietrich.  Initial stats show that bundling the addon incurs a performance penalty, but further review is needed to find out what is due to Jetpack and what is due to BrowserID portion.
* Security review is needed on portions of Jetpack that are going to be used in addon.
* Security review is needed on portions of Jetpack that are going to be used in addon.
* Addon needs fixed to handle opening multiple Firefox windows.
* Addon needs fixed to handle opening multiple Firefox windows.
* Quality and Security Reviews are needed on addon code.
* Quality and Security Reviews are needed on addon code.
| Feature localization status =  
| Feature localization status = l10n ideas have been talked about but nothing concrete.
* l10n ideas have been talked about but nothing concrete.
| Feature accessibility status = Need to make Sign Into the Browser and BrowserID portions accessible
| Feature accessibility notes = Should get Marco and David involved.
| Feature qa status =
| Feature qa notes = We need to start a QA and test plan.
}}
}}

Revision as of 08:33, 4 October 2011

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

Status

BrowserID Addon
Stage Draft
Status In progress
Release target Beta in Q4
Health OK
Status note `

Team

Product manager Dan Mills
Directly Responsible Individual `
Lead engineer Shane Tomlinson
Security lead Sid Stamm
Privacy lead `
Localization lead `
Accessibility lead `
QA lead James Bonacci
UX lead Alex Faaborg
Product marketing lead `
Operations lead `
Additional members Ben Adida, Lloyd Hilaiel, Dietrich Ayala,


Open issues/risks

  • GitHub Issues - GitHub Issues
  • Jetpack based addon bundled with Firefox has not been done before.
  • Jetpack based addons may cause performance penalty.
  • End to end security review needs done on site, addon, and Jetpack.
  • l10n needs to happen on on both the site and addon.
  • Content in URL bar being driven by content instead of the user or browser.
  • Need to address accessibility concerns

Stage 1: Definition

1. Feature overview

2. Users & use cases

3. Dependencies

4. Requirements

Non-goals

`

Stage 2: Design

5. Functional specification

6. User experience design

Faaborg's Mockups Faaborg's Account Sign In mocks

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

`


Feature details

Priority Q4 Beta Release
Rank 999
Theme / Goal `
Roadmap `
Secondary roadmap `
Feature list `
Project `
Engineering team `

"Q4 Beta Release" is not in the list (`, Unprioritized, P1, P2, P3) of allowed values for the "Feature priority" property.

Team status notes

  status notes
Products Signing into the browser concept needs revisited to ensure it matches user expectations. `
Engineering Lots of work to be done yet. An alpha version is available on GitHub at Alpha XPI.
  • Awaiting performance report from Dietrich. Initial stats show that bundling the addon incurs a performance penalty, but further review is needed to find out what is due to Jetpack and what is due to BrowserID portion.
  • Security review is needed on portions of Jetpack that are going to be used in addon.
  • Addon needs fixed to handle opening multiple Firefox windows.
  • Quality and Security Reviews are needed on addon code.
Security ` `
Privacy ` `
Localization l10n ideas have been talked about but nothing concrete. `
Accessibility Need to make Sign Into the Browser and BrowserID portions accessible Should get Marco and David involved.
Quality assurance We need to start a QA and test plan.
User experience ` `
Product marketing ` `
Operations ` `