Moving to Weblate? #793
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#793
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I personally don't really like Crowdin¹ :
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 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 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.
As a matter of fact, there is a gitea server which should one day host Plume development, the migration has just never been done
If we can do the migration to gitea soon, I would like to. Is there anything blocking us?
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.
Do you know what the troubles were exactly?
See this thread:
https://github.com/tootsuite/mastodon/issues/10385
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.
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.
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 :)