AMO Localizaiton Tool

From MozillaWiki
Jump to: navigation, search

Start of project

  • Project sponsors
    • Wil Clouser
    • Seth Bindernagel
  • Main contact
    • Wil Clouser
    • Seth Bindernagel
    • Gandalf
  • Main WebDev contact
    • Wil Clouser
  • Main QA contact
    • TBD
  • Main third party contact (if developed externally)
    • Perhaps Gandalf?
  • Final application owner/maintainer
    • Wil Clouser, Seth Bindernagel, and Gandalf

Overall goal of the project

To develop a tool that AMO developers can choose to use if they'd like to localize their add-ons.

Pre-requisites needed (technology, server capacity, staffing, monitoring, response time, etc)

The project will require a developer who can dedicate time to understanding the complexities of building an AMO localization tool. The developer will also need to know how AMO uniquely uses .po files and how to work with SVN.

Create a development environment with access to SVN and AMO.

Staging server to serve the tool and test.

Main Tool

  • Easily extensible for FF files, .po files, AMO db, and AMO metadata API
  • Automates viewing, translating, and maintaining the translation. Specifically, automatically pulls the English gettext files from AMO. Then, allows for translation and maintaining of a translation.
  • Translation memory and libraries?
  • Localizers can:
    • upload .po files (and create .mo files)
    • Able to edit .po files online
      • paginated, filtered, whatever
    • Able to add comments or flag localizations for review for other localizers
    • Review "suggestions" from public
  • Some nice extras:
    • AMO API could serve as a conduit for the meta-data and developers who don't have a plan for the add-ons themselves.
    • AMO localization integrated into a centralized dashboard where people can see percentage of localization per locale and help localize right from the web.
    • Provide a way for add-on authors to connect to localizers (opt-in) to provide an easier way for them to translate their add-ons and meta-data.

Users

  • Anyone can, for any locale:
    • View statistics
    • See which parts of projects need attention
    • See any new relevant news (feed off newsgroups, RSS, etc.)
  • Guest users (authenticated, but no cvs form on file) can, for any locale:
    • Elect to localize a string from locale X to locale Y. (X=English by default)
      • Can either be one at a time or many
      • Changes become "suggestions" for a localizer to review
    • View other users suggestions and live localizations and vote on quality (or flag for review)
    • How involved do we want anonymous users? Will allowing anonymous translations become a burden for localizers to review? Should localizers opt-in to allowing anonymous users?** Dev environment specs

Milestones and Tasks needed to get to completion

  • 90 days
  • We need to work on this...

Staging Signoff

In order to get an app into staging, the following should be completed:

  • Code committed to Mozilla source control and tagged
  • Initial architecture review by IT and WebDev
  • Site must be password protected
  • Review timeline to go live
  • Review any production requirements so IT can order any new hardware needed

Production Signoff/Launch

  • Final WebDev signoff
  • Final IT signoff
  • Final QA signoff
  • Operations documents filled for support & any training complete
  • Monitors in place