Features/Jetpack/Land Parts of Add-on SDK In Core

From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Land Parts of Add-on SDK In Core
Stage Planning
Status In progress
Release target `
Health OK
Status note `


Product manager David Mason
Directly Responsible Individual Dietrich Ayala
Lead engineer Irakli Gozalishvili
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


Stage 1: Definition

1. Feature overview

The Add-on SDK is a product for building Firefox addons. You download it separately from Firefox, and it builds addons that load in Firefox using Firefox's existing support for loading addons.

There are a variety of advantages to this approach, but there are also downsides. In particular, because the SDK packages API implementations, the addon bootstrapper, and the module loader with each individual addon (à la static linking in compiled software), addon packages are relatively large.

To reduce addon package size to the absolute minimum, we should land stable parts of the SDK's functionality into the core of Firefox. This includes API implementations, and it may also include the module loader and the bootstrapper.

However, we might decide to land API implementations in core as JavaScript Harmony modules rather than landing a CommonJS module loader in core alongside them.

Also, we should wait for the API implementations to stabilize (f.e. as a result of OOP addons) before we land them in core, since we can iterate faster on them in the SDK's code repository than in core's.

2. Users & use cases

The target audience is addon developers. The use case is an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) to build an addon.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan


8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation


Stage 5: Release

10. Landing criteria


Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap Jetpack
Secondary roadmap `
Feature list Jetpack
Project `
Engineering team Jetpack

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `