[bisq-network/proposals] Switch from Transifex to Weblate infrastructure (#111)

y3v63n notifications at github.com
Mon Sep 2 13:40:12 UTC 2019


@sanecito Thanks for your proposal!

I would like to add my input here.

There are certainly advantages of using a FOSS tool over Transifex, yet I would proceed with caution. I believe there should be value in migrating rather than just doing it for the sake of using an open-source platform.

1. We do have a free Transifex licence, and there are no plans to acquire a paid license for any tool right now. Therefore, we would need to choose the Self-Hosted option for Weblate, leaving us without the "Free advertising" feature and requiring someone to host and maintain the Weblate server.

2. There is no guarantee that if we want to request a feature, it would be implemented any time soon unless there is enogh interest in it from other projects as well.

3. Interface-wise Weblate looks a bit outdated, imo. Transifex is definitely more convenient to work with, though it is far from perfect as well. At the same time, as you mentioned, the markup of changed strings is better implemented in Weblate.

This being said, I don't want to discourage anyone from exploring other tools and improving translators experience, but I would like to suggest that if the proposal is supported, we should give it a series of test runs first by launching a couple of test projects (for software and website) and having everyone involved in translations and @ripcurlx who pulls the translations in the app expressing their opinion.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/111#issuecomment-527152043
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190902/5bc4ce8b/attachment-0001.html>


More information about the bisq-github mailing list