How can we fairly divide translation work and credit contributors?

[Robert_H]

I’m trying to organize a community-driven translation for an open-source app, but I’m stuck on how to fairly divide the work and credit contributors. Some volunteers want to tackle entire sections, while others can only do small chunks, and I’m worried the inconsistency will cause friction or abandoned tasks.

[MatthewC]

We split the work by translation files and let people pick chunks, but the pace varied a lot and some tasks stalled. To fix it we started a simple credits log in the repo that lists who touched which file and when, and we tracked a weekly count of completed strings. It helped turnout a little, but not magically.

[Tyler10]

Trying to hand whole sections to a single person sounded right at first, but when someone dropped off, the rest panicked about slowing the whole project. We ended up reassigning and it felt a bit like shuffling chairs.

[Anthony80]

Is the real problem just the workload split or maybe we’re missing a clear sense of what 'done' looks like? I keep wondering if something else—communication loops, response times, or incentive—is really the bottleneck.

[Paul_T]

Microtasks with tiny reviews helped keep people in, even if they only had a few minutes. Some folks liked noticing tiny wins, others hated the review back-and-forth. We tried a couple of small tweaks and parked some ideas.