Commit Access (Level 3) for Dale Harvey: mozilla-central commit

RESOLVED FIXED

Status

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

People

(Reporter: daleharvey, Assigned: rbryce)

Tracking

Details

mozilla-central requires level 3 access. You'll need to have another module owner/peer vouch for you in this bug as well.
(Reporter)

Updated

5 years ago
Summary: Commit Access (Level 2) for Dale Harvey: mozilla-central commit → Commit Access (Level 3) for Dale Harvey: mozilla-central commit
(Reporter)

Comment 2

5 years ago
I assume they cant be the same voucher (jlebar) from the last one? vingetun will do it when he gets internet that works, Fabrice?
Where does everyone keep reading that level 2 is mozilla-central?
(Reporter)

Comment 5

5 years ago
It was just a matter of not RTFM, Level 2 - General Access sounded right and it comes after 1, I didnt check what 3 was.

http://www.mozilla.org/hacking/commit-access-policy/
Hmm, ok.  You're definitely not the first one to do that.
(In reply to Dale Harvey (:daleharvey) from comment #2)
> I assume they cant be the same voucher (jlebar) from the last one?

They can be the same.

Also, not that I expect this to be an issue in this particular case, but the requirement is for two module owner/peer vouchers, and they don't "carry over" from the level 1 access bug (a vouch for level 1 access doesn't necessarily imply a vouch for level 3 access).
I vouch for Dale.
Assignee: mozillamarcia.knous → server-ops
While we're clarifying the procedure: Do any two module owners/peers work, or do they need to be peers of modules which live in m-c?  If it's the latter, I vouch for Dale.  :)
(Assignee)

Updated

5 years ago
Assignee: server-ops → rbryce
(Assignee)

Comment 10

5 years ago
Speaking on behalf of the IT team here.  When we flip bits to give access, our knowledge of the vouchers is completely based on tribal knowledge.  We would love some clarity on who can vouch for commit access.  Im glad to do the documentation work:)

Level 3 access granted
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(In reply to Justin Lebar [:jlebar] from comment #9)
> While we're clarifying the procedure: Do any two module owners/peers work,
> or do they need to be peers of modules which live in m-c?  If it's the
> latter, I vouch for Dale.  :)

And since you're a peer of 6 modules does it count for 6 vouches? :)
(In reply to Rick Bryce [:rbryce] from comment #10)
> Speaking on behalf of the IT team here.  When we flip bits to give access,
> our knowledge of the vouchers is completely based on tribal knowledge.  We
> would love some clarity on who can vouch for commit access.  Im glad to do
> the documentation work:)

Not quite true...there are already the "despots" who take care of ensuring that the vouches are OK. It's not IT's responsibility to know this. It becomes our job once the bug is moved to our queue.
(Assignee)

Comment 13

5 years ago
(In reply to Dumitru Gherman [:dumitru] from comment #12)
> (In reply to Rick Bryce [:rbryce] from comment #10)
> > Speaking on behalf of the IT team here.  When we flip bits to give access,
> > our knowledge of the vouchers is completely based on tribal knowledge.  We
> > would love some clarity on who can vouch for commit access.  Im glad to do
> > the documentation work:)
> 
> Not quite true...there are already the "despots" who take care of ensuring
> that the vouches are OK. It's not IT's responsibility to know this. It
> becomes our job once the bug is moved to our queue.

"Tribal Knowledge".  I believe it is still our job to verify that this is done correctly.  Sure, we can just trust that when gavin kicks the bug to Server Ops its good to go.  I would prefer to, "Trust, but verify"
Since our only purpose is to "verify", adding an extra verification step seems potentially burdensome :) But I think the information at http://www.mozilla.org/hacking/committer/ is correct and mostly complete - if you see stuff missing we can fix it.
(In reply to Justin Lebar [:jlebar] from comment #9)
> While we're clarifying the procedure: Do any two module owners/peers work,
> or do they need to be peers of modules which live in m-c?

The policy says the latter, but I think in practice we'd consider Gaia repos to also be "level 3".
(Assignee)

Comment 16

5 years ago
(In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #14)
> Since our only purpose is to "verify", adding an extra verification step
> seems potentially burdensome :) But I think the information at
> http://www.mozilla.org/hacking/committer/ is correct and mostly complete -
> if you see stuff missing we can fix it.

Awesome. I only chimed in because there seemed to be confusion, on the process as a whole.  I really just wanted to make sure we are doing our part to make things clear and simple for the end users.
You need to log in before you can comment on or make changes to this bug.