[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Translation Projects, Syncing?
- To: Documentation and Translation <doc at arabeyes dot org>
- Subject: Re: Translation Projects, Syncing?
- From: Abdulaziz Al-Arfaj <aalarfaj at gmail dot com>
- Date: Thu, 31 Mar 2005 10:49:09 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=fRz48lgHMpder9WOobIDfrqrep8KHl/f4Dpyxus7EeyiZS5CCK4YhyArH/Wfl3oc1MI3ZGaazz72273LwPlLqY1+dh3TWaUavQe9+adTr+AqnaoZKHp/0KGWJyk2p6zCAjr2eEVF2xGw8nROEun7s0yG02OJF2SxRKYoDYWYiKM=
On Wed, 30 Mar 2005 21:14:52 +0000, Youssef Chahibi <chahibi at gmail dot com> wrote:
> السلام عليكم،
>
> What do you mean by syncing ? This should applied only for projects that have
> been already 100 % translated which will have to be "synced" with their
> "motherships". In my opinion, 10 % of another project that hasn't been
> already fully translated should be translated per a month, but this should
> be determined by the volunteers and the chief of the project
> خير الأعمال أقلها و أدومها
Actually, syncing should be made, ideally, even if the project is 0%
translated. The POs on the mother ship continously change. Sometimes
strings are added, sometimes they are removed. Imagine coming up to a
PO file in a project thats not fully translated, translating that
file, only to realize that file has been removed in the mothership!
All your work would be for naught :-)
Thats why its always a good idea to keep up with whatever is going on
with the project. Syncing is a mundane and difficult task, I know, but
thats why we have Nadim and his Perl scripts :-)
> Brother Abdulaziz, your idea is a good one, scheduling the projects and
> providing a clear and detailled road map would be a great thing for Arabeyes
> إن شاء الله.
It was not my idea. This was a Core ruling :-)
> I propose to give each 2 months a list of tasks and do a one week freeze where
> volunteers will choose a task to do ,was it hard or easy. It's a kind of
> contract with the community. What do you think ?
Not a bad idea actually. Unfortunately it cannot be applied as various
projects have different development cycles. 2 months might be too long
or too short. It is best in our situation to let each individual
project maintainer assign tasks in his/her own team.
Salam,
Abdulaziz,