Content translation/Development Plan/Roadmap/CX03Release

Content Translation 0.03 release
See below for the detailed development plan for each of these features

Increase language support (Labs->Beta->Prod)

 * 1) Languages with high-quality support through Machine Translation Engines

Feature Set

 * 1) Entry Point: Red interlanguage link
 * 2) Translation editing tools: dictionary, machine translation, link adaptation, category adaptation, reference adaptation, limited template adaptation
 * 3) Translation dashboard: selection of source and target languages, warning about trying to create an existing article, saving and loading of drafts
 * 4) Machine translation features: Warning about too much machine translation before publishing; Tagging articles that were published with a high threshold of machine translation.
 * 5) Infrastructure improvements
 * 6) Analytics: Listing number of published drafts and articles and information about users who published them.

CX Deployment Plan for 0.03 Release January 2015
Deployment date: TBD

Project: Content Translation Framework

Release: 0.03 (fourth release)

Long-term project roadmap: Content_translation/Roadmap

Language Pairs to be supported:

Release as: Beta Feature

System Architecture
See: https://www.mediawiki.org/wiki/Content_translation/Technical_Architecture

https://www.mediawiki.org/wiki/Content_translation#Workflow_and_Technical_Architecture

https://www.mediawiki.org/wiki/Content_translation

Caching Architecture
The following diagram includes the caching requirements for the CX framework.

https://www.mediawiki.org/wiki/Content_translation/Server_communications_workflow

https://commons.wikimedia.org/wiki/File:CX_ArchitectureV1.svg

Components to be provisioned for production
CX server installation and configuration: https://phabricator.wikimedia.org/diffusion/GCXS/

See Setup: https://www.mediawiki.org/wiki/Content_translation/Setup for detailed information about component, installation and configuation and instructions.


 * Node.js


 * Dictd server (Also see: https://www.mediawiki.org/wiki/Content_translation/Dictionaries)


 * Apertium


 * Extension dependencies:
 * BetaFeatures
 * CLDR
 * EventLogging

Varnish:
 * Backend Services


 * External APIs called by CX
 * Wikidata
 * Parsoid API

Upstart and Systemd scripts are at: https://www.mediawiki.org/wiki/Content_translation/Setup
 * Configuration Scripts

Provisioning Plan
To be determined from discussion with ops To be determined from discussion with ops To be determined from discussion with ops
 * Storage Requirements
 * Hardware Requirements
 * Bandwidth Requirements
 * Performance expectations


 * MT TPS (Transactions per second)
 * User responsiveness
 * MT Round trip
 * General guidelines


 * https://www.mediawiki.org/wiki/Performance_guidelines
 * https://www.mediawiki.org/wiki/Performance_profiling_for_Wikimedia_code

Monitoring and metrics

 * EventLogging activity for CX
 * Number of users enabling the feature
 * Performance of S:CX, backend calls?
 * Check for node and varnish? Who to page?
 * Graph showing requests or timings for the WikiData API(s) we are calling
 * Graph showing requests or timings for the Parsoid API(s) we are calling

External Signoffs Required

 * Faidon - Ops
 * Gabriel - Infrastructure architecture
 * Ori - Performance
 * Chris Steipp - Security
 * Greg G - Release engineering
 * Mark - Ops
 * Tim - Platform

LE Team responsibilities

 * Kartik - Deployment, Engineer
 * Niklas - Engineer, Code Reviewer
 * Santhosh - Engineer, Code Reviewer
 * David - Engineer, Code Reviewer
 * Joel - Engineer, Code Reviewer
 * Runa - Team Scrum-Ninja / testing and communications
 * Pau - Feature UX reviewer, designer
 * Amir - Feature signoff
 * Alolita - Engineering coordination, Eng Manager