How can we streamline our community translation workflow for an OSS app?

[Logan.S]

I’ve been trying to organize a community-led translation for an open-source app, but the workflow is a mess. We’re using a platform where people can suggest translations and vote on them, but it feels like we’re just getting a lot of conflicting suggestions without any clear way to decide what’s best.

[Charles_C]

We kicked off with a public translation board and a simple upvote, but every week new proposals showed up and nothing converged. It felt like a popularity contest more than quality and some gloss choices dragged on for pages.

[IsabellaEB]

I tried setting up a small review team to triage every week and publish a canonical string. We tracked time to decision and open proposals, but we still hit deadlocks and back-and-forth.

[WilliamKJ]

I drafted a one page rubric with bits like usage frequency and source quality and pasted it in the chat, hoping it would speed things up. People mostly ignored it and kept voting on the snappiest phrasing.

[Camila69]

I think the bigger bottleneck is context. People see a snippet, not where it’s used in the app, so they vote for style instead of function. We added a quick UI context panel and a couple of people seemed to care, but the flood kept coming.

[Emily.S]

We seeded a 'best guess' translation and asked a small group to test, but the feedback loop was weak and a lot of changes got overwritten or shrugged off.

[Isabella74]

Is the real problem the translations or the platform not letting us converge? I keep wondering if we should switch to a doc style feedback thread and see what sticks.