Labs/F1/Feature Blocks/F1

< Labs‎ | F1
Revision as of 18:45, 12 April 2011 by Clarkbw (talk | contribs) (Created page with "{| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; backgro...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Feature Status ETA Owner
Sharing Roadmap is set. 2 open issues. Barely enough time. 2011-04-21 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
  • Etc.

Team list should make it clear who to ask about what, and who to ping when they're needed. If you do not need someone in a particular role (ie: Security), that's fine, just delete that line.

Release Requirements

Complete checklist of items that need to be satisfied before we can call this feature "done"


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

  1. Can the Firefox Sharing Preferences continue to use a web based interface?
  2. Using web content in a Panel bug 649144

Related Bugs & Dependencies


Designs


Test Plans

TODO

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

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.