RFE: Vertimus and assigned translator
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 consistency of the whole translation of a module. 3. The bugs routing is simple. I would like to see an optional feature in Vertimus where a team coordinator could assign one of translators to a particular module. This would mean that only this translator could perform "Reserve for translation" action. Even better, the "Reserve for translation" action will not be required at all. Any comments? If it is reasonable I'll file RFE. Thanks. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
2009/1/19 Marcel Telka : > 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. In which goal? Have a module untranslated because the responsible is on vacation :) > 2. To maintain consistency of the whole translation of a module. It's for this reason that the French team has migrated from this model where some people were responsible of a few modules, because it was very difficult to achieve consistency across the GNOME environment. > 3. The bugs routing is simple. I don't know why... Stéphane ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 the same for the Slovak team if they don't want to directly mark a translation as submitted if a committer user uploads directly a translation marked as translating. Makes sense? Cheers, El dl 19 de 01 de 2009 a les 09:58 +0100, en/na Stéphane Raimbault va escriure: > 2009/1/19 Marcel Telka : > > 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. > > In which goal? > Have a module untranslated because the responsible is on vacation :) > > > 2. To maintain consistency of the whole translation of a module. > > It's for this reason that the French team has migrated from this model > where some people were responsible of a few modules, because it was > very difficult to achieve consistency across the GNOME environment. > > > 3. The bugs routing is simple. > I don't know why... > > Stéphane > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
On Mon, Jan 19, 2009 at 09:58:38AM +0100, Stéphane Raimbault wrote: > 2009/1/19 Marcel Telka : > > 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. > > In which goal? > Have a module untranslated because the responsible is on vacation :) We are far away from 100 % translated. So no issue now. :-) There is nothing like "vacation" in this voluteering project. Personally, my translation activity during vacation is higher than during normal working day cycle :-). > > > 2. To maintain consistency of the whole translation of a module. > > It's for this reason that the French team has migrated from this model > where some people were responsible of a few modules, because it was > very difficult to achieve consistency across the GNOME environment. Maybe we will migrate from this model somewhere in the future too. Who knows? :-) > > > 3. The bugs routing is simple. > I don't know why... Because everybody knows who should care about the bug. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 de 2009 a les 10:42 +0100, en/na Marcel Telka va escriure: > 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 the same for the > > Slovak team if they don't want to directly mark a translation as > > submitted if a committer user uploads directly a translation marked as > > translating. > > > > Makes sense? > > Yes. Definitively. But I do not want to vaste Vertimus developer's > resources if this "our" feature will be used only by our team. > > We could live without it (as we did till today). I ma considering it > only as a "nice to have". > > Thanks. > > > > > Cheers, > > > > El dl 19 de 01 de 2009 a les 09:58 +0100, en/na Stéphane Raimbault va > > escriure: > > > 2009/1/19 Marcel Telka : > > > > 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. > > > > > > In which goal? > > > Have a module untranslated because the responsible is on vacation :) > > > > > > > 2. To maintain consistency of the whole translation of a module. > > > > > > It's for this reason that the French team has migrated from this model > > > where some people were responsible of a few modules, because it was > > > very difficult to achieve consistency across the GNOME environment. > > > > > > > 3. The bugs routing is simple. > > > I don't know why... > > > > > > Stéphane > > > ___ > > > gnome-i18n mailing list > > > gnome-i18n@gnome.org > > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > > -- > > gil forcada > > > > [ca] guifi.net - una xarxa lliure que no para de créixer > > [en] guifi.net - a non-stopping free network > > bloc: http://gil.badall.net > > > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 the same for the > Slovak team if they don't want to directly mark a translation as > submitted if a committer user uploads directly a translation marked as > translating. > > Makes sense? Yes. Definitively. But I do not want to vaste Vertimus developer's resources if this "our" feature will be used only by our team. We could live without it (as we did till today). I ma considering it only as a "nice to have". Thanks. > > Cheers, > > El dl 19 de 01 de 2009 a les 09:58 +0100, en/na Stéphane Raimbault va > escriure: > > 2009/1/19 Marcel Telka : > > > 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. > > > > In which goal? > > Have a module untranslated because the responsible is on vacation :) > > > > > 2. To maintain consistency of the whole translation of a module. > > > > It's for this reason that the French team has migrated from this model > > where some people were responsible of a few modules, because it was > > very difficult to achieve consistency across the GNOME environment. > > > > > 3. The bugs routing is simple. > > I don't know why... > > > > Stéphane > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > -- > gil forcada > > [ca] guifi.net - una xarxa lliure que no para de créixer > [en] guifi.net - a non-stopping free network > bloc: http://gil.badall.net > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 the same for the > > Slovak team if they don't want to directly mark a translation as > > submitted if a committer user uploads directly a translation marked as > > translating. > > > > Makes sense? > > Yes. Definitively. But I do not want to vaste Vertimus developer's > resources if this "our" feature will be used only by our team. > > 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 http://bugzilla.gnome.org/show_bug.cgi?id=118852 So I suggest those teams interested by this type of workflow to indicate their interest in comments of this bug. And yes, such an implementation would require substantial work in Damned Lies. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 http://bugzilla.gnome.org/show_bug.cgi?id=118852 > > So I suggest those teams interested by this type of workflow to indicate > their interest in comments of this bug. Thanks Claude, I added my interest there. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 start with the current intended Vertimus workflow documented. The alternative workflows could be added later. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 the Spanish translation team. > > The reasons are: > 1. To have one person responsible for the translation. > 2. To maintain consistency of the whole translation of a module. We use it especially for this reason. > 3. The bugs routing is simple. > > I would like to see an optional feature in Vertimus where a team > coordinator could assign one of translators to a particular module. > > This would mean that only this translator could perform "Reserve for > translation" action. Even better, the "Reserve for translation" action > will not be required at all. > > Any comments? I suscribe it. > > If it is reasonable I'll file RFE. > > Thanks. > -- Jorge González González Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
El lun, 19-01-2009 a las 09:58 +0100, Stéphane Raimbault escribió: > 2009/1/19 Marcel Telka : > > 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. > > In which goal? > Have a module untranslated because the responsible is on vacation :) As Marcel pointed out, many times during vacation there are even more translation commits. > > > 2. To maintain consistency of the whole translation of a module. > > It's for this reason that the French team has migrated from this model > where some people were responsible of a few modules, because it was > very difficult to achieve consistency across the GNOME environment. When you have a lot of people entering and leaving the team you don't get that consistency, since they have to learn the workflow and the style guides, which usually takes a while. > > > 3. The bugs routing is simple. > I don't know why... > > Stéphane > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Jorge González González Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
Le lundi 19 janvier 2009, à 19:27 +0100, Jorge González González a écrit : > El lun, 19-01-2009 a las 09:58 +0100, Stéphane Raimbault escribió: > > 2009/1/19 Marcel Telka : > > > 2. To maintain consistency of the whole translation of a module. > > > > It's for this reason that the French team has migrated from this model > > where some people were responsible of a few modules, because it was > > very difficult to achieve consistency across the GNOME environment. > When you have a lot of people entering and leaving the team you don't > get that consistency, since they have to learn the workflow and the > style guides, which usually takes a while. I see the potential issue you're highlighting, but at least for the french team, it was still a theoretical issue in the past few years (and we were already using vertimus): the fact is that newcomers nearly always ask how they can help first, and so they don't go and reserve modules without asking. Now, maybe it's a real issue for another team, in which case it's important to say that you're experiencing it :-) Vincent -- Les gens heureux ne sont pas pressés. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
Vincent Untz , Mon, 19 Jan 2009 23:14:57 +0100: > Le lundi 19 janvier 2009, à 19:27 +0100, Jorge González González a écrit : > > El lun, 19-01-2009 a las 09:58 +0100, Stéphane Raimbault escribió: > > > 2009/1/19 Marcel Telka : > > > > 2. To maintain consistency of the whole translation of a module. > > > > > > It's for this reason that the French team has migrated from this model > > > where some people were responsible of a few modules, because it was > > > very difficult to achieve consistency across the GNOME environment. > > When you have a lot of people entering and leaving the team you don't > > get that consistency, since they have to learn the workflow and the > > style guides, which usually takes a while. > > I see the potential issue you're highlighting, but at least for the > french team, it was still a theoretical issue in the past few years (and > we were already using vertimus): the fact is that newcomers nearly > always ask how they can help first, and so they don't go and reserve > modules without asking. > > Now, maybe it's a real issue for another team, in which case it's > important to say that you're experiencing it :-) From my experience there're two groups of newcomers (and neither of them could be described as vast majority). The first ones join the translation team with intention to translate particular piece of software, while the second ones join because they just want to help with the translation effort. Either way, it's in general a good idea to assign, if possible, every translator to particular modules, as Marcel said, as well as review the whole message catalog when one is updating translation previously assigned to and translated by someone else. 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. Cheers, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 consistency not only within a single application, but across the whole environment as well, so assigning people to modules only solves half the problem. -- Gintautas Miliauskas ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
Hi! "Gintautas Miliauskas" , Tue, 20 Jan 2009 04:47:28 +0200: > 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 consistency not only within a single application, but across > the whole environment as well, so assigning people to modules only > solves half the problem. It may be so, but then again, it's better than nothing. Personally, I'd apprehend the consistency across the whole environment as a second step towards the consistency perfection. :-) Best, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
On Tue, Jan 20, 2009 at 04:10:18AM +0100, Petr Kovar wrote: > "Gintautas Miliauskas" , Tue, 20 Jan 2009 04:47:28 +0200: > > > 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 consistency not only within a single application, but across > > the whole environment as well, so assigning people to modules only > > solves half the problem. > > It may be so, but then again, it's better than nothing. Personally, I'd > apprehend the consistency across the whole environment as a second step > towards the consistency perfection. :-) +1 :-) -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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_ > (e.g. other translator) to submit updated translation. Marcel, this is currently the same behavior used on Italian team, of course it has the advantages you listed, but please note there is at least one shorcoming: the inability of currently assigned translator to work on assigned/maintained module You can "lock" a translation in current l10n.gnome.org too, just "reserve the translation" immediately after commit. But what will happen if someone will not able to update him/her own translation in time for a release? GNOME Desktop is time based, so some translators in our (Italian) team start working after the string freeze. Sometimes they don't have the time to complete it, so the module is temporary assigned to another person. Note also that in order to temporary reassign a translation, the team coordinator (and his/her privileges on l10n.g.o) could be needed, adding a bottleneck - at least I think so, I have only committer privileges, I don't know if team coordinator can retract a reservation. IMHO, trying to merge the current l10n.g.o behavior and the "assigned" workflow, could be better add a "assigned-to" property to modules. This property could act as follow: * on l10n.g.o each module can be assigned to an account * this account will receive email alerts for each action performed on him/her assigned modules (comments could be useful to notify typos/errors/proposal/memos/other) * if you claim a translation for a module assigned to another account, this one have to "accept" the request * if the "assigned account" don't accept/reject the request within a week, accounts with review (or commit? dunno, but something below coordinator in order to make it faster) privileges can do this * other? Something like this (maybe better, it's just a stub) could be more feasible than a simple lock. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
Hi Luca, On Tue, Jan 20, 2009 at 12:10:53PM +0100, Luca Ferretti wrote: > 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_ > > (e.g. other translator) to submit updated translation. > > Marcel, this is currently the same behavior used on Italian team, of > course it has the advantages you listed, but please note there is at > least one shorcoming: the inability of currently assigned translator to > work on assigned/maintained module The same situation is today when a (random) translator choose "Reserve for translation" and no real progress is done. If I understand current DL & Vertimus correctly everybody is albe to register there and join a L10N team. There is no approval required from the L10N team to accept this new translator. After that, the translator could (b)lock some random translations using neverending "Reserve for translation" operation. What is better? Who knows... :-) > > You can "lock" a translation in current l10n.gnome.org too, just > "reserve the translation" immediately after commit. Exactly. 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 make it available to someone else. > > But what will happen if someone will not able to update him/her own > translation in time for a release? GNOME Desktop is time based, so some > translators in our (Italian) team start working after the string freeze. > Sometimes they don't have the time to complete it, so the module is > temporary assigned to another person. No problem, the process could be workarounded. The SVN commit access is not directly bound to Vertimus. So you could commit translations without Vertimus (as we did for years :-). > > Note also that in order to temporary reassign a translation, the team > coordinator (and his/her privileges on l10n.g.o) could be needed, adding > a bottleneck - at least I think so, I have only committer privileges, I > don't know if team coordinator can retract a reservation. No, see above. > > IMHO, trying to merge the current l10n.g.o behavior and the "assigned" > workflow, could be better add a "assigned-to" property to modules. > > This property could act as follow: > * on l10n.g.o each module can be assigned to an account I agree. > * this account will receive email alerts for each action performed > on him/her assigned modules (comments could be useful to notify > typos/errors/proposal/memos/other) I agree. > * if you claim a translation for a module assigned to another > account, this one have to "accept" the request In this case (at least for me) it is better to move ownership to the new person. > * if the "assigned account" don't accept/reject the request within > a week, accounts with review (or commit? dunno, but something > below coordinator in order to make it faster) privileges can do > this Can do what? Accept the request? I think most of teams are small, so we do not need to complicate things more than needed. :-) > * other? > > Something like this (maybe better, it's just a stub) could be more > feasible than a simple lock. Thanks for your valuable thoughts. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 consistency not only within a single application, but across > the whole environment as well, so assigning people to modules only > solves half the problem. yes, you're right, but that's the work of reviewers, to make the translations of others consistent. Cheers. -- Jorge González González Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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_ > > (e.g. other translator) to submit updated translation. > > Marcel, this is currently the same behavior used on Italian team, of > course it has the advantages you listed, but please note there is at > least one shorcoming: the inability of currently assigned translator to > work on assigned/maintained module > > You can "lock" a translation in current l10n.gnome.org too, just > "reserve the translation" immediately after commit. > > But what will happen if someone will not able to update him/her own > translation in time for a release? GNOME Desktop is time based, so some > translators in our (Italian) team start working after the string freeze. > Sometimes they don't have the time to complete it, so the module is > temporary assigned to another person. In any case, the coordinator or the person with the svn account is still the person in charge to commit the translations, and I belive many teams still work with their old workflow, i.e. sending the pot files to somewhere, and coordinating efforts from their respective mailing lists. Cheers. -- Jorge González González Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
Em Seg, 2009-01-19 às 23:14 +0100, Vincent Untz escreveu: > Le lundi 19 janvier 2009, à 19:27 +0100, Jorge González González a écrit : > > When you have a lot of people entering and leaving the team you don't > > get that consistency, since they have to learn the workflow and the > > style guides, which usually takes a while. > > I see the potential issue you're highlighting, but at least for the > french team, it was still a theoretical issue in the past few years (and > we were already using vertimus): the fact is that newcomers nearly > always ask how they can help first, and so they don't go and reserve > modules without asking. > > Now, maybe it's a real issue for another team, in which case it's > important to say that you're experiencing it :-) > When the pt_BR used a separate Vertimus server, we had some people reserving translations without even saying hello in the mailing list. Sometimes they were just curious, like the pt_BR KDE l1n coordinator, but sometimes the reserved modules for translation, or even worse, uploaded bad translations. Since we moved to the improved Damned Lies, we didn't have such problems. -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 make it available to > someone else. Well, here is a "backdoor" now: committer accounts always have a "Inform of submission" available. This resets the status ;) > > > > IMHO, trying to merge the current l10n.g.o behavior and the "assigned" > > workflow, could be better add a "assigned-to" property to modules. > > > > This property could act as follow: > > * on l10n.g.o each module can be assigned to an account > > I agree. > > > * this account will receive email alerts for each action performed > > on him/her assigned modules (comments could be useful to notify > > typos/errors/proposal/memos/other) > > I agree. Good. Do you have yet opened a bug on bugzilla? > > * if the "assigned account" don't accept/reject the request within > > a week, accounts with review (or commit? dunno, but something > > below coordinator in order to make it faster) privileges can do > > this > > Can do what? Accept the request? Yes, it was just a safe escape from any inability to have network access something like: "the assigner was arrested while traveling in another country and now languish with hunger in a remote prison..." :) But now we have the "inform of submission" backdoor, so it's no longer needed :D ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
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 possible for me (as a > > coordinator) to unlock such stuck translator and make it available to > > someone else. > > Well, here is a "backdoor" now: committer accounts always have a "Inform > of submission" available. This resets the status ;) Yes. I found it several days ago and it is working :-). Thanks. > > > > > > > IMHO, trying to merge the current l10n.g.o behavior and the "assigned" > > > workflow, could be better add a "assigned-to" property to modules. > > > > > > This property could act as follow: > > > * on l10n.g.o each module can be assigned to an account > > > > I agree. > > > > > * this account will receive email alerts for each action performed > > > on him/her assigned modules (comments could be useful to notify > > > typos/errors/proposal/memos/other) > > > > I agree. > > Good. Do you have yet opened a bug on bugzilla? For assigned translator feature: http://bugzilla.gnome.org/show_bug.cgi?id=568770 For emails, not yet. Feel free to file it yourself :-). -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
