Jetpack/Roadmap-2011

Jetpack 1.0 Goals

• A seamless install process: It defeats the purpose of Jetpack to first require users to install Jetpack, then install a particular Jetpack, before using its features. Instead, we need a solution which allows a seamless install process.
• Seamless debugging: No pointless error messages, and all relevant warnings, line numbers, and tracebacks, are displayed.
• Enabling API: An API deep enough to support a large range of add-ons. It is a non-goal in 1.0 to support everything, instead it is to support 80% of the long-tail of add-ons. The exact feature set of the API will be determined by a set of target add-ons (TBD) and feedback from Jetpack authors.
  • Frozen API: Although the API may be versioned, we the API will be backwards compatible from 1.0 on.
• Beautiful by default: A set of OS-specific icons, as well as a beautiful look for Jetpacks.
• Security-sensitive Import mechanism: The strength of any API is measured in how easily 3rd parties can extend it. The 1.0 release will have a strong import mechanism, replete with security provisions.
• Security: A functioning security system that mixes code with social protections.
  • An AMO-like service with social code-review
• Localization story
• Works on Fennec

Milestone 1

Functional prototype API that follows the Guiding Principles and provides enough capability to implement these target add-ons:

Target Add-ons

Milestone 2

Get to a point where we can start implementing something like social bookmarking (e.g. Delicious Bookmarks) via the API:

• Access to prefs
• Access to cookie jar or alternatively the ability to have its own sandboxed cookie jar
• Web service calls via Firefox network prefs (i.e. proxy settings)
• mozStorage
• Ability to modify menus/keyboard shortcuts
• New Sidebar, new toolbar, and adding/removing buttons from Fx toolbar
• Ability to add search plugins (but not remove unrelated plugins)