Firefox/Projects/Jetpack

Summary

Make sure Jetpack's needs in Firefox and Platform are met. Facilitate communication between Firefox and Jetpack teams.

Background

Jetpack's architecture under versions 0.8 and earlier (now called the Jetpack "prototype") is being abandoned for a new architecture nicknamed the Jetpack "reboot". Check the Labs reboot wiki page for details, but briefly, the differences between the two:

• The reboot has a security model, the prototype didn't.
• Extensions produced under the reboot are actually XPIs. Under the prototype they were single JS files.
• The reboot is very loosely integrated with Firefox. The Jetpack runtime is bundled in each XPI. The only significant hook that these XPIs require is a no-restart-needed mechanism.

Current Status

• Firefox team
  • ??? Is mossop handling the no-restart-needed mechanism or is atul?
• Jetpack team
  • Determining the set of APIs to expose under the reboot.
  • Published a roadmap.

Next Steps

• ???

Related Bugs

• List of Jetpack-related Firefox/Platform bugs (quicksearch [jetpack])
• Integration of runtime into Firefox/Platform:
  • ??? Where's the no-restart-needed-mechanism bug?
• Enabling Jetpack APIs:
  • ??? Where's Myk's bug about arbitrary content in XUL panels? bug 130078, bug 532569?

Related Links

• Labs Jetpack reboot wiki page

Team

• Lead: adw
• Sprinter: mossop
• Jetpack team contact: atul

Goals/Use Cases

• Make sure Jetpack has what it needs for a smooth uplift into Firefox.
• Keep an open communication channel between the Firefox and Jetpack teams.

Non Goals

• Finalize the Jetpack API.