Moving to Weblate? #793

Open
opened 2020-06-25 18:37:07 +00:00 by elegaanz · 10 comments
elegaanz commented 2020-06-25 18:37:07 +00:00 (Migrated from github.com)

I personally don't really like Crowdin¹ :

  • it is not open-source/free/libre
  • the CLI tools to manage translations are not that good
  • I often receive private messages proposing to translate Plume in exchange of some money. I'm not against paying contributors, but I don't really like people who don't care about the project getting money out of it (if you are a translator and you want to get some money, I can add you to the Liberapay team).
  • They more or less said to one of our contributors that their account will be closed in a few month, unless they start paying for a premium plan. I really don't like that.

And we now have the possibility to have an Weblate instance hosted for us, by some people who want to help the project, so I would like to ask all the translators if they would prefer to stay with Crowdin or to switch to Weblate.

The only feature Crowdin has that Weblate doesn't, is in context translation, that we are using on https://translate.joinplu.me and https://translate.docs.joinplu.me, but I don't know if these sites are really used? So little poll: did you already used them?

1: When choosing a translation platform, I compared the different solutions that were available, and it seemed to be the least bad, I didn't especially liked it at that time either. And I couldn't host Weblate or something else on the small server that powers https://joinplu.me.

I personally don't really like Crowdin¹ : - it is not open-source/free/libre - the CLI tools to manage translations are not that good - I often receive private messages proposing to translate Plume in exchange of some money. I'm not against paying contributors, but I don't really like people who don't care about the project getting money out of it (if you are a translator and you want to get some money, I can add you to the Liberapay team). - They more or less said to one of our contributors that their account will be closed in a few month, unless they start paying for a premium plan. I really don't like that. And we now have the possibility to have an Weblate instance hosted for us, by some people who want to help the project, so I would like to ask all the translators if they would prefer to stay with Crowdin or to switch to Weblate. The only feature Crowdin has that Weblate doesn't, is in context translation, that we are using on https://translate.joinplu.me and https://translate.docs.joinplu.me, but I don't know if these sites are really used? So little poll: did you already used them? 1: When choosing a translation platform, I compared the different solutions that were available, and it seemed to be the least bad, I didn't especially liked it at that time either. And I couldn't host Weblate or something else on the small server that powers https://joinplu.me.
ahangarha commented 2020-06-25 19:44:30 +00:00 (Migrated from github.com)

I strongly support this suggestion. FLOSS projects deserve to get contributions on FLOSS platform. Not just for translation, I hope the repo also move to gitlab or gitea.

I strongly support this suggestion. FLOSS projects deserve to get contributions on FLOSS platform. Not just for translation, I hope the repo also move to gitlab or gitea.
requiem958 commented 2020-06-25 20:00:24 +00:00 (Migrated from github.com)

I support this change too, crowdin seems to have a good IHM. More, it seems we can translate without an account, maybe this Will attract more contributors.
I personally not use the context translation, so no loss.

I support this change too, crowdin seems to have a good IHM. More, it seems we can translate without an account, maybe this Will attract more contributors. I personally not use the context translation, so no loss.

Not just for translation, I hope the repo also move to gitlab or gitea.

As a matter of fact, there is a gitea server which should one day host Plume development, the migration has just never been done

> Not just for translation, I hope the repo also move to gitlab or gitea. As a matter of fact, there is a [gitea server](https://git.joinplu.me/) which should one day host Plume development, the migration has just never been done
elegaanz commented 2020-06-25 20:22:41 +00:00 (Migrated from github.com)

If we can do the migration to gitea soon, I would like to. Is there anything blocking us?

If we can do the migration to gitea soon, I would like to. Is there anything blocking us?
splacat commented 2020-06-25 20:32:43 +00:00 (Migrated from github.com)

In the past I was translating Catalan to Mastodon project via Weblate until some troubles with Weblate forced developers to move to Crowding.
I’m used to Crowdin now but anyway, choose the translating platform you like most.

In the past I was translating Catalan to Mastodon project via Weblate until some troubles with Weblate forced developers to move to Crowding. I’m used to Crowdin now but anyway, choose the translating platform you like most.
elegaanz commented 2020-06-25 20:33:39 +00:00 (Migrated from github.com)

Do you know what the troubles were exactly?

Do you know what the troubles were exactly?
splacat commented 2020-06-25 20:41:37 +00:00 (Migrated from github.com)
See this thread: https://github.com/tootsuite/mastodon/issues/10385
elegaanz commented 2020-06-25 20:43:40 +00:00 (Migrated from github.com)

Thank you. Seems like a specific moderation problem, and we shouldn't have the same issue since we don't grant automatic rewards to translators, and because Plume is much "smaller"/less known than Mastodon, so less people are likely to abuse the system.

Thank you. Seems like a specific moderation problem, and we shouldn't have the same issue since we don't grant automatic rewards to translators, and because Plume is much "smaller"/less known than Mastodon, so less people are likely to abuse the system.
verymilan commented 2020-06-25 21:06:31 +00:00 (Migrated from github.com)

I have been asked for an opinion, but I am not sure if i can say anything of value... if Crowding randomly tries to charge contributors like this, it definitely loses points.
Technically i have adapted to it quickly when i did the recent submissions. I cannot say anything about Weblate, i don't recall using it, but i think that i have read its name often.

If it doesn't bring us downsides (do we know that Plume won't grow significantly and won't offer rewards in the future?), or any kind of extra barriers, i'm fine with you changing platforms.

I have been asked for an opinion, but I am not sure if i can say anything of value... if Crowding randomly tries to charge contributors like this, it definitely loses points. Technically i have adapted to it quickly when i did the recent submissions. I cannot say anything about Weblate, i don't recall using it, but i think that i have read its name often. If it doesn't bring us downsides (do we know that Plume won't grow significantly and won't offer rewards in the future?), or any kind of extra barriers, i'm fine with you changing platforms.
meneer commented 2020-06-25 21:28:25 +00:00 (Migrated from github.com)

Apart from all governance related issues, I was quite pleased with using the mobile browser based webclient. Translating all text strings was really very efficient. But since I'm at 100% done now, moving to another platform would not bother me a lot. Most translators are used to switching :)

Apart from all governance related issues, I was quite pleased with using the mobile browser based webclient. Translating all text strings was really very efficient. But since I'm at 100% done now, moving to another platform would not bother me a lot. Most translators are used to switching :)
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#793
No description provided.