CVS Account Request - Graydon Hoare <graydon@mozilla.com>

RESOLVED FIXED

Status

mozilla.org
Repository Account Requests
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: graydon, Assigned: aravind)

Tracking

Details

(Whiteboard: ssh-key, voucher, form, sr1, sr2, sr3)

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
I've been cooking up a couple patches for the past several months (bz 333078 and 348789) and at least the latter is nearly ready to land (given the appropriate r+ and sr+ votes, etc.)

However, I haven't gotten around to acquiring CVS write access yet. I'm not sure what the appropriate technique is. I can send an SSH public key.. is that enough? Do I need someone else to vouch for me?

Comment 1

11 years ago
Moving to CVS account request.
Assignee: server-ops → marcia
Component: Server Operations → CVS Account Request
QA Contact: justin → justdave
See http://www.mozilla.org/hacking/getting-cvs-write-access.html
Group: mozillaorgconfidential
Summary: I'd like to start landing patches → CVS Account Request - Graydon Hoare <graydon@mozilla.com>
Bug 348789 doesn't seem to the bug you meant.
OS: Other → All
Need someone to vouch, as well as some SRs to chime in.
Status: NEW → ASSIGNED
I will vouch!

/be
I sr with glee.
brendan/shaver: should someone outside of mozilla.com add their sr approval or is this good to go?
Perhaps roc and dbaron would sr+?

/be
I haven't really looked at anything of Graydon's.
sr=roc
(Reporter)

Comment 11

11 years ago
Created attachment 240073 [details]
my public SSH-DSA key
Graydon meant bug 333078 and bug 348798.

In general, our policy has been that we don't give out CVS write access until somebody has written enough *checked in* (by others) patches to show the things mentioned in http://www.mozilla.org/hacking/getting-cvs-write-access.html .  While I have a high opinion of graydon's work, I don't see a strong need to make an exception to that policy here, and it would be somewhat hypocritical of me to sr *at this time* given that I'm pushing others towards making our CVS access policies more restrictive.
(Reporter)

Comment 13

11 years ago
(In reply to comment #12)

> While I have a high opinion of graydon's work, I don't see a strong need to
> make an exception to that policy here, and it would be somewhat hypocritical of
> me to sr *at this time* given that I'm pushing others towards making our CVS
> access policies more restrictive.

Fair enough. This is an aspect of being an outsider hired into the project that we all forsaw, and I take no offense at it. I will continue to update the patches I have in bugzilla.

In the meantime I have faxed in my form and attached my key. Presumably they can be kept on file until needed.
Fax form received.
sr=dbaron
This looks ready to go.
Whiteboard: ssh-key, voucher, form, sr1, sr2, sr3
Account created. Over to server-ops for SSH key.
Assignee: marcia → server-ops
Status: ASSIGNED → NEW
(Assignee)

Updated

11 years ago
Assignee: server-ops → aravind
(Assignee)

Comment 18

11 years ago
Your CVS account has been created.  Your CVSROOT should be:

   graydon%mozilla.com@cvs.mozilla.org:/cvsroot

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
You need to log in before you can comment on or make changes to this bug.