View source for Add-on SDK in Firefox

{{FeatureStatus
|Feature name=Add-on SDK in Firefox
|Feature stage=Draft
|Feature status=In progress
|Feature version=Firefox 15
|Feature health=OK
}}
{{FeatureTeam
|Feature feature manager=Dietrich Ayala (:dietrich)
|Feature lead engineer=Irakli Gozalishvili (:gozala)
}}
{{FeaturePageBody
|Feature open issues and risks=Open issues:

* Need to ensure Jetpack tests are run per-checkin by default on all branches (where it makes sense)
|Feature overview=Ship the Add-on SDK runtime and libraries inside Firefox.

* Meta-bug: {{bug|731779}}
* Bi-weekly meetings with the [https://wiki.mozilla.org/Jetpack/Features Jetpack Features group]

Prior work, notes:

* [https://etherpad.mozilla.org/jetpack-in-firefox Notes from Dec 2011 meeting]
* [https://etherpad.mozilla.org/jetpack-in-firefox-estimate Package-oriented proposal from Drew]
* Brian Warner currently runs a bridge that syncs the Add-on SDK Git repo with hg.m.o/projects/addon-sdk, based on https://github.com/schacon/hg-git
|Feature users and use cases=* Reduced add-on size. Currently add-ons created with the SDK are 200k at a minimum. This reduces download time and installation time of add-ons, streamlining the process.
* Develop core features using the SDK. Firefox core developers can use the SDK libraries to build features.
* Easier to convert add-ons into Firefox features, so prototyping features should be easier.
* Repacking might be simpler, or not required at all
* Scratchpad could be used as an offline version of the Add-on Builder.
* Old school add-ons can more easily leverage features from the add-on sdk, which should help them port older add-ons.
|Feature dependencies=* Packageless Jetpack proposal may be a dependency ([https://github.com/mozilla/addon-sdk/wiki/JEP-packageless view])
|Feature requirements=* Add-on SDK loader and API libraries are shipped inside Firefox, removing the necessity of packaging them inside each add-on.
* SDK development continues on Github.
* SDK continues to be developed and reviewed by the SDK team.
|Feature non-goals=* Allow runtime resolution of modules.
* Allow sharing of modules across add-ons.
* Allow interdependency at the add-on level.
|Feature implementation plan=Meta-bug: {{bug|731779}}

* Set up Git->HG syncing infrastructure (Non-blocking: If not ready by landing time, can do weekly drops.)
* Work with browser/toolkit module owners to determine code location in each component.
* Land CommonJS loader in Firefox (In toolkit, have Mossop to review.)
* Jetpack housecleaning required before landing
** Misc cleanup (removing window-utils, etc.)
** Packagelessness
** Separate core APIs into Browser and Toolkit sets
* Land core APIs in Firefox

Each of these Loader usage scenarios should be supported and documented with code samples:
* Inclusion into XUL window scope
* Inclusion into non-window scopes (JS XPCOM, JS Modules)
* Support shared & private instances

|Feature security review=The Add-on SDK has gone through multiple security reviews. Should schedule another one to review how/where the code lives and is initiated/loaded inside Firefox.
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus
|Feature security status=sec-review-needed
|Feature security health=Assigned
|Feature security notes=dveditz assigned
}}