Please create an LDAP/SVN account for: Name: Jannis Leidel Email: firstname.lastname@example.org I'm a MDN web dev and want to update the MDN strings in Verbatim. :mathjazz mentioned that I may need to sign a "committer's agreement"? Is this still true despite the fact that my work contract already contains similar agreements?
Component: Server Operations: Account Requests → Server Operations
QA Contact: moconnor → shyam
To clarify, I have no idea if I signed one of those "committer's agreement" as part of onboarding, or can you remember what you signed with jet-lag on your first work days?
Yes you do need to sign a committer's agreement - https://www.mozilla.org/hacking/committer/
Assignee: server-ops → mozillamarcia.knous
Component: Server Operations → Repository Account Requests
QA Contact: shyam
:ashish Are you saying you looked in my files and found out that I hadn't signed such a thing during the onboarding week in MV or generally sepaking?
I've mailed the committer's agreement with a S/MIME signed email to Marcia Knous. I'm not sure what's the next step means though: "Get your voucher(s), and/or the owner of the exception tree you want access for, to add a comment to the bug saying they support your application." Mind elaborating?
Form received. In order to have access to the Mozilla Repos, usually someone who already has access vouches for you. Also the commit access form is not signed when you are onboarded at Mozilla, this is something you have to do if you want access to the various repos.
needinfo'ing :groovecoder who is my manager with access to the required repo. Luke, please needinfo :marcia once you've "vouched" here for me.
+1 :jezdez is MDN dev staffer and needs SVN access.
Flags: needinfo?(lcrouch) → needinfo?(mozillamarcia.knous)
Over to server-ops for LDAP/SVN.
Assignee: mozillamarcia.knous → server-ops
ssh_key in place. +SVN access. + email@example.com to the projects/mdn group in SVN authz file.
Assignee: server-ops → rbryce
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.