Labs/F1/Feature Blocks/F1

From MozillaWiki
< Labs‎ | F1
Jump to navigation Jump to search
Feature Status ETA Owner
F1/Mozilla Share Roadmap set. 2 Open Issues related to Panel and Preferences implemented in HTML. Server on track, getting ready for Ops.

SDR: P || SIR: P

2011-05-12 Bryan Clark

Summary

This is the bare minimum pieces needed to use the F1 share feature built into Firefox with a single working account.

Team

Who's working on this?

  • Feature Manager: Bryan Clark
  • Developers: James Burke, Shane Caraveo, Philipp von Weitershausen, Tarek Ziadé
  • Product Manager: Bryan Clark
  • QA:
  • UX: Stephen Horlander, Alex Faaborg
  • Security: Curtis Koenig, Yvan Boily, Daniel Veditz, Sid Stamm, David Chan, Lucas Adamski, Pete Fritchman

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done"
Feature Status ETA Owner
F1 Preferences/Account Settings Preferences pane landed, blocked on bug 653002 for OS styling 2011-05-05 Bryan Clark
F1 Twitter Account Initial prototype. Blocked on staging server running bug 650900 and bug 653002 for OS styling. 2011-04-27 Bryan Clark


Next Steps

in no order
  • Settle the Firefox Preferences technical question
  • Settle the Panel IFRAME technical question
  • Finalize the UX of the Preferences
  • Finalize the UX of the Twitter Account
  • Implement the Panel UX changes


Open Issues

Related Bugs & Dependencies


Designs


Test Plans

TODO

Any and all test plans and strategies. Either inline or linked to.

Security

  • Security reviews currently underway

Goals/Use Cases

See F1 Use Cases
  • Create a trusted service users can use to share pages with their services
  • Simplify the sharing system away from cut & paste of links
  • Work against the problem of choice of services for both the producer and sharer

Non-Goals

We are not developing all accounts at once, this feature set will be less than what is currently available in the F1 add-on.

Legend

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.