Canmove, confirm
548
edits
Changes
Created page with "{{FeatureStatus |Feature name=Add-on SDK as an Addon |Feature stage=Draft |Feature version=TBD |Feature health=OK |Feature status note=Investigating as part of post-1.0 planning ..."
{{FeatureStatus
|Feature name=Add-on SDK as an Addon
|Feature stage=Draft
|Feature version=TBD
|Feature health=OK
|Feature status note=Investigating as part of post-1.0 planning
}}
{{FeatureTeam
|Feature product manager=David Mason
|Feature feature manager=David Mason/Myk Melez
}}
{{FeaturePageBody
|Feature overview=The Add-on SDK is distributed as ZIP and tarball archives on ftp.mozilla.org. We should distribute it as an addon on addons.mozilla.org instead, because:
* AMO has built-in support for automated updates to newer versions
* AMO has built-in support for stable and beta distribution channels
* provided the SDK is able to package itself, it would make SDK developers eat their own dogfood
* it would enable the Builder to offload the time-consuming repacking process to the client
* it would open up the possibility of adding graphical addon development interfaces (like those in the original prototype, in Builder, and in Alexandre Poirot's port of the SDK's functionality to an addon) to Firefox itself
|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.
}}
{{FeatureInfo
|Feature priority=P3
|Feature roadmap=Jetpack
|Feature list=Jetpack
|Feature engineering team=Jetpack
}}
{{FeatureTeamStatus
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}
|Feature name=Add-on SDK as an Addon
|Feature stage=Draft
|Feature version=TBD
|Feature health=OK
|Feature status note=Investigating as part of post-1.0 planning
}}
{{FeatureTeam
|Feature product manager=David Mason
|Feature feature manager=David Mason/Myk Melez
}}
{{FeaturePageBody
|Feature overview=The Add-on SDK is distributed as ZIP and tarball archives on ftp.mozilla.org. We should distribute it as an addon on addons.mozilla.org instead, because:
* AMO has built-in support for automated updates to newer versions
* AMO has built-in support for stable and beta distribution channels
* provided the SDK is able to package itself, it would make SDK developers eat their own dogfood
* it would enable the Builder to offload the time-consuming repacking process to the client
* it would open up the possibility of adding graphical addon development interfaces (like those in the original prototype, in Builder, and in Alexandre Poirot's port of the SDK's functionality to an addon) to Firefox itself
|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.
}}
{{FeatureInfo
|Feature priority=P3
|Feature roadmap=Jetpack
|Feature list=Jetpack
|Feature engineering team=Jetpack
}}
{{FeatureTeamStatus
|Feature products status=tbd
|Feature engineering status=tbd
|Feature security status=tbd
|Feature privacy status=tbd
|Feature localization status=tbd
|Feature accessibility status=tbd
|Feature qa status=tbd
|Feature ux status=tbd
}}
