Simple module loader
Status
| Feature name here | |
| Stage | Draft |
| Status | In progress |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Feature name here
|Feature stage=Draft |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | David Mason |
| Directly Responsible Individual | ` |
| Lead engineer | Irakli Gozalishvili |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=David Mason
|Feature feature manager=` |Feature lead engineer=Irakli Gozalishvili |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Addon SDK's module loader was implemented at the early stage of the project and intentionally was designed with lots of flexibility in mind. This flexibility comes with a price of complexity, unjustified for at this stage of the project.
This feature is to simplify the SDK's module loader and bootstrap code and relay on platform capabilities were possible.
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
https://bugzilla.mozilla.org/show_bug.cgi?id=638742 https://bugzilla.mozilla.org/show_bug.cgi?id=672443
4. Requirements
- Combine bootstrap.js, components/harness.js, cuddlefish.js and securable-module.js into single form module loader that has no external dependencies. - Let platform handle all IO operations associated to the module loading. - Make module loader agnostic of addon form (whether.xpi is unpacked or not).
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=Addon SDK's module loader was implemented at the early stage of the project and intentionally was designed with lots of flexibility in mind. This flexibility comes with a price of complexity, unjustified for at this stage of the project.
This feature is to simplify the SDK's module loader and bootstrap code and relay on platform capabilities were possible. |Feature users and 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. |Feature dependencies=https://bugzilla.mozilla.org/show_bug.cgi?id=638742 https://bugzilla.mozilla.org/show_bug.cgi?id=672443 |Feature requirements=- Combine bootstrap.js, components/harness.js, cuddlefish.js and securable-module.js into single form module loader that has no external dependencies. - Let platform handle all IO operations associated to the module loading. - Make module loader agnostic of addon form (whether.xpi is unpacked or not). |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}