canmove, Confirmed users
1,570
edits
(Created page with '= Overview = '''Sprint lead:''' Mossop<br/> '''Sprinters:''' Unfocused, johnath ;Description :Explore possibilities of uplifting Jetpack to Firefox.future, to ...') |
No edit summary |
||
Line 7: | Line 7: | ||
:Explore possibilities of uplifting [[Labs/Jetpack|Jetpack]] to Firefox.future, to provide a more web-like method of extending the browser. | :Explore possibilities of uplifting [[Labs/Jetpack|Jetpack]] to Firefox.future, to provide a more web-like method of extending the browser. | ||
= | = Potential exploration areas = | ||
* | * APIs: Existing and new capabilities that we believe need to be either abstracted from XPCOM (e.g. crypto) and XUL (e.g. menus), or created wholesale (e.g. slidebar), in order to enable at least 80% of the capabilities of popular add-ons | ||
* | * Platform and front-end changes required to enable these APIs as well as the nascent security model (re: work being done by mrbkap, lucas and atul on flexible membranes, securable modules, etc.) | ||
* Jetpack | * Discovery, installation & asset management capabilities and interaction model required to support Jetpacks as first-class add-ons in the product | ||
* Create roadmap/plan for uplifting Jetpack into Firefox | |||
* Explore potential integration/interaction with new [[Firefox/Sprints/Extension_Manager_API|Extension Manager API]] | |||
'''Non Goals''' | '''Non Goals''' | ||
Line 17: | Line 19: | ||
* Make the Jetpack project redundant | * Make the Jetpack project redundant | ||
* Replace existing addons architecture | * Replace existing addons architecture | ||
* Standardizing API for other browsers to implement | |||
= Status = | = Status = | ||
* Established a dialogue with the Jetpack team, scheduling an phone meeting for early next week | |||
* | |||
= References = | = References = |