The new translation status page has been installed:
You will notice that there is a new column called "Availability" for
each package. It either says "Finished" (if the translation is 100%) or
has a "Take" button (if the translation is not 100%). This feature is
designed to minimise the commit conflicts and better coordinate the
translation activity within the same language group. If you wish to
finish the translation of a package, just click "Take" button, fill in
your login and password. Then you will be able to finish and commit the
translation to cvs. All cvs account holders should have received or soon
to receive information about login name and password.
Please feel free to ask if you have any questions and encountered any
After much debate and careful consideration in light of the many
emails (many of which were passionate and full of incitement), Arabeyes
regretfully announces the suspension of its current participation
pending further review of Fedora's upcoming policy. This decision was
not made hastily nor without debate, but in light of all the recent
changes/discussions and Fedora's lack of appreciation and recognition of
Arabeyes' efforts and its team-centric attitude, it was decided that it
is best if Arabeyes steps aside. The decision was made by Arabeyes
'core' managers as well as 3 of the key Fedora translators who have
noted losing any interest in working on the Fedora translation project
(note, the vote was 6 to 1 in favor of suspension).
We don't believe our feelings are unique with this regard in the
Open Source community with respect to the approach and conduct
regarding translations. We do, however, think its in Fedora's and the
Open Source community's best interest to consider a more team
encouraging approach to localization projects. It was a shame to see
such a trivial issue mushroom out of control. Arabeyes' intentions
were/are not to 'take control' of anything but rather to unify all
aspects of Arabic contributions (including translations) across Open
Source software (scattered and disorganized attempts failed in the
This is the last we are going to say about this topic and we humbly
request all Arabeyes members to simply forgo this topic entirely --
we've said all we want to say.
Those who are looking to know the truth behind Arabeyes and its
achievements should visit its homepage and study its contributions
and compare them to those making unjust accusations. We work
transparently and expect others to do the same.
I am about to commit the dist.po file after translating part of it to Arabic.
since this is my first commit and I think I am missing something.
$ cvs commit specspo/ar.po
cvs commit: use `cvs add' to create an entry for specspo/ar.po
cvs [commit aborted]: correct above errors first!
I thought this may be because the file is taken (removed?) by me,
$ cvs -z9 co specspo/ar.po
Enter passphrase for key '/home/munzir/.ssh/id_dsa':
cvs server: warning: new-born specspo/ar.po has disappeared
The above message gave me that impression, so I released it first and tried
again but the same message. Is it necessary to do cvs add first? I don't want
to mess things up so I decided to ask first.
Munzir Taha PGP Key available
gpg --recv-keys --keyserver www.mandrakesecure.net F0671821
Telecommunications and Electronics Engineer
Linux Registered User #279362 at http://counter.li.org
Mandrake Club member
Maintainer of the Open Arabic Bugs Project at
CIW Designer, ICDL, MOUS
New Horizons CLC
The mailing list for Fedora Translation Project Arabic team is available
For the moment I elected myself as the list maintainer, however, I
encourage everyone interested in contributing to Arabic translation of
Fedora to subscribe to the list and elect your own maintainer.
Let's please move the threads relating to Arabic translation to this
list from now on.
What will be the user/pass for taking the available file from web?
I have tried with my cvs user/pass.. but it doesn't work.
What should be done?
Username of my cvs account is, jamil
If there were translation teams, and I was the coordinator of my team...
* I would encourage all translators to have a CVS account and commit
their changes, *provided* the file has been *reviewed* and *accepted* by
the rest of the members of the team.
* I would encourage all translators to apply as maintainers for those
files that they are familiar with, either because they have translated
them before, or because they use them often, or for whatever reason. I
would still give priority to the last translator to be the maintainer if
he/she would like to.
* I would make sure that whenever a file is "taken" or "released" the
team's mailing list, and specially the maintainer of a file, are
informed about it.
* I would have more time to translate, and I would have to spend less
time coordinating the team, assigning files and keeping track of who's
doing what and for how long they have been doing it.
*** Translator: the person translating a file at a given time.
*** Maintainer: is the person responsible to keep updated a file,
whenever it needs improvements. This person would be responsible for any
translation bugs on that file. He/she doesn't have to be the translator,
though. The translator might change over time, upon team member's
A Maintainer should be informed about translators taking their files,
and maybe maintainers should be able to commit at any time independently
of who's taken the file... (if possible)
Briefly, a maintainer is the person to contact for a certain file, and
it often happens to be its translator too.
*** Coordinator (team): the person to contact about anything related to
the translation of a certain language (as described in Christian Rose's
description of the GNOME Model¹). It is the maintainer of all those
files that have not yet a maintainer, or for whom s/he is the real
maintainer, of course. It will commit files and act as a maintainer on
behalf of translators that have no CVS account.
The coordinator coaches new translators (could be done by maintainers
Possibly the coordinator should have full CVS access to any file that
belongs to its language.
The election of the coordinator is up to each team, any changes about
coordinator must be submitted to this mailing list.
The coordinator should be informed about changes in Maintainers.
Maybe there could be the role of the "translation project coordinator"
much like what Christian Rose is for the GNOME project, and which I
suppose falls into Sarah Wang right now.
Fedora translation page should have a description of the translation
process, teams, coordinators... you get the idea :)
All that... of course, if there were translation teams...
Briefly, combining teams with the new method have a lot of potential
that we should explote.
Again, this is only my view, and there might be flaws, if there are I
hope you can spot them and tell me :)
Bernd: these might be the scriptures you were asking for :)
Note: not all members of a team have to be translators, there are also
proof readers, philologists, users, etc, and not all of them have to
have CVS access.
-----BEGIN PGP SIGNED MESSAGE-----
On Monday 28 June 2004 23:30, Munzir Taha wrote:
> On Yaum al-Ithnain 10 Jumaada al-Awal 1425 11:38 am, Youcef Rabah Rahal
> > On Sunday 27 June 2004 17:08, Munzir Taha wrote:
> > [...]
> > > Yousef, will you please
> > > release that file for us.
> > [...]
> > As you can't commit yet to Fedora CVS, I think releasing it will not
> > resolve the issue and will make you loose more precious time and money.
> > You can:
> No, I have a CVS account now so please release it since there is no need to
> put a _proxy_ in between ;)
> Yousef, we are really going to commit through arabeyes in the present and
> future inshallah. I am not against committing via arabeyes in general as
> you know but for now release the file so that I release the last remaining
> part of anxiety towards the subject.
Youcef R. Rahal
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
I just want to recap and clear all the heat in
the previous emails, hoping to reach a point
where everyone cool down and reach a working
- - Most of the Arabic translation almost done.
- - Arabeyes team to take credit for the translaiton.
- - New team from KCAST want to join.
- - Individuals from other Arabic LUGs want to join
- - Fedora Team still working on setting up team pages,
current system allow maintainers for modules, and
or large scale maintainer for certain lang. I belive
the system should fit fine, yet it is open
for suggesstion and request enhancement as needed.
I personally agree with what Alan mentioned that
most of the translation teams usually appear when
all the work are done. I can see valid request from
Arabeyes to have maintainership on the arabic
translation. Also I can see the concerns which
the other groups have against arabeyes, and the
fear of control and forcing policies from
Arabeyes, requesting to be part of arabeyes
or you can not contribute. Some ppl do not want to be
part of Arabeyes yet they would like to contribute.
I would like to recommend something to solve
all this. No one can deny the effort done by
Arabeyes and it would be unfair not to grant
them the maintainer. Yet, I hope that feedback
from others and suggestion would be faced
by difficult attitude from Arabeyes. This
is one of the main issue I saw personally.
Quoting from Mohamed Elzubeir:
> - You have certain issues with the way Arabeyes handles
> things (so far Arabeyes officially has not done anything,
> so I'm not sure what you are referring to -- but if
> you do have such issues, we would be happy
> to hear constructive criticism on the 'general' list).
That would not be only me. Munzir & Mohammed Desoky requested
more open and flexible attitude from Arabeyes. Not only
referring to what is currently Arabeyes doing on Fedora,
but overall as a policy. For example the attitude
when discussing things, starting aggressively defending,
sarcasm tone, ...etc. Not only what happened here
while discussing, but also from the link Munzir
pasted, it seems the default way to handle issues.
I think it worth listening and considering :)
After all we all are interested in Arabic being properly
supported and translated. It is good to have larger
group regardless if they want to work under Arabeyes
or outside. I hope you agree with me on this.
So I would like to ask the other arabic groups
to team up with arabeyes, and work up something
which satisfy everyone, and get the work done.
I belive we will need to review & QA the work
done already plus finishing up the last big file which
is not yet done.
Munzir, Mohamed Deskoy, Arabeyes & Other indiveduals
any suggestion on how to move from this point forward?
Just keep in mind two things Arabeyes is well established
group who I belive should maintain. Yet, a littel
bit of change of how things handled and allow
more freedome to others groups need to be clear
and granted from Arabeyes. Afterall we all working
on one target.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----