Closed Bug 864844 Opened 11 years ago Closed 10 years ago

Commit Access (Level 3) for Garrett Robinson

Categories

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

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: grobinson, Assigned: rbryce)

References

Details

Use grobinson@mozilla.com. See 853689 (my previous bug for Level 1 access) for SSH public key and confirmation of signed committer's agreement.
Depends on: 853689
I vouch for Garrett. He did some web console patches that I reviewed.
I vouch for Garrett. I saw his work on the web console patches and also he clearly has great taste in vouchers.
This request is ready for consideration.
Over to server-ops for L3 access.
Assignee: mozillamarcia.knous → server-ops
Garrett, I notice that you've only had L1 access for a month, and you've had two patches checked into the tree since starting at Mozilla. For L3 access we usually prefer to have applicants present a larger body of work than that, regardless of their employment status. Would you mind holding off on this until there's more of a paper trail to back up your vouchers' words?
Assignee: server-ops → mozillamarcia.knous
That's ok. Can you give me an idea of what would qualify as sufficient, and also how to re-engage in the request for commit access once I've reached that point?
There's no hard and fast rule; I imagine that six or eight nontrivial bugs would be plenty. Just leave a comment here when it's time to reevaluate the request.
Please re-evaluate this request based on the following nontrivial bugs (and others):

* bug 855326 (csp 1.1 nonce-source)
* bug 883975 (csp 1.1 hash-source)
* bug 945268 (enable csp tests on multiprocess gecko)
* bug 713980 (logging for blocked cross site requests)
* bug 924708 (incorrect enforcement of report-only CSP)
* bug 837351 ("security" panel in Web Console)

Do I need new/different vouchers?
Looks fine to me.
Assignee: mozillamarcia.knous → server-ops
+scm_level_[2-3]
Assignee: server-ops → rbryce
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.