Translation workflow in GitLab
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
What
For the past few days I've been doing translation work inside Crowdin, adding translations and approving them. I've also been helping to externalize strings in the GitLab codebase. Along the way, I am switching back and forth between Crowdin and GitLab, looking at the GitLab codebase, and having conversations with collaborators in both places. It's not a great experience because it's not integrated. I think there's opportunity for improvement.
Opportunity
I think the opportunity is huge here since DevOps is really becoming the software development standard, and internationalization/localization efforts are critical for organizations to scale their software across the world, with GitLab itself being a classic case of this. In my personal experience in these past few days, sometimes I don't know whether a string has been externalized or not, or whether it's a translation problem, and I'm also translating three different but related languages (that's probably an edge case). So there's a lot of friction from switching around. Making this smoother would increase adoption of these tools and ultimately help more people translate.
MVC
I'm not sure what an MVC would look like. It seems like any proposal of integration would require a lot of work. I'll keep thinking about it. If anyone reading this can think of something small, please suggest it. Or if GitLabbers here want to close this issue since it's not feasible anytime soon, please do.