Ok, back on the list (sorry for the off-list disgression for the one having interest in it, sorry for this intrusion on the list for the others ;).
Mt.
----- Forwarded message from Martin Quinson <[EMAIL PROTECTED]> -----
Date: Wed, 8 Oct 2003 15:56:13 +0200
To: Fabio Massimo Di Nitto <[EMAIL PROTECTED]>
Cc: Martin Quinson <[EMAIL PROTECTED]>,
Christian Perrier <[EMAIL PROTECTED]>
Subject: Re: apache translator please hold on a few days
From: Martin Quinson <[EMAIL PROTECTED]>
Would you mind if we go back to the ML ? It could be interesting for other
people as well,
On Wed, Oct 08, 2003 at 01:05:57PM +0200, Fabio Massimo Di Nitto wrote:
> On Wed, 8 Oct 2003, Martin Quinson wrote:
>
> > I have two possible solutions for this:
> > - Make a script able to send a given text to all translators. It would run
> > an editor (just as reportbug) and build the mail to all people listed in
> > the po files as translator.
>
> read my comments below :-)
>
> > - Take a new co-DD for the package responsible of the translation. I would
> > be pleased to volunteer on this, but I'm not DD yet. Maybe Christian
> > would accept? The charge of this person would be to act as proxy between
> > the apache devel and the translators wrt mails and l10n bugs. He needs
> > the right to write in the CVS containing the package to do his job.
>
> The fact that you are not a DD is not an issue at all and your help would
> be great but when i pointed out the problem it was with a more generic
> target than just apache. Anyway for apache and apache2 you are welcome to
> join us. To get access to the different repositories please join us on
> irc.oftc.net #debian-apache and we will coordinate. since i do not handle
> the access to the repositories directly.
Ok, I'll do that.
But the point is that I tried to find a rapid fix for your perticular
situation. Of course, fixing it for Debian as a whole needs a much more
complete solution.
> > A third solution could be to use a README.translators file placed in debian/
> > or debian/po/ to communicate with them. But it does not solve your problem
> > with having to deal with the answers of all of them (neither does the first
> > solution).
>
> This cannot work since it is still released with an upload. translators
> should be somehow able to interact before an upload, dealing with
> situations like this one in which urgency was a "requirement" and so on...
> i find difficult to find the right balance to make everyone happy, and in
> certain situations it ends up with a dog that bite its own tail.
>
> > I'm very interrested in your advice of what system would be the best to ease
> > interactions between packagers and translators. I think we need a bit of all
> > three solutions ;)
>
> mmm the situation has to be evaluated from several point of views and it
> is not easy at all to solve.
>
> imho the second solution applied to a global (Debian) scale would be nice
> but it hits 2 big limits:
>
> 1) not all the packages are maintained via a shared system (CVS, svn,
> whatever)
>
> 2) do we have enough translators to assign to each package as "gateway"
> between the Maintainer and the translation teams?
>
> The first problem is impossible to solve. We cannot force anyone to use a
> shared system neither we can bloat alioth with all the packages in Debian.
>
> The second can be probably solved "hiring" different translators from
> different teams.. the coordinator doesn't need to come necessarly from the
> french team or the italian team... the main issue in my opinion is that
> the coordinator must be able to understand what is going on in the
> package not only in terms of templates/translations. This would be a
> requirement imho. Just imagine if a very urgent upload needs to be done
> and templates are changed or in similar situations like it happened with
> apache and the coordinator start translating crap triggering all the
> teams.... hmm you can see the mess yourself.
>
> i hounestly have no idea on how to improvite on a huge scale because the
> process itself is extremely dynamic... but it might be a challenge to find
> a solution... i need to think about it with a bit more quitness..
My solution is to put all translatable material within Debian in a big CVS,
and make the proper tools to ease first the interaction of the translators
with this beast, and then the interaction of the DDs and this beast. The
beast would allow to uncouple the interactions between DD and translators to
allow each groups to organize their work in the much appropriated way to fit
their needs. My thought are detailed in
http://lists.debian.org/debian-i18n/2003/debian-i18n-200309/msg00077.html
I did not realize that this needs a way for maintainer to give advices to
translators about the urgency of the translation, but I'll think about that.
It sounds feasible if maintainer use a script to put their material manually
to the DB (as opposed to getting the material automatically extracted from
the packages).
Thanks, Mt.
--
Je préfère glisser ma peau sous les draps pour le plaisir des sens
que la risquer sous les drapeaux pour le prix de l'essence.
----- End forwarded message -----
--
- Les morts ne sont plus ici et ils ne votent pas, j'en ai peur.
- Vous vous trompez. Ils sont ici et ils votent. On appelle ça la
tradition et ils ont majorité à vingt contre un.
-- Johny Maxwell (Terry Pratchett)
pgp3e0G8oCkNz.pgp
Description: PGP signature
