User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/2008103100 SUSE/3.0.4-4.6 Firefox/3.0.4
need write access in order to commit translations to CVS
Created attachment 385339 [details]
SSH public key for CVS access
Have you filled out the Committer's agreement and returned it to Erica? http://www.mozilla.org/hacking/committer/committers-agreement.pdf.
Also will need someone to vouch.
Yes i did send it already... please advise me more on how to do it.
Marcia, has Mozilla received Vannak's signed committer's agreement?
CCing Erica for info on the form.
Adjusting the bug to actually make sense, this needs to be HG, of course.
ok i'll resend it and cc to Marcia.
I received the form via email - Axel is this one ready to go?
This isn't ready yet, it needs a review of the actual localization still.
Axel: is this being kept open to track that review, or has this request just stalled? I'd like to try and keep the account-request queue clear and actionable, but also want to make sure I'm not throwing a wrench into your process.
Vannak? How's Khmer doing?
@Axel: when will i be able to commit the translation?
See my comment 9. https://wiki.mozilla.org/L10n:Becoming_an_Official_Localization has details on how to get a bug on file to get it reviewed.
Hi Axel, Do I need to file a registration bug and attach localization source for the review?
Someone else has filed a Registration bug here:
Do you know this person? We should get an official Khmer registration bug on file that has all community members working on it. In that bug, we can attach a Khmer version for review.
Have you filed or considered filing that bug yet?
Look for Registration and Management under Component...but be sure to reach out in the other bug first to see who that contributor is.
Hi Seth, Yes I know him. He is a member of JugCam, Joomla User Group in Cambodia. So should I attach localization file to that bug for reviewing?
You could do this. Or, consider contacting him and asking him if you can file a new bug with him as a CC on it. Then, close that original bug and move forward with the new one by attaching your localization to that one that you file. Making sure you manage the community and gather as many contributors should be part of the plan for your team. Thanks again for you interest. I am excited to see a Khmer localization one day!
Actually, my colleague,Piseth, and I have already been working on localizing FireFox and Thunderbird into Khmer by naming it as Mekhala and Moyura. but we think it would be better if we can also have FireFox and Thunderbird in khmer.
No followup here for a while, going to assume this is no longer needed.
Gavin, this bug is for Vannak to get hg access. We still require a Firefox in Khmer. Can we review why Vannak is not given hg access?
To be clear, I was not making any judgment about whether he needs or should get access - I was merely noting the fact that there has been no displayed interest in moving this forward, and resolved this bug to get it off our list of action items.
My (perhaps incorrect) understanding of the l10n access process is that resolving bug 551886 is a prerequisite to getting access, so perhaps attention is best focused there. I think Seth B or Axel are the people to poke about that.
Still no actionable items here for the account-request processing - you can ping me if there's confusion about the process.
I just got the source few weeks ago and started translating new strings around 600. it is supposed to be finished this week. i'll submit the source for review as soon as it is finished.
Reopening this bug, as we need Vannak being able to push changes l10n Khmer repo on mercurial.
Axel, can you vouch, plese?
(In reply to Milos Dinic [:Milos] from comment #24)
> Reopening this bug, as we need Vannak being able to push changes l10n Khmer
> repo on mercurial.
> Axel, can you vouch, plese?
Sorry for the lag, I didn't dig through the flurry of new people we took in this cycle.
This is good for IT, please create a level 1a account with scm_l10n, and send out an ldap password notification.
Please also add Vannak to @Localizers for svn access. I thought there's a bug on that somewhere, but I can't find it right now, sorry.
(In reply to Axel Hecht [:Pike] from comment #26)
> Sorry for the lag, I didn't dig through the flurry of new people we took in
> this cycle.
> This is good for IT, please create a level 1a account with scm_l10n, and
> send out an ldap password notification.
> Please also add Vannak to @Localizers for svn access. I thought there's a
> bug on that somewhere, but I can't find it right now, sorry.
axel: thanks for the ack.
ServerOps/Marcia: This was assigned to Marcia, but changed to ServerOps in comment#26. Not sure if intentionally. Per comment#7, comment#8, Vannak's committer agreement has already been filed. Do you need any other info to complete
SSH public key attached in comment 1
Erica confirmed she has contributors agreement on file in comment 8
Axel vouched in comment 26
Protocol is for either Marcia/Gavin to now say that everything is OK and should be moved to Ops.
I'm actually the one that hand over account requests for scm_l10n over to IT, commonly neither marcia nor gavin are involved.
As I said before, this is good for IT.
LDAP account has been created and emailed to firstname.lastname@example.org. Passing the bug to Dumitru to complete ssh key.
You attached your private key, not your public key.
Considering that the bug is 2 years old, I would highly recommend to generate a new SSH key pair and re-send us the new public part of your key.
Created attachment 588292 [details] [diff] [review]
New Publice SSH
Done. Added you to the localizers group in svn.
(In reply to Dumitru Gherman [:dumitru] from comment #33)
> Done. Added you to the localizers group in svn.