Confirmed users
134
edits
Identity/BrowserID/Addon: Difference between revisions
no edit summary
Stomlinson (talk | contribs) No edit summary |
Stomlinson (talk | contribs) No edit summary |
||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
|Feature stage=Draft | |Feature stage=Draft | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=Beta in Q4 | |||
|Feature health=OK | |Feature health=OK | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Feature product manager=Dan Mills | |Feature product manager=Dan Mills | ||
| Feature lead engineer=Shane Tomlinson | |Feature lead engineer=Shane Tomlinson | ||
| Feature additional members=Ben Adida | |Feature security lead=Yvan Boily | ||
|Feature privacy lead=Sid Stamm | |||
|Feature qa lead=James Bonacci | |||
|Feature ux lead=Alex Faaborg | |||
|Feature additional members=Ben Adida, Lloyd Hilaiel, Dietrich Ayala, Myk Melez | |||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks= | |Feature open issues and risks=* GitHub Issues - [https://github.com/mozilla/browserid_addon/issues/ GitHub Issues] | ||
* | * Jetpack based addon bundled with Firefox has not been done before. | ||
|Feature overview= | * Jetpack based addons may cause performance penalty. | ||
|Feature users and use cases= | * End to end security review needs done on site, addon, and Jetpack. | ||
* l10n needs to happen on on both the site and addon. | |||
|Feature dependencies=* | * Content in URL bar being driven by content instead of the user or browser. | ||
|Feature requirements=* | * Need to address accessibility concerns | ||
|Feature functional spec=* | |Feature overview=The BrowserID addon is a Jetpack based addon that will be bundled with Firefox to provide an in-browser experience for using BrowserID as well as showing user's authentication status in the browser URL bar for sites that support the Sessions API [https://wiki.mozilla.org/Identity/Verified_Email_Protocol/Latest-Session Sessions API] | ||
|Feature ux design= | |Feature users and use cases=All Firefox users who use BrowserID. This addon provides an in-browser experience for using BrowserID, making phishing and spoofing of the BrowserID site much more difficult. | ||
|Feature implementation plan=* | |Feature dependencies=* Jetpack Addon-SDK [https://addons.mozilla.org/en-US/developers/docs/sdk/1.1/ Jetpack SDK] - [https://wiki.mozilla.org/Identity/BrowserID/Addon/JetpackDependencies List of Jetpack Dependencies] | ||
* BrowserID [https://browserid.org BrowserID] | |||
|Feature requirements=* | |||
|Feature functional spec=* | |||
|Feature ux design=Faaborg's Mockups [http://people.mozilla.com/~faaborg/files/projects/accountManager/# Faaborg's Account Sign In mocks] | |||
|Feature implementation plan=* | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo}} | ||
|Feature | {{FeatureTeamStatus | ||
|Feature products status=Signing into the browser concept needs revisited to ensure it matches user expectations. | |||
|Feature engineering status=Lots of work to be done yet. | |||
|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. | |||
* 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. | |||
|Feature security status=sec-review-needed | |||
|Feature security health=Assigned | |||
|Feature security notes=sstamm | |||
|Feature localization status=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 notes=We need to start a QA and test plan. | |||
}} | }} | ||