Firefox/Features/PFS2 datasource

Feature	Status	ETA	Owner
Feature Page Structure	Needs input from webdev	Firefox 6-7	Kev Needham

Summary

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

Team

Who's working on this?

• Feature Manager: Kev Needham
• Lead Developer: Mossop (?)
• Product Manager: Kev Needham
• QA: TBD
• UX: TBD
• Security: TBD
• Privacy: N/A
• WebDev: Morgamic

Release Requirements

• Performance and load testing of PFS2 application to ensure its 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

Next Steps & Open Issues

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 573775, 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.

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

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.

Use Cases

Everyone loves use cases, so you should provide them if you can (and where it makes sense). The Channel Switcher Feature Page has some good examples.

Designs

No designs required. Project has been scoped at https://wiki.mozilla.org/PFS2

Test Plans

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.

Goals

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

Non-Goals

• Plugin Update Checking
• Plugin Updates

Legend (remove if you like)

	Healthy: feature is progressing as expected.
	Blocked: feature is currently blocked.
	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.

Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.