Features/Thunderbird/BigFiles: Difference between revisions
Jbpiacentino (talk | contribs) No edit summary |
Jbpiacentino (talk | contribs) No edit summary |
||
| Line 10: | Line 10: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks=Marketing: | |Feature open issues and risks=Marketing:<br/> | ||
- How to position this feature vs attachment. This is NOT a replacement to file attachment. (see 'Non goals' section below) | - How to position this feature vs attachment. This is NOT a replacement to file attachment. (see 'Non goals' section below)<br/> | ||
- Not all online storage services categories can possibly be addressed in v1. What guiding principles to apply to make a choice ? | - Not all online storage services categories can possibly be addressed in v1. What guiding principles to apply to make a choice ? (do we know the user segment most interested in this ?)<br/> | ||
- Are there differences in different countries ? Some consumer storage providers more popular in some countries ? | - Are there differences in different countries ? Some consumer storage providers more popular in some countries ?<br/> | ||
Use cases: | Use cases:<br/> | ||
- How to deal with offline mode ? | - How to deal with offline mode ?<br/> | ||
- Are there cases where TB should or could delete a file ? | - Are there cases where TB should or could delete a file ?<br/> | ||
- Should the online file make reference to the email that created it ? | - Should the online file make reference to the email that created it ?<br/> | ||
- Some online storage services have file expiration dates (on free accounts). Is it acceptable ? Can the recipients understand there is a limited lifetime to the link ? | - Some online storage services have file expiration dates (on free accounts). Is it acceptable ? Can the recipients understand there is a limited lifetime to the link ?<br/> | ||
- Some providers rely on a synchronization model (Dropbox, Ubuntu one...) vs direct file access (FTP, network drive...). and recommend using an installed synchronization application. Is this a problem ? Is it mandatory (can we use web APIs for TB and let users choose to install the client if they want to ?) | - Some providers rely on a synchronization model (Dropbox, Ubuntu one...) vs direct file access (FTP, network drive...). and recommend using an installed synchronization application. Is this a problem ? Is it mandatory (can we use web APIs for TB and let users choose to install the client if they want to ?) <br/> | ||
- Does the local client helps offline use (sync happens when going online, in the background) ? | - Does the local client helps offline use (sync happens when going online, in the background) ?<br/> | ||
- Recipients must not have to register to the online service provider to have access to the online file. | - Recipients must not have to register to the online service provider to have access to the online file.<br/> | ||
Implementation:<br/> | |||
- Senders should be able to ensure that a big file can only be viewed by the recipients of the email (this should be the default setting). Is this true possible for all providers ?<br/> | |||
- What technology for provider API implementation ? <br/> | |||
- Can this be done through a web app exposing web intents ? Can the web app be local ? <br/> | |||
- Each provider must be supported through an installable provider (web app or add-on), some of which are distributed by default with TB<br/> | |||
- FTP servers are difficult to set up for average users (at least to ensure security & privacy). Can this be offered to an average consumer (probably one of the the reason why online file storage are popular)<br/> | |||
|Feature overview=This Thunderbird feature provides a way to use online storage services to store large size email file attachments. With this feature, email file attachments are replaced by urls pointing to an online file storage server, where the files can be found. | |Feature overview=This Thunderbird feature provides a way to use online storage services to store large size email file attachments. With this feature, email file attachments are replaced by urls pointing to an online file storage server, where the files can be found. | ||
This feature is meant to: | This feature is meant to:<ul> | ||
<li>offer a way to easily share very large files through email</li> | |||
<li>reduce ‘file too big’ bounce email situations</li> | |||
<li>encourage file sharing over copying</li> | |||
<li>save recipients inbox space and eliminate file duplication for multiple recipients</li> | |||
<li>increase attachment sending and receiving speed</li></ul> | |||
A tight and smooth integration with Thunderbird will be required to facilitate usage and adoption of this alternative way of sending a file via email. For example, Thunderbird could propose to use this feature to resend a ‘file-too-big’ bounced email or when sending a file known or likely to be too large for the recipients email domain. On a different idea, on-the-fly setup/signup could also be implemented to ease the first use of the feature. | A tight and smooth integration with Thunderbird will be required to facilitate usage and adoption of this alternative way of sending a file via email. For example, Thunderbird could propose to use this feature to resend a ‘file-too-big’ bounced email or when sending a file known or likely to be too large for the recipients email domain. On a different idea, on-the-fly setup/signup could also be implemented to ease the first use of the feature. | ||
Online storage services can be of different categories: | Online storage services can be of different categories:<ul> | ||
<li>commercial services such as DropBox, YouSendIt, Box.net...</li> | |||
<li>consumer document sharing services such as Google Docs or MS Skydrive,</li> | |||
<li>enterprise document sharing resources such as MS SharePoint, network drives </li> | |||
<li>or more traditional network storage resources such FTP folders, …</li> | |||
</ul> | |||
|Feature users and use cases=- When a user attaches a 'Big File'<br/> | |Feature users and use cases=- When a user attaches a 'Big File'<br/> | ||
If the file is above a certain size, warn the user and offer to use online storage instead of attachment. Note: The size could be an arbitrary value, or set by the user, or even retrieved on the fly by analyzing recipients domains (gmail.com for example has a limit of 25MB). | If the file is above a certain size, warn the user and offer to use online storage instead of attachment. Note: The size could be an arbitrary value, or set by the user, or even retrieved on the fly by analyzing recipients domains (gmail.com for example has a limit of 25MB). | ||
Revision as of 17:42, 25 September 2011
Status
| Feature name here | |
| Stage | Draft |
| Status | ` |
| Release target | Thunderbird 11 or 12 |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Feature name here
|Feature stage=Draft |Feature status=` |Feature version=Thunderbird 11 or 12 |Feature health=OK |Feature status note=` }}
Team
| Product manager | Jb Piacentino |
| Directly Responsible Individual | Jb Piacentino |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Jb Piacentino
|Feature feature manager=Jb Piacentino |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
Marketing:
- How to position this feature vs attachment. This is NOT a replacement to file attachment. (see 'Non goals' section below)
- Not all online storage services categories can possibly be addressed in v1. What guiding principles to apply to make a choice ? (do we know the user segment most interested in this ?)
- Are there differences in different countries ? Some consumer storage providers more popular in some countries ?
Use cases:
- How to deal with offline mode ?
- Are there cases where TB should or could delete a file ?
- Should the online file make reference to the email that created it ?
- Some online storage services have file expiration dates (on free accounts). Is it acceptable ? Can the recipients understand there is a limited lifetime to the link ?
- Some providers rely on a synchronization model (Dropbox, Ubuntu one...) vs direct file access (FTP, network drive...). and recommend using an installed synchronization application. Is this a problem ? Is it mandatory (can we use web APIs for TB and let users choose to install the client if they want to ?)
- Does the local client helps offline use (sync happens when going online, in the background) ?
- Recipients must not have to register to the online service provider to have access to the online file.
Implementation:
- Senders should be able to ensure that a big file can only be viewed by the recipients of the email (this should be the default setting). Is this true possible for all providers ?
- What technology for provider API implementation ?
- Can this be done through a web app exposing web intents ? Can the web app be local ?
- Each provider must be supported through an installable provider (web app or add-on), some of which are distributed by default with TB
- FTP servers are difficult to set up for average users (at least to ensure security & privacy). Can this be offered to an average consumer (probably one of the the reason why online file storage are popular)
Stage 1: Definition
1. Feature overview
This Thunderbird feature provides a way to use online storage services to store large size email file attachments. With this feature, email file attachments are replaced by urls pointing to an online file storage server, where the files can be found.
This feature is meant to:
- offer a way to easily share very large files through email
- reduce ‘file too big’ bounce email situations
- encourage file sharing over copying
- save recipients inbox space and eliminate file duplication for multiple recipients
- increase attachment sending and receiving speed
A tight and smooth integration with Thunderbird will be required to facilitate usage and adoption of this alternative way of sending a file via email. For example, Thunderbird could propose to use this feature to resend a ‘file-too-big’ bounced email or when sending a file known or likely to be too large for the recipients email domain. On a different idea, on-the-fly setup/signup could also be implemented to ease the first use of the feature.
Online storage services can be of different categories:
- commercial services such as DropBox, YouSendIt, Box.net...
- consumer document sharing services such as Google Docs or MS Skydrive,
- enterprise document sharing resources such as MS SharePoint, network drives
- or more traditional network storage resources such FTP folders, …
2. Users & use cases
- When a user attaches a 'Big File'
If the file is above a certain size, warn the user and offer to use online storage instead of attachment. Note: The size could be an arbitrary value, or set by the user, or even retrieved on the fly by analyzing recipients domains (gmail.com for example has a limit of 25MB).
- When an email is bounced
If Thunderbird detects that the bounce reason is a 'File Too Big', offer to resend via BigFile.
- On-the-fly setup/signup
If the user is about to use BigFiles but has not configured TB for it, allow the setup or signup procedure to happen on the fly, in such a way that the user should not have to bother pre-confguring BigFiles before first using it.
A list of pre-configured online storage services should be proposed for setup or signup.
- Quota management
Detect over quota situations (mostly in the case of consumer online storage services free offers) and guide towards resolution (signup for premium service, file deletions...)
- Advanced features - Some consumer online storage services offer document tracking (YouSendIt for example). It might be interesting
3. Dependencies
`
4. Requirements
- APIs access to consumer & professional online storage services
Non-goals
This is not a replacement to file attachment. Care should be taken to make it clear in the UX (for example through a specific UI), whilst facilitating the use of BigFiles when using 'regular' attachments.
Stage 2: Design
5. Functional specification
`
6. User experience design
`
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
`
{{#set:Feature open issues and risks=Marketing:
- How to position this feature vs attachment. This is NOT a replacement to file attachment. (see 'Non goals' section below)
- Not all online storage services categories can possibly be addressed in v1. What guiding principles to apply to make a choice ? (do we know the user segment most interested in this ?)
- Are there differences in different countries ? Some consumer storage providers more popular in some countries ?
Use cases:
- How to deal with offline mode ?
- Are there cases where TB should or could delete a file ?
- Should the online file make reference to the email that created it ?
- Some online storage services have file expiration dates (on free accounts). Is it acceptable ? Can the recipients understand there is a limited lifetime to the link ?
- Some providers rely on a synchronization model (Dropbox, Ubuntu one...) vs direct file access (FTP, network drive...). and recommend using an installed synchronization application. Is this a problem ? Is it mandatory (can we use web APIs for TB and let users choose to install the client if they want to ?)
- Does the local client helps offline use (sync happens when going online, in the background) ?
- Recipients must not have to register to the online service provider to have access to the online file.
Implementation:
- Senders should be able to ensure that a big file can only be viewed by the recipients of the email (this should be the default setting). Is this true possible for all providers ?
- What technology for provider API implementation ?
- Can this be done through a web app exposing web intents ? Can the web app be local ?
- Each provider must be supported through an installable provider (web app or add-on), some of which are distributed by default with TB
- FTP servers are difficult to set up for average users (at least to ensure security & privacy). Can this be offered to an average consumer (probably one of the the reason why online file storage are popular)
|Feature overview=This Thunderbird feature provides a way to use online storage services to store large size email file attachments. With this feature, email file attachments are replaced by urls pointing to an online file storage server, where the files can be found.
This feature is meant to:
- offer a way to easily share very large files through email
- reduce ‘file too big’ bounce email situations
- encourage file sharing over copying
- save recipients inbox space and eliminate file duplication for multiple recipients
- increase attachment sending and receiving speed
A tight and smooth integration with Thunderbird will be required to facilitate usage and adoption of this alternative way of sending a file via email. For example, Thunderbird could propose to use this feature to resend a ‘file-too-big’ bounced email or when sending a file known or likely to be too large for the recipients email domain. On a different idea, on-the-fly setup/signup could also be implemented to ease the first use of the feature.
Online storage services can be of different categories:
- commercial services such as DropBox, YouSendIt, Box.net...
- consumer document sharing services such as Google Docs or MS Skydrive,
- enterprise document sharing resources such as MS SharePoint, network drives
- or more traditional network storage resources such FTP folders, …
|Feature users and use cases=- When a user attaches a 'Big File'
If the file is above a certain size, warn the user and offer to use online storage instead of attachment. Note: The size could be an arbitrary value, or set by the user, or even retrieved on the fly by analyzing recipients domains (gmail.com for example has a limit of 25MB).
- When an email is bounced
If Thunderbird detects that the bounce reason is a 'File Too Big', offer to resend via BigFile.
- On-the-fly setup/signup
If the user is about to use BigFiles but has not configured TB for it, allow the setup or signup procedure to happen on the fly, in such a way that the user should not have to bother pre-confguring BigFiles before first using it.
A list of pre-configured online storage services should be proposed for setup or signup.
- Quota management
Detect over quota situations (mostly in the case of consumer online storage services free offers) and guide towards resolution (signup for premium service, file deletions...)
- Advanced features - Some consumer online storage services offer document tracking (YouSendIt for example). It might be interesting |Feature dependencies=` |Feature requirements=- APIs access to consumer & professional online storage services |Feature non-goals=This is not a replacement to file attachment. Care should be taken to make it clear in the UX (for example through a specific UI), whilst facilitating the use of BigFiles when using 'regular' attachments. |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Thunderbird |
| Secondary roadmap | ` |
| Feature list | Thunderbird |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=Thunderbird |Feature secondary roadmap=` |Feature list=Thunderbird |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}