There should be way to feed built in translation memory with strings translated in Weblate. This needs to handle several situations:
Sitewide installation, when all strings are pushed to TM, this is usually desired in the installation used by single company.
Per project or component installation (maybe it could utilize addons) for multi purpose installation such as Hosted Weblate. By installing enabling TM addon, users will get access to it and all their translations will go there. This probably needs some legal framework as well.
The updates should be batched and run in the background. We could reuse code for fulltext index updates, but maybe it's just better to switch to some task queue (which we need anyway, see https://github.com/WeblateOrg/weblate/issues/492). So far I think the best match would be https://github.com/closeio/tasktiger as it supports batching requests, what is perfect fit for translation memory or index updates.
There should be way to feed built in translation memory with strings translated in Weblate. This needs to handle several situations:
The updates should be batched and run in the background. We could reuse code for fulltext index updates, but maybe it's just better to switch to some task queue (which we need anyway, see https://github.com/WeblateOrg/weblate/issues/492). So far I think the best match would be https://github.com/closeio/tasktiger as it supports batching requests, what is perfect fit for translation memory or index updates.