Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Switch from Transifex to Weblate infrastructure #111
Proposal: Move from using Transifex to translate the project to Weblate (non-self-hosted instance). Note that Weblate hosted (vs self-hosted) would likely be free given their Gratis for libre projects pricing.
Implementer(s): @erciccione (mentioned in Slack that they'd be happy to help, has experience moving from Pootle to self-hosted Weblate), myself, and/or those who implemented Transifex (was thinking mainly for feedback / lessons learned, but if they want they can set up the config too). Weblate admins and language maintainers would be the same as Transifex.
Testing: Before executing the migration itself, as suggested by y3v63n we'd be having "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"
Why should the Bisq community care about improving our localization tools?: Apart from maybe adding new fiat processing methods, localization is arguably the biggest factor in improving liquidity. Don't believe me? Look at other language based issues where you hear things like this:
But we already have Transifex and it works well enough. Why should any effort be put into moving to another tool when we could spend it elsewhere?:
But I'm already here in the config panel and I know the project name, why not just let me type and subscribe? Weblate gets this:
A proprietary mindset leads to proprietary design which is at odds with FOSS collaboration ideals. Take for example Huey today highlighted in Slack for Persian/Farsi localizers to look at strings like this. Let's say I'm on mobile and just want to look at the string in question. Can't, because you have to have to be logged into an account to look at anything. Even when I'm logged in on PC it doesn't let me look at how the Persian/Farsi speakers translated it, only 'my' language, Japanese. Weblate you don't need to be logged in to view and can easily see how other people might have syntactically styled things:
Probably the biggest quality of life improvement from a localizer viewpoint that I've come across is that Weblate nicely marks up when a string has been modified, no clicks to show the diff required:
Transfiex on the other hand requires that you click around in Translation Memory:
In Summary: Moving to Bisq gives us among other things: the ability to fix or add features to our tool (or otherwise bountify), free advertising to other fellow FOSS contributors which can turn into more Bisq localizers, and a better UX which leads to better productivity. We can further improve the liquidity offered on Bisq by switching from Transifex to Weblate.
@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.
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.
Thanks for your feedback! I've updated the issue to address all of your concerns I believe apart from the outdated look you mentioned.