Tails

#4 Updated by drebs 2018-03-19 09:19:37

I just found out that the Debian l10n portuguese team has similar needs than Tails l10n pt-br team, but they use CVS and WML files instead to translate the Debian website.

See a post in the debian-l10n-portuguese list about a proposed graphical flowchart for translation.

Debian has been discusing a transition to Git and they mention Weblate as a possibility.

#5 Updated by emmapeel 2018-03-19 09:29:40

u wrote:
> I don’t think this will be possible with the setup we are creating right now, or is weblate able to have different Git repository inputs for different projects/components?

Currently the only Project we have in weblate is Tails. We could have more. Those projects can have different owners and translator roles.

In each component you can decide a repo and a branch. Currently we have all components liked to the index Component repo, but we could have one repository for each component (*.po file). This inside Tails project and other projects that we could have.

That said, when I did my first round of asking about this to people, not many projects got interested on sharing our install. And the work we do in puppet and Debian could be reused for other projects to have their own instances of weblate too. I am not sure where to go with this issue. Maybe we can discuss it on next meeting and evaluate the different advantages of each proposal.

#6 Updated by emmapeel 2018-03-19 09:48:21

I think that ‘friendly projects’ do:

- transifex mostly

- if they care about opensource, they use hosted.weblate.org
- if they care about privacy, they use their own install

#7 Updated by emmapeel 2018-03-25 07:45:48

I have added a test project with some Debian packages translation.

You can see it at https://translate.tails.boum.org/projects/test-debian/

It cannot push to any directory but it should be refreshed from their repo.

You can check out the changes with for example:

git clone https://translate.tails.boum.org/git/test-debian/gnupg2

#8 Updated by emmapeel 2018-03-26 10:03:29

OK it seems that the whole ‘sharing translation platform’ discussion also happened at the Tor Rome meeting, see:

https://trac.torproject.org/projects/tor/wiki/org/meetings/2018Rome/Notes/LocalizationLinguine

I will join the mailing list they’ve created and find out more about the plan.

#11 Updated by Anonymous 2018-06-12 13:59:11

The way we are implementing our automatization of this platform might be very complicated to actually propose to other projects that we host them. At least, for example for the tails repos, we can create cronjobs etc. But what about the other projects? They would have to follow our guidelines, ask our sysadmins to add puppet code and cronjobs. I don’t think it’s worth it and I’d rather focus on giving them clear instructions on building their own platform.

#12 Updated by emmapeel 2018-06-24 07:26:37

emmapeel wrote:
> I have added a test project with some Debian packages translation.
>
> You can see it at https://translate.tails.boum.org/projects/test-debian/
>
> It cannot push to any directory but it should be refreshed from their repo.
>
> You can check out the changes with for example:
>
> git clone https://translate.tails.boum.org/git/test-debian/gnupg2

This repository has been deleted, so this paragraph is not valid anymore.

The future setup is not able to be shared, so I will close this ticket.

Regarding sharing, I think we should aim for a ‘safe sex’ sharing, sharing glossaries and importing other .po files in tmserver, making them available as suggestions to our translators.