|Status note||The F1 add-on has been rewritten and released as an alpha on AMO. It uses client side OAuth and the OWA APIs for long-tail support. Desktop team is finalizing the requirements for this feature and will work with Engineering to kick-off this work in the coming weeks.|
|Product manager||Chris Lee|
|Directly Responsible Individual||Chris Lee|
|Lead engineer||Dietrich Ayala / Davd Dahl|
|Security lead||Curtis Koenig, Yvan Boily, Daniel Veditz, Sid Stamm, David Chan, Lucas Adamski, Pete Fritchman|
|Privacy lead||Sid Stamm|
|QA lead||Aaron Train, Paul Silaghi|
|UX lead||Stephen Horlander|
|Product marketing lead||`|
|Additional members||Shane Caraveo|
Work to build Share on top of OWA and Web Activities is largely complete. Further work towards feature completion is in progress and Product is working with the Firefox Engineering to plan out a schedule for integration.
This work is scheduled for 2H12.
Stage 1: Definition
1. Feature overview
This is the bare minimum pieces needed to use the F1 share feature built into Firefox with a single working account.
- Updated requirements (Q1'12)
- Use the iframe from each given service (FB, Twitter, etc.)
- Link sharing with commenting for most services
- Shift from current implementation
- Improved confirmation so users know the link was sent/submitted (this may be taken care of by the service)
- UX recommendations needed
- We will support email services and hook it up to "send link" which maps to the default mailto: service
- Create a new "share" icon
- UX recommendations needed
2. Users & use cases
- See F1 Use Cases
- Simplify the sharing system away from cut & paste of links
- Improve the problem of choice of services for both the producer and sharer by creating user preferences built into the choice
- Twitter Account bug 647578
- F1 Name & Copy bug 648892 - "Share"
- Icon bug 648894
We are not developing all accounts at once, the rewritten Share addon currently only supports Twitter, Facebook and GMail, though long-tail support is possible with OWA.
Stage 2: Design
5. Functional specification
This is the addition of another share account to the working share feature, creating 2 working account types.
6. User experience design
Stage 3: Planning
7. Implementation plan
A third share account to the working share feature, creating 3 working account types.
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteriaShare feature integrated into Firefox, possibly using an add-on approach
- 3 working accounts of types Twitter, Facebook, and Email
Priority P2 Rank 1 Theme / Goal ` Roadmap Sharing Secondary roadmap ` Feature list Desktop Project ` Engineering team Desktop front-end
Team status notes
status notes Products ` ` Engineering ` ` Security sec-review-complete Notes Privacy priv-review-complete Privacy Review Localization ` ` Accessibility ` ` Quality assurance ` ` User experience ` ` Product marketing ` ` Operations ` `