Features/Jetpack/Land Parts of Add-on SDK In Core
|Land Parts of Add-on SDK In Core|
|Product manager||David Mason|
|Directly Responsible Individual||Dietrich Ayala|
|Lead engineer||Irakli Gozalishvili|
|Product marketing lead||`|
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.
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.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes