User:Runab WMF/CX-Roadmap

Development plan

 * 1) Improve the server as per the POC to handle requests using socket.io, have all the boiler plate and architecture code(to be evolved in future) https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4023
 * 2) "Load the given article to the editor" should be refactord to a server task https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4024
 * 3) Sent the article title, language pair to server
 * 4) with the response from point 5 Show the article. No UI change. Currently it's loaded by frontend API, directly from MW. Change it to load from CX server after processing.
 * 5) Perform initial processing of the article content at server side
 * 6) Server side responds to UI request by creating an empty "project" in the data store
 * 7) Sentence segmentation (minimal, matching [a-z]\.\s+[A-Z])
 * 8) Save processed article into server-side data store-in the form of data model
 * 9) Serve the data model from the store as version 0.
 * 10) Research on sentence segmentation
 * 11) Segmentation may be with TR29 and other pluggable/expandable methods
 * 12) May also be language-specific
 * 13) Basic segmentation Implementation
 * 14) Block alignment - paragraph, table, image, div, ul, headers alignment in Special:CX
 * 15) ROT13 integration-for debugging and development
 * 16) CX Server tests
 * 17) CI integration
 * 18) Write segmentation tests. Goto step 7 and loop :)
 * 19) UX adaptation for design update-eg: Progress bar stick to tools pane as per latest design from Pau
 * 20) Entry point 1: Red interlanguage link
 * 21) Publishing to user space
 * 22) Design Service provider interface
 * 23) MT Interface
 * 24) Dictionary Interface
 * 25) TM Interface
 * 26) Wikidata interface
 * 27) Wikidata interface implementation
 * 28) MT Interface implementation
 * 29) UI cards infrastructure
 * 30) Support for choosing translation service
 * 31) TM Interface implementation
 * 32) Progress bar calculation implementation
 * 33) Abuse detection
 * 34) Basic reference adaptation support
 * 35) Bubble documentation in GuidedTour style
 * 36) Dictionary interface implementation
 * 37) Start with some existing dictionaries
 * 38) Redis data store modeling
 * 39) Persistence configuration
 * 40) Data model diff design and implementation - Do not send the whole data model every time
 * 41) Preprocessing - Clean up
 * 42) Remove Table of contents, preprocess templates
 * 43) Think about "transcoding templates" in an analogous way to link handling
 * 44) Table support
 * 45) Infobox support
 * 46) Capturing edits for Machine learning
 * 47) Translation center
 * 48) Suggest articles to be translated
 * 49) Entry point: New translation from Contributions page
 * 50) Support for re-editing a saved draft
 * 51) Notify when an article the user is translating has been created
 * 52) Auto-save translations
 * 53) Allow collaborative translation
 * 54) Add content to existing articles

Special:ContentTranslation

 * Done: Loading source article
 * Done: Segmentation
 * Done: Editing target article section-by-section
 * Done: Publishing the translated article to user space in target language

Translation tools

 * Translation memory
 * Automatic links insertion

Backend

 * Done: Loading source article
 * Cleanup of the source article from unneeded markup
 * Segmentation
 * Initial caching of the source article segments in the backend (Redis)
 * Saving the segment translations
 * Done: Publishing
 * Generic interface to language services (TM, MT, dictionaries, Wikidata, etc.)
 * Interface to translation memory
 * Interface to Wikidata

QA plan

 * Manual Testing
 * Browser tests for Special:ContentTranslation
 * Done: Browser tests for the red link entry point dialog
 * Unit tests for the backend

Analytics

 * Prepare UI event logging, translation statistics and translation tools usage according to the analytics plan