Create development and testing environment for translation memory
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Nikerabbit
	Nov 2 2020, 3:03 PM

Description

In order to improve the translation memory, it should be easy to get an environment for it.

It seems that docker-compose is the way to go these days.

Requirements for the environment:

Status	Assigned	Task
Resolved	None	T195760 Language Annual Plan 2018-2019
Resolved	Nikerabbit	T204818 Language tools maintenance intervention: Improve the quality of translations for Translate extension
Open	None	T101236 TTMServer performance and coverage issues
Resolved	Nikerabbit	T267030 Create development and testing environment for translation memory

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptNov 2 2020, 3:03 PM

Nikerabbit triaged this task as Medium priority.Nov 3 2020, 8:28 AM

Ran setup-03-launch-mediawiki-docker.sh from the docker scripts.

README.md on mediawiki-docker-scripts can be formatted better.
The current setup doesn't use MariaDB, though it should not have an impact on the testing.
Should we add "extensions/UniversalLanguageSelector/composer.json" to composer.local.json?
Should we document, enable and test that XHProf works well?

Yes.
There is https://www.mediawiki.org/wiki/MediaWiki-Docker/Configuration_recipes/Alternative_databases
ULS does not have any non-dev composer dependencies.
I don't believe XHProf will be the tool to evaluate/benchmark different approaches for performance

I was able to get Translate setup with MariaDB also, incase needed. Some notes related to that are here: https://www.mediawiki.org/wiki/User:APatro_(WMF)/Docker_Translate

I think the objectives of this task are met, and we can mark this as done.