Content translation/Development Plan/Roadmap/CX02Release
Content Translation 0.02 release
editThe goal of this release is to make the translation process more fluent and provide more flexibility in the way they start to translate. See below for the detailed development plan for each of these features
Increase language support (Labs->Beta->Prod)
edit- Languages with high-quality support through Machine Translation Engines
- Define criteria for enabling new language pairs. Done
- Selection waiting on prelim user testing of production-ready language pairs in Apertium
- Blocked due to technical issues in the infrastructure setup on wikimedia betalabs
Feature Set
edit- New entry Points
- Translation dashboard to initiate and continue translations.
- Auto-saving translation drafts as users translate.
- Initiate translations from dashboard
- Notifications pointing to the dashboard) about relevant translation-related events.
- Entry point to the dashboard from the contributions page.
- Translation dashboard to initiate and continue translations.
- Editor: improved language tools
- Editing
- Keep focus on content for a fluent editing.
- Warnings and options for existing translations.
- Avoid formatting to be added when pasting content.
- Exploration and basic support for the Yandex, Google or Bing API
- Category adaptation
- Better support for links:
- Red links support
- Handle link adaptation for disambiguation pages
- Creating links and editing their target
- Editing
- Infrastructure improvements
- Make it ready to be deployed.
- Analytics:
- Content Translation publishing data
- Visualization (basic)
Auto-saving translation drafts
editFrom gerrit:172528: this is about translation drafts. A translator can save translation and resume later. The draft content is annotated html with segmented sections and sentences (also lot of other data in DOM that represent a state in translation workflow). This drafts won't be available as articles but it can be opened in translation editor and resumed, published.
Drafts can be resumed from any OS, browser, any wiki, any machine, any other translator (this is futuristic) from content translation central dashboard.
Production Deployment - Resources & Provisioning
editMilestones
editCompletion Date/Milestones | Features | Sprints |
---|---|---|
October 8 - October 21 2014 |
|
76 |
October 22 - November 4 2014 |
|
77 |
November 5 - November 18 2014 |
|
78 |
Development Plan
editFeature | Details |
---|---|
Entry Points |
|
Editor |
|
Link and Category Adaptation |
|
Translation Dashboard |
|
Machine Translation Support (mt) |
|
Dictionary Support | |
Templates Support | |
Architecture (technical feature) | |
Research and preliminary development | |
Analytics |
|
Deployment |
CX Deployment Plan for 0.02 Release November 2014
editDeployment date: TBD
Project: Content Translation Framework
Release: 0.02 (third release)
Long-term project roadmap: Content_translation/Roadmap
Language Pairs to be supported:
Release as: Beta Feature
Overall Plan
editSystem Architecture
editSee: 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
editThe 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
editCX server installation and configuration: https://git.wikimedia.org/markdown/mediawiki%2Fservices%2Fcxserver.git/HEAD/README.md
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
- Backend Services
Varnish:
- External APIs called by CX
- Wikidata
- Parsoid API
- Configuration Scripts
Upstart and Systemd scripts are at: https://www.mediawiki.org/wiki/Content_translation/Setup
Provisioning Plan
edit- Storage Requirements
To be determined from discussion with ops
- Hardware Requirements
To be determined from discussion with ops
- Bandwidth Requirements
To be determined from discussion with ops
- 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
edit- 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
edit- Faidon - Ops
- Gabriel - Infrastructure architecture
- Ori - Performance
- Chris Steipp - Security
- Greg G - Release engineering
- Mark - Ops
- Tim - Platform
LE Team responsibilities
edit- 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