Page MenuHomeLubuntu Development

Get translations going again
Stalled, Needs more Info, HighPublic

Description

We really need to get translations going again so people can contribute that way.

There's a few problems at the moment with the way we do translations. Launchpad doesn't have support for translations in Git repositories yet, and while Weblate did work for .desktop files where we always knew the location, with the Lubuntu Manual, the main problem was really that the content changes so much and we don't have a good way to scour the subdirectories natively in Weblate (that's how Weblate supports translations; per-directory, and you can't just set a "recursive" flag).

So we can either get the Weblate instance going again and task @lynorian with manually adding new chapters and such to be translated, as well as keeping on top of updating the translations and importing new ones, or we can find a different solution that works better for us in the long run.

Event Timeline

tsimonq2 triaged this task as High priority.Aug 2 2019, 8:31 PM
tsimonq2 created this task.

I find it convenient, if we have other things in other languages, also have the manual. I worked a lot on this before the server failed, it won't be a problem to do it again.

What would manually adding stuff entail?

You have to use the web GUI and manually add each one. Takes about 30-60 seconds each.

I don't remember offhand exactly what it looks like.

wxl added subscribers: teward, wxl.Jan 31 2020, 5:48 PM

I'm adding @teward here as ultimately this becomes an issue of needing to set up Weblate again. I don't think we have a task for doing that. Is there any reason to think this would be particularly difficult or problematic?

apparently, there are problems to work weblate in the infrastructure, but it is better that he explain it.

teward added a comment.Feb 2 2020, 5:07 PM
In T104#3084, @Noumeno wrote:

apparently, there are problems to work weblate in the infrastructure, but it is better that he explain it.

Trying to deploy weblate on the main infrastructure, it keeps complaining about not enough resources. I'm investigating other options for now, but unless we can get the infrastructure resources increased accordingly, I'm not sure Weblate will be willing to deploy. (Haven't had too much time to dig into this, email's been the primary focus for now).

teward claimed this task.Feb 2 2020, 5:15 PM
teward added a project: Restricted Project.Feb 2 2020, 5:41 PM
wxl added a comment.Feb 2 2020, 5:58 PM

@teward could this be as simple as provisioning additional resources from the host? Which resource(s)?

teward added a comment.Feb 2 2020, 6:01 PM
In T104#3088, @wxl wrote:

@teward could this be as simple as provisioning additional resources from the host? Which resource(s)?

The error message about not enough resources was more cryptic than some of my most vague techie statements in existence. It basically gave *no useful information*. But if we want to talk about resources I'mma just share this:

We probably could use more RAM, but the core problem I see on the main infra box is we're 85% full on our hard drive space, we might need to expand the disk size. That said, that's a @tsimonq2 thing.

Failing increasing disk and RAM, I've been freeing up resources on my own infrastructure here at home and have been attempting to spin up enough resources to launch a dedicated 2GB VM for Weblate and then going to try deploying it fresh there.

This is being placed On Hold for now per @wxl

There are not enough free/available resources on the system to handle a Weblate instance. LC is currently discussing how to proceed.

teward changed the task status from Open to Needsinfo.Feb 4 2020, 10:49 AM