Re: Using two translation workflows for one module

[Debarshi Ray <debarshi ray gmail com>]

> If it
> gets translated elsewhere, then it should not get into gnome without
> language team approval, if it exists.

This is the part that I do not understand. Does getting into GNOME
mean using GNOME infrastructure or being an official module. Solang is
not an official module. The reason for using git.gnome.org is one of
convenience and alignment. eg., getting our Mallard documentation
reviewed, staying upto date with the GNOME Goals, etc..

> Just consider hundreds of one time launchpad clickers, updating the
> work of organized gnome team (to be clear; not all of launchpad users
> are clickers of course).

I do not know about Launchpad because I have never used it. But in
Transifex.net developers have the option of allowing anyone to submit
or require that new translators or teams ask for permission. Solang
requires that new translators/teams ask for permission.

> Solang is being translated by the same team as other gnome
> translations to Slovenian, no matter where it is hosted, because it's
> a good project. It just isn't updated regularly, because no-one
> remembers to check it on transifex.

Good point.

The problem with Tx.net is that there is no way a developer can
communicate directly with the l10n community. Ofcourse translators are
notified by Tx about string changes, but it is hard for me to say "Hey
here is a new program and I would like to have translations for it". I
am told work is on to add this feature to Tx.

> If developers state: "Therefore in cases of conflicts (we have not had
> any till now) I plan to give preference to
> the submissions from Damned Lies.", then there should really be no problems.

That is a good way to move forward and work together, yes.

Cheers,
Debarshi
-- 
One reason that life is complex is that it has a real part and an
imaginary part.
    -- Andrew Koenig