Features/Firefox/PluginCrashComments
Status
| Plugin crash comments | |
| Stage | Planning |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Plugin crash comments
|Feature stage=Planning |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | Sheila Mooney |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Vlad Ghetiu (irc: vladg) |
| UX lead | Jennifer Boriss |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Sheila Mooney |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Vlad Ghetiu (irc: vladg) |Feature ux lead=Jennifer Boriss |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
Need to get this feature prioritized and an owner for the implementation.
Stage 1: Definition
1. Feature overview
Today, if a plugin crashes, the user is prompted to submit a crash report. However, they are not provided with an interface for entering a comment alongside the crash report as they can with other types of crashes. Although comments are optional and we rely on the users ability to give us informed information about what they are doing at the time of the crash, they are another piece of data that can assist us in diagnosing a problem. Plugin crashes are particularly difficult to analyze so any additional data is helpful.
A recent security study showed a pretty high percentage of users liked the idea of providing comments and crash reports to help improve Firefox. In more than one case during the course of Firefox 4 development, reading the users' comments has lead to the resolution of a serious top crash in the product. For this reason we think this is a pretty important enhancement to get in.
Another side benefit of getting this implemented is Electrolysis. We will want to enable users to submit comments when the content process crashes.
2. Users & use cases
`
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
Design details and mockups can be found in Bug 648675.
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
We are currently tracking this feature in Bug 648675.
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=Need to get this feature prioritized and an owner for the implementation. |Feature overview=Today, if a plugin crashes, the user is prompted to submit a crash report. However, they are not provided with an interface for entering a comment alongside the crash report as they can with other types of crashes. Although comments are optional and we rely on the users ability to give us informed information about what they are doing at the time of the crash, they are another piece of data that can assist us in diagnosing a problem. Plugin crashes are particularly difficult to analyze so any additional data is helpful.
A recent security study showed a pretty high percentage of users liked the idea of providing comments and crash reports to help improve Firefox. In more than one case during the course of Firefox 4 development, reading the users' comments has lead to the resolution of a serious top crash in the product. For this reason we think this is a pretty important enhancement to get in.
Another side benefit of getting this implemented is Electrolysis. We will want to enable users to submit comments when the content process crashes. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=Design details and mockups can be found in Bug 648675. |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=We are currently tracking this feature in Bug 648675. |Feature landing criteria=` }}
Feature details
| Priority | P2 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Plugin Interactions |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | Desktop front-end |
{{#set:Feature priority=P2
|Feature rank=999 |Feature theme=` |Feature roadmap=Plugin Interactions |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}
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=` }}