Change Details

**Participants**, please read/think about/research these, ahead of time: * Session description: ** Next Steps for Languages and Cross Project Collaboration * Session Goals: ** Find out the Language infrastructure capabilities and opportunities for Wikimedia movement. Identify projects and tasks to meet the strategic goals of Wikimedia in this area. ** ... * Pre-event questions for discussion ** ... ** ... * Related position statements: ** https://wikifarm.wmflabs.org/devsummit/index.php/Session:5 * Related background reading: ** Languages, Machine Translation: *** The [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering | Language Team ]] who was responsible for Language related projects , now does not exist. It is merged to Collaboration team and part of [[ https://www.mediawiki.org/wiki/Global_Collaboration | Global Collaboration team ]] now. The Language infrastructure that the ex-Language team was responsible for, are [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering#Projects | listed here ]] *** The Content translation(CX) system to translate articles between languages - https://mediawiki.org/wiki/Content_translation *** The machine translation service used by the system is a public API provided by cxserveer: https://www.mediawiki.org/wiki/Content_translation/cxserver But used only by Content translation now. *** Currently we have [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Apertium | Apertium ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Yandex | Yandex ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Youdao | Youdao ]] machine translation backends. Apertium is hosted by Wikimedia. Rest of them accessed using their APIs using special API keys. A legal contract exist between WMF and these providers. Discussions to use Google MT is in its final stages. *** ** ... **Topic Leaders** (@Lydia_Pintscher @santhosh) , please * Add more details to this task description, * Coordinate any pre-event discussions (here, IRC, email, hangout, etc), * Outline the plan for discussing this topic at the Developer Summit. * Optionally, include what it will //not// try to solve. * Update this task with summaries of any pre-event discussions. * Include ways for people not attending to be involved in discussions before the summit and afterwards. This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. ---- Post-event Summary: * ... Action items: * ...

**Participants**, please read/think about/research these, ahead of time: Session description: * Next Steps for Languages and Cross Project Collaboration This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. Goals: * Find out the Language infrastructure capabilities and opportunities for Wikimedia movement. * Identify projects and tasks to meet the strategic goals of Wikimedia in this area. * ... Pre-event questions for discussion * ... * ... Related position statements: * https://wikifarm.wmflabs.org/devsummit/index.php/Session:5 Related background reading: * Languages, Machine Translation: ** The [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering | Language Team ]] who was responsible for Language related projects , now does not exist. It is merged to Collaboration team and part of [[ https://www.mediawiki.org/wiki/Global_Collaboration | Global Collaboration team ]] now. ** The Language infrastructure that the ex-Language team was responsible for, are [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering#Projects | listed here ]] ** The Content translation(CX) system to translate articles between languages - https://mediawiki.org/wiki/Content_translation ** The machine translation service used by the system is a public API provided by cxserveer: https://www.mediawiki.org/wiki/Content_translation/cxserver But used only by Content translation now. ** Currently we have [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Apertium | Apertium ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Yandex | Yandex ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Youdao | Youdao ]] machine translation backends. Apertium is hosted by Wikimedia. Rest of them accessed using their APIs using special API keys. A legal contract exist between WMF and these providers. Discussions to use Google MT is in its final stages. ** ** ... **Topic Leaders** (@Lydia_Pintscher @santhosh) , please * Add more details to this task description, * Coordinate any pre-event discussions (here, IRC, email, hangout, etc), * Outline the plan for discussing this topic at the Developer Summit. * Optionally, include what it will //not// try to solve. * Update this task with summaries of any pre-event discussions. * Include ways for people not attending to be involved in discussions before the summit and afterwards. ---- Post-event Summary: * ... Action items: * ...

**Participants**, please read/think about/research these, ahead of time: Session description: * Session description: ** Next Steps for Languages and Cross Project Collaboration * Session Goals: ** Find out the Language infrastructure capabilities and opportunities for Wikimedia movement. Identify projects and tasks to meet the strategic goals of Wikimedia in this area. ** ... This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. Goals: * Pre-event questions for discussionFind out the Language infrastructure capabilities and opportunities for Wikimedia movement. * Identify projects and tasks to meet the strategic goals of Wikimedia in this area. *** ... Pre-event questions for discussion ** ... * ... Related position statements: ** https://wikifarm.wmflabs.org/devsummit/index.php/Session:5 Related background reading: * Languages, Machine Translation: * Related background reading:* The [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering | Language Team ]] who was responsible for Language related projects , now does not exist. It is merged to Collaboration team and part of [[ https://www.mediawiki.org/wiki/Global_Collaboration | Global Collaboration team ]] now. ** ** The Language infrastructure that the ex-Languagese team was responsible for, Machine Translation:are [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering#Projects | listed here ]] *** The [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering | Language Team ]] who was responsible for Language related projects , now does not exist. It is merged to Collaboration team and part of [[ https://www.mediawiki.org/wiki/Global_Collaboration | Global Collaboration team ]] now. The Language infrastructure that the ex-Language team was responsible for, are [[ https://www.mediawiki.org/wiki/Wikimedia_Language_engineering#Projects | listed here ]] The Content translation(CX) system to translate articles between languages - https://mediawiki.org/wiki/Content_translation *** The Content translation(CX) system to translate articles between languages - https://mediawiki.org/wiki/Content_translation The machine translation service used by the system is a public API provided by cxserveer: https://www.mediawiki.org/wiki/Content_translation/cxserver But used only by Content translation now. *** The machine translation service used by the system is a public API provided by cxserveer: Currently we have [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Apertium | Apertium ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Yandex | Yandex ]], [[ https://www.mediawiki.org/wiki/Content_translation/cxserver But used only by Content translation nowMachine_Translation/Youdao | Youdao ]] machine translation backends. Apertium is hosted by Wikimedia. Rest of them accessed using their APIs using special API keys. A legal contract exist between WMF and these providers. Discussions to use Google MT is in its final stages. *** Currently we have [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Apertium | Apertium ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Yandex | Yandex ]], [[ https://www.mediawiki.org/wiki/Content_translation/Machine_Translation/Youdao | Youdao ]] machine translation backends. Apertium is hosted by Wikimedia. Rest of them accessed using their APIs using special API keys. A legal contract exist between WMF and these providers. Discussions to use Google MT is in its final stages. *** ** ... **Topic Leaders** (@Lydia_Pintscher @santhosh) , please * Add more details to this task description, * Coordinate any pre-event discussions (here, IRC, email, hangout, etc), * Outline the plan for discussing this topic at the Developer Summit. * Optionally, include what it will //not// try to solve. * Update this task with summaries of any pre-event discussions. * Include ways for people not attending to be involved in discussions before the summit and afterwards. This is one of the 8 [[https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 |Wikimedia Developer Summit 2018]] topics. ---- Post-event Summary: * ... Action items: * ...