User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20071127 Firefox/126.96.36.199 Build Identifier: Request for CVS access Reproducible: Always Steps to Reproduce: 1. 2. 3.
In order to get CVS write access, you need to follow the steps outline at http://www.mozilla.org/hacking/getting-cvs-write-access.html, which state that besides attaching your SSH key, you need to fill out the CVS Contributor Form (http://www.mozilla.org/hacking/form.html) and get two vouchers plus one super-reviewer to vouch for you. Is there a particular reason why you wish to get CVS access? I don't see that you've contributed any patches or anything of the sort at all.
Sorry, I will fax the form soon. I am a team member of the Malayalam (ml) localization team. I used to send the translated files to Joyce<firstname.lastname@example.org> (who has CVS access), for committing. But now the team has three active members and it created some conflicts (translation of already translated content). Upon my request, Joyce contacted Axel regarding CVS access for us. And Axel asked us to file a cvs access request bug. From what I know, Axel asked Joyce to vouch and said that he will second the vouching.
Off the UNCO radar.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: CVS Account Request - Joshy K Jacob <email@example.com> → l10n CVS Account Request - Joshy K Jacob <firstname.lastname@example.org>
I am vouching for Joshy.
@ Marcia - i've faxed the CVS Contributor Form. @ joyce - Thanks
Carrying over the vouching from Joyce. Marcia, this can go to IT as soon as you confirm the form.
Whiteboard: ssh-key → ssh-key, voucher
Form received. Over to server-ops for l10n account creation.
Assignee: marcia → server-ops
Assignee: server-ops → justdave
Your CVS account has been created. Your CVSROOT should be: email@example.com:/l10n Don't forget to set your CVS_RSH environment variable to 'ssh'. If you have any problems connecting, let me know.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Thanks a lot. I could login successfully.
You need to log in before you can comment on or make changes to this bug.