Re: GNOME Moduleset Reorganization vs. L10N

[Shaun McCance <shaunm gnome org>]

On Fri, 2010-10-15 at 12:59 +0300, Dimitris Glezos wrote:
> On Fri, Oct 15, 2010 at 12:42 PM, Johannes Schmid <jhs jsschmid de> wrote:
> >> Starting from 1.0, Transifex no longer forces commits to VCS. Yay. :-)
> >
> > We want forced commits! We don't want people to care about translations
> > unless they are translators because we found out in the past that some
> > won't care.
> >
> > If the maintainer has to commit translations manually - that's a pain!
> 
> Yeah, this is a common challenge with maintainers. =)
> 
> The command-line tool can be quite flexible though. Here are some
> proposed workflows:
> 
>  1. Language leaders can run something like `tx pull --release
> gnome/3-0 --language pt_BR` and mass-commit their language before the
> translation deadline, for example.

Is that something that's done per-module? Our release sets
have well over 100 modules. That would be a real pain for
translators.

Also, there's no real translation deadline in Gnome. The
deadline is the release. And we want the translations to
be in all the unstable releases as well. They should be
available in git (or wherever) as they are updated.

>  2. Developers can put into their 'make release' Makefule rule the `tx
> pull` command, which exports all translation files from Tx.

I would really prefer distcheck not to hit the network.

>  3. We can easily setup a script to do all these in a batch mode once
> per day, or even dynamically using a web hook.

I think this is the only thing that would work for Gnome.
A daily cron job (or maybe twice-daily) seems reasonable,
but I'd be worried about missing last-minute translations
in our releases. Perhaps we'd have to implement an actual
translation deadline.


-- 
Shaun McCance
http://syllogist.net/