Commit Access (Level 3) for Anant Narayanan

RESOLVED FIXED

Status

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

People

(Reporter: anant, Assigned: ashish)

Tracking

Details

(Reporter)

Description

6 years ago
Tried to commit something to mozilla-inbound today, but it turns out I don't actually have a level 3 account. I'm planning on landing some code for WebRTC and Apps on m-c on a tight schedule, so it would be great to be able to push patches on my own.

Potential vouchers on CC. Thanks!
I'll vouch of course
I also vouch for Anant, 100%.
Erm, but I'm not a module owner or peer of code stored at level 3, which I would need to be to vouch for Anant, according to the commit access policy <http://www.mozilla.org/hacking/commit-access-policy/>.

Anant: the major level 3 modules are Firefox, Thunderbird, and Fennec:

https://wiki.mozilla.org/Modules/All#Firefox
https://wiki.mozilla.org/Modules/All#Thunderbird
https://wiki.mozilla.org/Modules/All#Fennec

Are there owners/peers of those modules who are familiar with your work?

Note: I'm happy to help push patches over the next couple days as needed until you obtain level 3 access.
(Reporter)

Comment 4

6 years ago
Ah, thanks Myk, I didn't realize there were only three level 3 modules. So I'm guessing none of the sub-modules in Core/Other count.

I will take you up on your offer to push patches, thanks again!
Erm, sorry, I mixed up "module" with "repository."  The level 3 requirement is "two vouchers - module owners or peers of code stored in a repo at this level."  So modules/peers of Core/Other code stored in mozilla-central qualify, as do modules/peers of Core/Other code stored in any of the following other repositories:

comm-central
releases/*
mobile-browser
projects/electrolysis
projects/firefox-lorentz
mid-air collision, but I'll post my comment anyways:

I am a module owner of a level 3 module (webrtc, recently created).  If anant already has level 2 access, then the requirement is covered (via "Someone can be upgraded from level 2 to level 3 by being vouched for by a single module owner of level-3-stored code.")

The requirement is:
"module owners or peers of code stored in a repo at this level."

Any module that's part of Core is "stored in a repo at this level".  I don't believe that requirement is for a top-level module peer (and if you look at other commit-access bugs, I suspect you'll find this is the norm).  See bug 696277, but there are tons other I believe.  If I'm wrong, then the statement above needs to be edited.

I can also push patches as needed.
Over to server-ops for Level 3 access.
Assignee: mozillamarcia.knous → server-ops
(Assignee)

Comment 8

6 years ago
+scm_level_3!
Assignee: server-ops → ashish
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.