Re: cvs-po-commits-list *still broken*

[danilo gnome org (Danilo Åegan)]

Today at 13:12, Ross Golder wrote:

> My first thoughts are to build on the 'check-po-commit.sh' script so
> that it identified the po file being updated *and* the module it is
> being updated in. We can then (using some kind of lookup tables, or mail
> aliasing scheme) look up the translation team for that language, and the
> maintainer of the module, and fire off a brief e-mail with a subject of
> 'module/po/xx.po file changed by <cvslogin>' and a patch attached.
> Should be achievable with some basic shell scripts, or it might be worth
> re-coding it in python/perl or something.
>
> Thoughts? Ideas? Offers of help? :)

Wonderful idea!  If Bugzilla sits on the same server, we might even
use the appropriate component e-mail from l10n product: if there is no
official contact for l10n product for a certain language, we could
issue a mail to gnome-i18n. We generally require all translation
teams to have a working Bugzilla component inside l10n product, so
we'll also notice these missing Bugzilla components as well.

The only thing I'd like to avoid is having a patch attached: patches 
to PO files sometime contain a lot of uninteresting data, such as
changes to source references.  Well, I may work on a PO diff tool
which would output only interesting changes, so that's also where I'd
be willing to help.

Cheers,
Danilo