Il giorno mar, 20/01/2009 alle 11.32 +0100, Marcel Telka ha scritto:
In all cases, when a translation is locked for too long time some
administrative intervention is needed.
Comment for Vertimus authors: Today it is not possible for me (as a
coordinator) to unlock such stuck translator and
On Tue, Jan 27, 2009 at 10:53:16AM +0100, Luca Ferretti wrote:
Il giorno mar, 20/01/2009 alle 11.32 +0100, Marcel Telka ha scritto:
In all cases, when a translation is locked for too long time some
administrative intervention is needed.
Comment for Vertimus authors: Today it is not
El mar, 20-01-2009 a las 04:47 +0200, Gintautas Miliauskas escribió:
Hello,
The consistency matters, and
I've difficulty understanding how real consistency could be maintained in an
open group of volunteers where people are constantly changing the modules
they translate.
You need
El mar, 20-01-2009 a las 12:10 +0100, Luca Ferretti escribió:
Il giorno lun, 19/01/2009 alle 09.33 +0100, Marcel Telka ha scritto:
Hi all,
In our localization team (Slovak) we are working in a way where a module
is assigned to particular translator. So it is not allowed to _anybody_
Hi all,
In our localization team (Slovak) we are working in a way where a module
is assigned to particular translator. So it is not allowed to _anybody_
(e.g. other translator) to submit updated translation.
The reasons are:
1. To have one person responsible for the translation.
2. To maintain
On Mon, Jan 19, 2009 at 09:58:38AM +0100, Stéphane Raimbault wrote:
2009/1/19 Marcel Telka mar...@telka.sk:
Hi all,
In our localization team (Slovak) we are working in a way where a module
is assigned to particular translator. So it is not allowed to _anybody_
(e.g. other translator) to
Then, we can ask coordinators to write their workflow in some
live.gnome.org wiki page, try to figure out some basics workflows that
suite some of them (to not have n (n as number of teams) workflows).
Don't know if adds a lot of code and redesign in Vertimus though ...
Cheers,
El dl 19 de 01
Le lundi 19 janvier 2009 à 10:42 +0100, Marcel Telka a écrit :
On Mon, Jan 19, 2009 at 10:33:00AM +0100, Gil Forcada wrote:
Maybe Vertimus can implement different workflows and each coordinator
can assign their workflow to each team.
Then others teams will not see this functionality. And
On Mon, Jan 19, 2009 at 11:22:25AM +0100, Claude Paroz wrote:
Le lundi 19 janvier 2009 à 10:42 +0100, Marcel Telka a écrit :
We could live without it (as we did till today). I ma considering it
only as a nice to have.
This might be related to
On Mon, Jan 19, 2009 at 10:49:01AM +0100, Gil Forcada wrote:
Then, we can ask coordinators to write their workflow in some
live.gnome.org wiki page, try to figure out some basics workflows that
suite some of them (to not have n (n as number of teams) workflows).
Good idea. I think we should
El lun, 19-01-2009 a las 09:33 +0100, Marcel Telka escribió:
Hi all,
In our localization team (Slovak) we are working in a way where a module
is assigned to particular translator. So it is not allowed to _anybody_
(e.g. other translator) to submit updated translation.
We use it as well for
El lun, 19-01-2009 a las 09:58 +0100, Stéphane Raimbault escribió:
2009/1/19 Marcel Telka mar...@telka.sk:
Hi all,
In our localization team (Slovak) we are working in a way where a module
is assigned to particular translator. So it is not allowed to _anybody_
(e.g. other translator) to
12 matches
Mail list logo
