Closed Bug 496227 Opened 16 years ago Closed 16 years ago

Hg Account Request - Nicholas Nethercote <nnethercote@mozilla.com>

Categories

(mozilla.org :: Repository Account Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: n.nethercote, Assigned: fox2mike)

Details

(Whiteboard: ssh-key, form, voucher1, voucher2)

Attachments

(1 file)

Attached file my public SSH key
After discussion with Sayre, I'm applying for commit access. I've attached my public SSH key. I'm happy for any of the people I've CC'd to be vouchers :) I don't think I need super-reviewer approval because I work in the JavaScript module.
Is this only for tracemonkey?
OS: Mac OS X → All
Hardware: x86 → All
Summary: HG write access for Nicholas Nethercote → Hg Account Request - Nicholas Nethercote <nnethercote@mozilla.com>
Whiteboard: ssh-key
I'll certainly vouch for njn. Tracemonkey branch at least, though ... I wasn't aware we even *had* separate ACLs by branch. Do we?
I have access to tracemonkey and tamarin-* but not mozilla-central or branch (I think, never actually tried it).
vouch
(In reply to comment #1) > Is this only for tracemonkey? Yes, only the tracemonkey repository.
If I'm right about not needing the super-reviewer approval, then I just need to fill out and send in the Committer's Agreement now, and then update the bug once I have done so, correct?
Please send the form and Erica will update the bug. Please also include the Bug ID since it makes it easier for Erica to figure out which bug to comment in. Thanks. (In reply to comment #6) > If I'm right about not needing the super-reviewer approval, then I just need to > fill out and send in the Committer's Agreement now, and then update the bug > once I have done so, correct?
I just sent the Committer's Agreement to Erica via snail-mail. Coming from Australia, it'll probably take a week or more to reach Mountain View.
I have received a Committer's Agreement for Nick.
Great. I don't think I have to do anything more now, is that correct?
Does anyone know who is responsible for the next step? Judging from http://www.mozilla.org/hacking/committer/, we're up to step 11 or 12: 11. Update the bug when all the needed info is in the bug. This way, Bugzilla can send off mail to the Mozilla representative tending to account creation. 12. The Mozilla representative will double-check that the needed info is recorded and, if so, create an account.
Sorry for the delay. Everything looks in order. Over to IT for SSH key addition to LDAP and hg_mozilla bit flip.
Assignee: marcia → server-ops
Whiteboard: ssh-key → ssh-key, form, voucher1, voucher2
Assignee: server-ops → shyam
All done. Nicholas, let me know if you see any issues.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
It doesn't seem to be working: [ocean:~] ssh nnethercote@hg.mozilla.org Permission denied (publickey,gssapi-with-mic). I'm reading https://developer.mozilla.org/en/Mercurial_FAQ. I'm pretty certain my SSH private key is correct, I regularly connect to several other machines from this one.
Ah, I hadn't setup .ssh/config correctly. Works now, thanks.
Component: Account Request: Hg → Repository Account Requests
QA Contact: hg-acct-req → repo-acct-req
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: