Here's my commit: https://gerrit.wikimedia.org/r/c/mediawiki/services/cxserver/+/1127084

Hi, DeepL is a proprietary machine translation service and their API key has a price associated with - at least to use in the scale of current traffic of cxserver. For such external Machine translation services, we(WMF) usualy has a partnership. For example, to use Google API, WMF and Google has partnership agreement. For DeepL too, we will need such agreement(legal, branding, pricing).

It is also not clear whether you are using cxserver with DeepL in a private usecase outside Wikimedia translation service. Can you please clarify?

We (Openfox) are company building knowledge systems, on top of Mediawiki framework. Our customers using ContentTranslation extension with cxserver, and using deepL as MT provider.

We already hack the source code to meet our needs, but prefer to add this code to the mainstream, allowing others use it, and us better maintaining of it.

Thanks for that context. For the reasons I explained above, my advice would be to have DeepL client in your customized version and not in the upstream. Currently, our team or organization does not have a collaboration with DeepL. If this situation changes, we will definitely consider your client code. Thanks!

The CX, CXServer project's roadmaps and features are optimized for Wikipedia. As far as I know, yours is first non-WMF use of it. Thanks for letting us know. It is free and opensource software and you are free to use it as per its license, however please be aware that we currently do not promise backward compatibility or stability for external usecases.

What a honor to be the first!

I understand and respect that, which leads me to the next question – would the cxserver's team be open to considering the proposed change here?