canmove, Confirmed users
1,570
edits
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 16:30, 6 April 2012
, 6 April 2012no edit summary
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Add-on SDK Localization API and Service | |Feature name=Add-on SDK Localization API and Service | ||
|Feature stage= | |Feature stage=On hold | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note= | |Feature status note=The full API and web service has been put on hold in favour of a simpler local API for now. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature product manager=David Mason | |Feature product manager=David Mason | ||
|Feature | |Feature security lead=Dan Veditz | ||
|Feature localization lead=Zbigniew Braniecki | |Feature localization lead=Zbigniew Braniecki | ||
}} | }} | ||
| Line 25: | Line 23: | ||
In addition, since most of the hard work has been done, we can launch this in phases: | In addition, since most of the hard work has been done, we can launch this in phases: | ||
Phase 1: | '''Phase 1:''' The initial step is simply to land gandalf's "Common Pool" module. This will allow devs to flag strings to translate with a _("string to translate") - When done, the dev can then upload the xpi to https://l10n.mozillalabs.com/projects/p/mozilla-jetpacks/upload/ and the strings will enter the common pool to be translated, and returned to the developer. | ||
'''Phase 2:''' In this stage we should iterate on the l10n support, including taking a look at localizing html files (a method for hosted html as well as included html). | |||
At the same time, we should look at adding automatic uploads to transifex directly from the Online Builder so that devs don't have to worry about doing that themselves. | |||
'''Phase 3:''' when the AMO devs have time to implement it, we should have the automatic uploads work directly from AMO when a dev uploads his/her xpi to AMO. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||
|Feature priority= | |Feature priority=Unprioritized | ||
|Feature roadmap=Jetpack | |Feature roadmap=Jetpack | ||
|Feature list=Jetpack | |Feature list=Jetpack | ||
|Feature engineering team=Jetpack | |Feature engineering team=Jetpack | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus | ||
|Feature security status=sec-review-needed | |||
|Feature security health=Assigned | |||
|Feature security notes=dveditz | |||
}} | |||
Existing work: | Existing work: | ||
* http://diary.braniecki.net/2011/01/12/jetpack-localization-common-pool-approach/ | * http://diary.braniecki.net/2011/01/12/jetpack-localization-common-pool-approach/ | ||
* http://diary.braniecki.net/2011/01/12/using-common-pool-tutorial/ | * http://diary.braniecki.net/2011/01/12/using-common-pool-tutorial/ | ||