Firefox/Features/PFS2 datasource: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(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...")
 
No edit summary
 
(14 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Use PFS2 as Plugin Finder data source
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Development
| style="font-weight: bold; background: #DDD;" | Status
|Feature status=In progress
| style="font-weight: bold; background: #DDD;" | ETA
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | Owner
|Feature status note=Needs input from webdev
|-
}}
<section begin="status" />
{{FeatureTeam
| [[Feature Page Structure]]
|Feature product manager=Kev Needham
| {{StatusHealthy|status=Needs input from webdev}}
|Feature feature manager=Kev Needham
| 2011-05-02
|Feature qa lead=Mihai Morar
| Kev Needham
|Feature additional members=Mike Morgan (webdev)
<section end="status" />
}}
|-
{{FeaturePageBody
|}
|Feature open issues and risks=Readiness of PFS2 webapp is a blocker to implementation. Risks include resource availability with WebDev, and results of testing. The back-end must be ready to go before a product change is made, so the web service is a blocker for this feature.


== Summary ==
This feature should be re-considered as a P2 given the unknown state of PFS2.
|Feature overview=Ensure PFS2 is ready for prime-time, and switch the pfs.datasource.url in Firefox (and update legacy URI, if possible) to use PFS2.


Switch the pfs.datasource.url to use PFS2.
Goals: Provide identical service as current PFS, but use new infrastructure which facilitates management of listed plugins through the directory-driven back-end.
|Feature requirements=* Performance and load testing of PFS2 application to ensure it is capable of meeting needs of Firefox users
* WebDev signoff of above
* Functional testing of PFS2 application
* QA Signoff of above
* Security review of PFS2 application
* Commit preference change to trunk and test
|Feature non-goals=* Plugin Update Checking
* Plugin Updates
|Feature functional spec=No designs required. Project has been scoped at [[PFS2]].
|Feature qa review=* The current test plan/method is documented on the [[PFS#Testing_PFS|PFS wiki page]], and requires updating for PFS2 to identify platforms, mime-types, and expected behaviours.
|Feature implementation notes=The change to Firefox itself is relatively minor, and involves changing a single preference. The larger issues are on the back-end, where additional work may be required to ensure the service can meet demand, and stay responsive (see bugs {{bug|573775}}, {{bug|564803}}, and {{bug|564807}}, which outline some potential issues). Next steps require an assessment from WebDev on current state of PFS2, and what changes and/or development is required to bring it on-line.  


== Team ==
The [[PFS#Testing_PFS|PFS Test Plan]] will need to be updated to identify test cases/scenarios.
Who's working on this?


* '''Feature Manager''': ''Kev Needham''
* {{bug|573834}} - Change PFS backend to use PFS2
* '''Lead Developer''': ''TBD''
* {{bug|573775}} - Load test PFS2 API for Firefox 4 integration
* '''Product Manager''': ''TBD''
* {{bug|564803}} - Directory needs better caching with per-plugin invalidation
* '''QA''': ''TBD''
* {{bug|564807}} - Optimize the directory's gnarly slow DB queries
* '''UX''': ''TBD''
}}
* '''Security''': ''TBD''
{{FeatureInfo
* '''Privacy''': ''TBD''
|Feature priority=P2
* '''WebDev''': ''TBD''
|Feature roadmap=Plugin Interactions
 
|Feature list=Desktop
== Release Requirements ==
|Feature engineering team=Desktop front-end
Complete checklist of items that need to be satisfied before we can call this feature "done". 
}}
 
{{FeatureTeamStatus
== Next Steps & Open Issues ==
|Feature security status=sec-review-unnecessary
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.  Including the name of who's responsible for each item, and a rough ETA can be useful.
|Feature security health=OK
 
|Feature security notes={{bug|744966}}
Open issues include unanswered questions, things that need to be explored, decisions that still need to be made, etc.  Again, including the name of who's responsible for each item can be useful.
}}
 
== Related Bugs & Dependencies ==
 
{{bug|573834}} - Change PFS backend to use PFS2
{{bug|573775}} - Load test PFS2 API for Firefox 4 integration
{{bug|564803}} - Directory needs better caching with per-plugin invalidation
{{bug|564807}} - Optimize the directory's gnarly slow DB queries
 
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
 
== Risks ==
Identify, prioritize, track and communicate any risks associated with this feature/project.
 
== Use Cases ==
Everyone loves use cases, so you should provide them if you can (and where it makes sense).  The [[ChannelSwitching/ChannelSwitchingFeature#Use_Cases|Channel Switcher]] Feature Page has some good examples.
 
== Designs ==
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
 
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.
 
== Goals ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
 
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.
 
== Other Stuff ==
Can include things like:
* Competitive landscape
* Research & references
* Whatever else is useful to the project.
 
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status=&nbsp;}}
| 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.
|}
 
__NOTOC__
 
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 
[[Category:Features]]
[[Category:Firefox]]
[[Category:Platform]]
[[Category:Services]]
[[Category:Mobile]]
[[Category:Other]]

Latest revision as of 07:16, 22 July 2013

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

Status

Use PFS2 as Plugin Finder data source
Stage Development
Status In progress
Release target `
Health OK
Status note Needs input from webdev

{{#set:Feature name=Use PFS2 as Plugin Finder data source

|Feature stage=Development |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Needs input from webdev }}

Team

Product manager Kev Needham
Directly Responsible Individual Kev Needham
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Mihai Morar
UX lead `
Product marketing lead `
Operations lead `
Additional members Mike Morgan (webdev)

{{#set:Feature product manager=Kev Needham

|Feature feature manager=Kev Needham |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Mihai Morar |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Mike Morgan (webdev) }}

Open issues/risks

Readiness of PFS2 webapp is a blocker to implementation. Risks include resource availability with WebDev, and results of testing. The back-end must be ready to go before a product change is made, so the web service is a blocker for this feature.

This feature should be re-considered as a P2 given the unknown state of PFS2.

Stage 1: Definition

1. Feature overview

Ensure PFS2 is ready for prime-time, and switch the pfs.datasource.url in Firefox (and update legacy URI, if possible) to use PFS2.

Goals: Provide identical service as current PFS, but use new infrastructure which facilitates management of listed plugins through the directory-driven back-end.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

  • Performance and load testing of PFS2 application to ensure it is capable of meeting needs of Firefox users
  • WebDev signoff of above
  • Functional testing of PFS2 application
  • QA Signoff of above
  • Security review of PFS2 application
  • Commit preference change to trunk and test

Non-goals

  • Plugin Update Checking
  • Plugin Updates

Stage 2: Design

5. Functional specification

No designs required. Project has been scoped at PFS2.

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

  • The current test plan/method is documented on the PFS wiki page, and requires updating for PFS2 to identify platforms, mime-types, and expected behaviours.

Operations review

`

Stage 4: Development

9. Implementation

The change to Firefox itself is relatively minor, and involves changing a single preference. The larger issues are on the back-end, where additional work may be required to ensure the service can meet demand, and stay responsive (see bugs bug 573775, bug 564803, and bug 564807, which outline some potential issues). Next steps require an assessment from WebDev on current state of PFS2, and what changes and/or development is required to bring it on-line.

The PFS Test Plan will need to be updated to identify test cases/scenarios.

  • bug 573834 - Change PFS backend to use PFS2
  • bug 573775 - Load test PFS2 API for Firefox 4 integration
  • bug 564803 - Directory needs better caching with per-plugin invalidation
  • bug 564807 - Optimize the directory's gnarly slow DB queries

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=Readiness of PFS2 webapp is a blocker to implementation. Risks include resource availability with WebDev, and results of testing. The back-end must be ready to go before a product change is made, so the web service is a blocker for this feature.

This feature should be re-considered as a P2 given the unknown state of PFS2. |Feature overview=Ensure PFS2 is ready for prime-time, and switch the pfs.datasource.url in Firefox (and update legacy URI, if possible) to use PFS2.

Goals: Provide identical service as current PFS, but use new infrastructure which facilitates management of listed plugins through the directory-driven back-end. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=* Performance and load testing of PFS2 application to ensure it is capable of meeting needs of Firefox users

  • WebDev signoff of above
  • Functional testing of PFS2 application
  • QA Signoff of above
  • Security review of PFS2 application
  • Commit preference change to trunk and test

|Feature non-goals=* Plugin Update Checking

  • Plugin Updates

|Feature functional spec=No designs required. Project has been scoped at PFS2. |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=* The current test plan/method is documented on the PFS wiki page, and requires updating for PFS2 to identify platforms, mime-types, and expected behaviours. |Feature operations review=` |Feature implementation notes=The change to Firefox itself is relatively minor, and involves changing a single preference. The larger issues are on the back-end, where additional work may be required to ensure the service can meet demand, and stay responsive (see bugs bug 573775, bug 564803, and bug 564807, which outline some potential issues). Next steps require an assessment from WebDev on current state of PFS2, and what changes and/or development is required to bring it on-line.

The PFS Test Plan will need to be updated to identify test cases/scenarios.

  • bug 573834 - Change PFS backend to use PFS2
  • bug 573775 - Load test PFS2 API for Firefox 4 integration
  • bug 564803 - Directory needs better caching with per-plugin invalidation
  • bug 564807 - Optimize the directory's gnarly slow DB queries

|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 sec-review-unnecessary bug 744966
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=sec-review-unnecessary |Feature security health=OK |Feature security notes=bug 744966 |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=` }}


Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/Features/PFS2_datasource&oldid=682077"