Closed
Bug 548096
Opened 15 years ago
Closed 15 years ago
Hg (Level 1) Account Request - Chris Leary <cleary@mozilla.com >
Categories
(mozilla.org :: Repository Account Requests, task)
mozilla.org
Repository Account Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cdleary, Assigned: jlaz)
Details
(Whiteboard: ssh-key)
Attachments
(1 file)
401 bytes,
text/plain
|
Details |
This is for the http://hg.mozilla.org/tracemonkey repository.
Reporter | ||
Comment 1•15 years ago
|
||
Whoops, lost the pubkey in the email disambiguation page...
Updated•15 years ago
|
Attachment #428521 -
Attachment mime type: application/octet-stream → text/plain
Comment 2•15 years ago
|
||
Tracemonkey isn't an incubator repository.
OS: Linux → All
Hardware: x86 → All
Summary: Incubator Account Request for Chris Leary <cleary@mozilla.com> → Hg Account Request - Chris Leary <cleary@mozilla.com>
Whiteboard: ssh-key
Reporter | ||
Comment 3•15 years ago
|
||
Thanks, resolving as invalid. Is there some way to check that status in the future?
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Comment 4•15 years ago
|
||
(In reply to comment #3)
> Thanks, resolving as invalid. Is there some way to check that status in the
> future?
If you still need access, we can go through the appropriate process... Your original summary called this an incubator access request, though, which is what I was correcting.
Specifically, you'll need:
* Signed Committer's Agreement sent/given to Erica (http://www.mozilla.org/hacking/committer/committers-agreement.pdf)
* Two vouchers to vouch for you
Reporter | ||
Comment 5•15 years ago
|
||
Hmm okay -- is there a way for me to add that key for a user repository in the meantime?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 6•15 years ago
|
||
(In reply to comment #5)
> Hmm okay -- is there a way for me to add that key for a user repository in the
> meantime?
No, we don't have any policy that applies to user repositories currently, so we can't (currently) grant accounts for such requests.
Comment 7•15 years ago
|
||
(In reply to comment #6)
>
> No, we don't have any policy that applies to user repositories currently,
Agree.
> so we can't (currently) grant accounts for such requests.
Disagree.
Comment 8•15 years ago
|
||
Sayrer is a man of few words, but I can interpret: we make new policy by doing experiments, one-offs. We are not a-priori totalizing policy wonks. When we don't have a policy, the answer is not "no", it's "yes, for you, and we will learn and codify as we go". ;-)
/be
Comment 9•15 years ago
|
||
We have consistent precedence via numerous bugs of not accepting such requests for users/-only accounts. The new Commit Access Policy (https://wiki.mozilla.org/Commit_Access_Policy) will permit such requests, but until it's put into effect, there's nothing I can do based on current policy.
CC'ing Mitchell, the owner of the "Commit Access Policy" submodule (https://wiki.mozilla.org/Module_Owners_Activities_Modules#Governance_Submodule:_Commit_Access_Policy), in case she has any comments.
If Chris wants to apply for something for which we currently have policy, I'll be happy to help him through that, but in this current case, my hands are tied based on the current policies (and lack thereof).
Comment 10•15 years ago
|
||
The new policy is in effect, following Mitchell's post to .planning a few weeks ago. However, we lack the technical ability to implement it. Aravind is working on that now, and hopes to have it done by the end of the month.
Given that, I would be happy with giving Chris hg_mozilla based on the new policy's provisions, and then manually changing him to still have just hg_mozilla after any future migration step. We could maintain a (short) list of people in that category. That would allow us to use the new policy now.
Gerv
Comment 11•15 years ago
|
||
(In reply to comment #10)
> The new policy is in effect, following Mitchell's post to .planning a few weeks
> ago.
... and the large {draft} notice at the top?
> However, we lack the technical ability to implement it. Aravind is working
> on that now, and hopes to have it done by the end of the month.
I'd rather us not take on a policy that we can't even use most of the provisions, as it wouldn't make sense at all, and we're likely to forget to modify people's access when it does come into effect. Also, I have yet to see an IT bug that actually specifies the things that need to be done to implement such a policy. You mentioned bug 524080 in another bug, but that bug is just about account deactivation -- nothing about modifying the current Hg setup.
Comment 12•15 years ago
|
||
(In reply to comment #11)
> ... and the large {draft} notice at the top?
Fair point :-) Fixed.
> I'd rather us not take on a policy that we can't even use most of the
> provisions, as it wouldn't make sense at all, and we're likely to forget to
> modify people's access when it does come into effect.
I'm happy to take responsibility for maintaining the list of names of people who require manual changes after the migration has taken effect. I'm sure it won't be a long list. We seem to get about one request like this a month.
> Also, I have yet to see
> an IT bug that actually specifies the things that need to be done to implement
> such a policy.
Well, IT are working on it, and are using bug 524080 to track it. If you think that's wrong, take it up with them :-)
Gerv
Comment 13•15 years ago
|
||
Ok, the new policy is now in effect.
As per https://wiki.mozilla.org/Commit_Access_Policy#Level_3_-_Core_Product_Access, two module owners/peers and a super-reviewer are now required for access to the tracemonkey repository.
Status: REOPENED → NEW
Comment 14•15 years ago
|
||
we're looking for level 1:
Level 1 - Try/User/Incubator Access
Requirements: one voucher - any another user with level 2 or above access
I am the voucher.
Comment 15•15 years ago
|
||
comment #1 is confusing here, I realize.
Comment 16•15 years ago
|
||
(In reply to comment #15)
> comment #1 is confusing here, I realize.
Yeah, I missed comment #5 when rereading this.
Ok, just waiting on Erica to confirm receipt of the form.
Summary: Hg Account Request - Chris Leary <cleary@mozilla.com> → Hg (Level 1) Account Request - Chris Leary <cleary@mozilla.com>
Reporter | ||
Comment 17•15 years ago
|
||
Ping! Erica, can you confirm please?
Comment 18•15 years ago
|
||
I have received Chris' Committer's Agreement.
Comment 19•15 years ago
|
||
This one looks good to go. Over to server-ops for access to tracemonkey repo.
Assignee: marcia → server-ops
Comment 20•15 years ago
|
||
(In reply to comment #19)
> This one looks good to go. Over to server-ops for access to tracemonkey repo.
No, this is for level 1, so just hg_mozilla bit.
Assignee | ||
Comment 21•15 years ago
|
||
hg_mozilla and ssh key added
-jlazaro
Assignee | ||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Assignee: server-ops → jlazaro
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.
Description
•