Add-on SDK in Firefox: Difference between revisions

no edit summary
mNo edit summary
No edit summary
Line 3: Line 3:
|Feature stage=Draft
|Feature stage=Draft
|Feature status=In progress
|Feature status=In progress
|Feature version=Firefox 14
|Feature version=Firefox 15
|Feature health=OK
|Feature health=OK
}}
}}
Line 39: Line 39:
|Feature implementation plan=Meta-bug: {{bug|731779}}
|Feature implementation plan=Meta-bug: {{bug|731779}}


# Allow one-way syncing of a Git repository to a Mercurial repository
* Set up Git->HG syncing infrastructure (Non-blocking: If not ready by landing time, can do weekly drops.)
# Create a Git repo that's specifically for pulling from
* Work with browser/toolkit module owners to determine code location in each component.
# Land the SDK's module loader in Firefox at /browser/modules via the Git repo
* Land CommonJS loader in Firefox (In toolkit, have Mossop to review.)
# Progressively land SDK API libraries in Firefox via the Git branch
* Jetpack housecleaning required before landing
# Once migration is complete, sync the SDK's master instead of the migration rep
** 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.
|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.
}}
}}
Confirmed users, Bureaucrats and Sysops emeriti
2,088

edits