Firefox/Features/Add plugincheck functionality to Add-on Manager: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(13 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Add plugincheck functionality to Add-on Manager
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Planning
| style="font-weight: bold; background: #DDD;" | Status
|Feature health=Blocked
| style="font-weight: bold; background: #DDD;" | ETA
|Feature status note=Blocked on finding an implementor, and possibly PFS2.
| style="font-weight: bold; background: #DDD;" | Owner
}}
|-
{{FeatureTeam
<section begin="status" />
|Feature product manager=Kev Needham
| [[Firefox/Features/Add_plugincheck_functionality_to_Add-on_Manager]]
|Feature qa lead=Henrik Skupin
| {{StatusBlocked|status=Blocked on finding an implementor, and possibly PFS2.}}
|Feature ux lead=Jennifer Boriss
| TBA, probably Firefox 7
}}
| Kev Needham
{{FeaturePageBody
<section end="status" />
|Feature open issues and risks=* Determine where to retrieve latest plugin info from. Possibilities:
|-
|}
 
== Summary ==
Integrate Plugin Check with installed plugins in the Add-ons Manager.
 
== Team ==
 
* '''Feature Manager''': [mailto:mossop@mozilla.com Dave Townsend]
* '''Lead Developer''': TBA
* '''Product Manager''': [mailto:kev@mozilla.com Kev Needham]
* '''QA''': [mailto:hskupin@mozilla.com Henrik Skupin]
* '''UX''': [mailto:jboriss@mozilla.com Jennifer Boriss]
 
 
== Release Requirements ==
* ???
 
== Next Steps & Open Issues ==
* Determine where to retrieve latest plugin info from. Possibilities:
** [[Firefox/Features/PFS2_datasource|PFS2]]
** [[Firefox/Features/PFS2_datasource|PFS2]]
** New API provided by PluginCheck
** New API provided by PluginCheck
** PFS1
** PFS1
 
|Feature overview=Integrate Plugin Check with installed plugins in the Add-ons Manager.
== Related Bugs & Dependencies ==
|Feature users and use cases=* Plugin A is out of date. Vendor provides a link to an updated installer. Can download installer directly from Addons Manager.
Bug for this feature is {{bug|613305}}.
* Plugin B is out of date. Vendor provides a link to a page that contains information on how to update. Can get to that page from the Addons Manager.
* Plugin C is out of date. SUMO has a support article on how to update it. Can get to that page from the Addons Manager.
* Plugin X is up to date. User sees this and is overcome with joy.
|Feature non-goals=* Installing and updating of all plugins via XPI hosted on AMO (long-term plan?).
|Feature ux design=[[Image:Plugincheck-integration.png]]
|Feature qa review=Most (if not all) of this should be able to be automated with browser-mochitest tests and a fake PFS/PFS2 server.
|Feature implementation notes=Bug for this feature is {{bug|613305}}.


Intermediate step is to include a link to the PluginCheck page in the Addons Manager. See:
Intermediate step is to include a link to the PluginCheck page in the Addons Manager. See:
Line 43: Line 29:
* {{bug|656269}}
* {{bug|656269}}


[[Firefox/Features/PFS2_datasource|PFS2]] may be a dependency.  
[[Firefox/Features/PFS2_datasource|PFS2]] may be a dependency.
 
}}
== Risks ==
{{FeatureInfo
TBA.
|Feature priority=P2
 
|Feature rank=7
== Use Cases ==
|Feature theme=Experience
* Plugin A is out of date. Vendor provides a link to an updated installer. Can download installer directly from Addons Manager.
|Feature roadmap=Plugin Interactions
* Plugin B is out of date. Vendor provides a link to a page that contains information on how to update. Can get to that page from the Addons Manager.
|Feature list=Desktop
* Plugin C is out of date. SUMO has a support article on how to update it. Can get to that page from the Addons Manager.
|Feature engineering team=Desktop front-end
* Plugin X is up to date. User sees this and is overcome with joy.
}}
 
{{FeatureTeamStatus
== Designs ==
|Feature security status=sec-review-needed
[[Image:Plugincheck-integration.png]]
|Feature security health=Blocked
 
|Feature security notes={{bug|744967}}
== Test Plans ==
|Feature qa status=Not Started
Most (if not all) of this should be able to be automated with browser-mochitest tests and a fake PFS/PFS2 server.
}}
 
== Goals ==
* Should be able to tell which plugins are out of date, and figure out how to update them from within the addons manager.
 
== Non-Goals ==
* Installing and updating of all plugins via XPI hosted on AMO (long-term plan?).
 
== Other Stuff ==
TBA.
 
__NOTOC__
 
[[Category:Features]]
[[Category:Firefox]]

Latest revision as of 21:46, 12 April 2012

Please use "Edit with form" above to edit this page.

Status

Add plugincheck functionality to Add-on Manager
Stage Planning
Status `
Release target `
Health Blocked
Status note Blocked on finding an implementor, and possibly PFS2.

{{#set:Feature name=Add plugincheck functionality to Add-on Manager

|Feature stage=Planning |Feature status=` |Feature version=` |Feature health=Blocked |Feature status note=Blocked on finding an implementor, and possibly PFS2. }}

Team

Product manager Kev Needham
Directly Responsible Individual `
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Henrik Skupin
UX lead Jennifer Boriss
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Kev Needham

|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Henrik Skupin |Feature ux lead=Jennifer Boriss |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

  • Determine where to retrieve latest plugin info from. Possibilities:
    • PFS2
    • New API provided by PluginCheck
    • PFS1

Stage 1: Definition

1. Feature overview

Integrate Plugin Check with installed plugins in the Add-ons Manager.

2. Users & use cases

  • Plugin A is out of date. Vendor provides a link to an updated installer. Can download installer directly from Addons Manager.
  • Plugin B is out of date. Vendor provides a link to a page that contains information on how to update. Can get to that page from the Addons Manager.
  • Plugin C is out of date. SUMO has a support article on how to update it. Can get to that page from the Addons Manager.
  • Plugin X is up to date. User sees this and is overcome with joy.

3. Dependencies

`

4. Requirements

`

Non-goals

  • Installing and updating of all plugins via XPI hosted on AMO (long-term plan?).

Stage 2: Design

5. Functional specification

`

6. User experience design

Plugincheck-integration.png

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

Most (if not all) of this should be able to be automated with browser-mochitest tests and a fake PFS/PFS2 server.

Operations review

`

Stage 4: Development

9. Implementation

Bug for this feature is bug 613305.

Intermediate step is to include a link to the PluginCheck page in the Addons Manager. See:

PFS2 may be a dependency.

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=* Determine where to retrieve latest plugin info from. Possibilities:

    • PFS2
    • New API provided by PluginCheck
    • PFS1

|Feature overview=Integrate Plugin Check with installed plugins in the Add-ons Manager. |Feature users and use cases=* Plugin A is out of date. Vendor provides a link to an updated installer. Can download installer directly from Addons Manager.

  • Plugin B is out of date. Vendor provides a link to a page that contains information on how to update. Can get to that page from the Addons Manager.
  • Plugin C is out of date. SUMO has a support article on how to update it. Can get to that page from the Addons Manager.
  • Plugin X is up to date. User sees this and is overcome with joy.

|Feature dependencies=` |Feature requirements=` |Feature non-goals=* Installing and updating of all plugins via XPI hosted on AMO (long-term plan?). |Feature functional spec=` |Feature ux design=Plugincheck-integration.png |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=Most (if not all) of this should be able to be automated with browser-mochitest tests and a fake PFS/PFS2 server. |Feature operations review=` |Feature implementation notes=Bug for this feature is bug 613305.

Intermediate step is to include a link to the PluginCheck page in the Addons Manager. See:

PFS2 may be a dependency. |Feature landing criteria=` }}

Feature details

Priority P2
Rank 7
Theme / Goal Experience
Roadmap Plugin Interactions
Secondary roadmap `
Feature list Desktop
Project `
Engineering team Desktop front-end

{{#set:Feature priority=P2

|Feature rank=7 |Feature theme=Experience |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 sec-review-needed bug 744967
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance Not Started `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-needed |Feature security health=Blocked |Feature security notes=bug 744967 |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Not Started |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}