Features/Jetpack/Add-on SDK Localization API and Service: Difference between revisions

Features/Jetpack/Add-on SDK Localization API and Service (view source)

Revision as of 23:51, 14 September 2011

1,046 bytes added , 14 September 2011

no edit summary

Dcm-moz

canmove, Confirmed users

548

edits

@@ Line 1: / Line 1: @@
 {{FeatureStatus
 |Feature name=Add-on SDK Localization API and Service
-|Feature stage=Draft
+|Feature stage=Planning
+|Feature status=In progress
 |Feature version=TBD
 |Feature health=OK
@@ Line 20: / Line 21: @@
 |Feature dependencies=The feature depends on work to be done in the SDK, AMO, and a localization service with which AMO interacts to solicit and retrieve localizations.
 |Feature requirements=The feature must enable localization of addons and distribution of localized addons without requiring the developer of an addon to do anything other than identify the strings needing localization and submit the addon to AMO.
+|Feature implementation plan=A good deal of work to implement this has already been done by Gandalf - what is missing is the coordination among Jetpack, Gandalf, and AMO as was originally planned. In addition, AMO's time to work on this is very limited and perhaps too far away for us to effectively launch this feature in a timely manner. To that end, we may want to move the "pushing to the 3rd party service" side of this to the Add-on Builder.
+In addition, since most of the hard work has been done, we can launch this in phases:
+Phase 1: we can create a simple way for evelopers to push their xpi, on their own, to Transifex. This would allow us to have an l10n option for developers *now*.
+Phase 2: Put the necessary "push to transifex" features into the online builder - perhaps we can connect this to the "push to AMO" functionality we already have.
+Phase 3: When AMO can take on these tasks we can move the push functionality to the AMO side, utilizing the work that the Builder team has already done.
 }}
 {{FeatureInfo