Closed Bug 875296 Opened 13 years ago Closed 12 years ago

Disable repository access of tchien@mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: timdream, Assigned: dumitru)

Details

I recently realized I have two commit access account, and they are of the same thing(?). - timdream@gmail.com, created in bug 437620, revived in bug 875206 - tchien@mozilla.com, created in bug 726492 I figured I should shut of the tchien@ one, given the fact I have never used it in my local working env configuration. However, I am not sure if an account created with @mozilla.com contains any MoCo special bit (autoland, maybe?). If the above is true and I am allow to, please close down the tchien@mozilla.com account and transfer the MoCo permissions to timdream@gmail.com, my original account. Thanks.
Maybe the discussion in bug 745180 is related?
If you don't use one account, repository access gets disabled for inactivity by our scripts. Up to you what you want to do with the accounts. I'd say leave them and have them get disabled. Also, I don't know if MoCo LDAP has special rights for autoland. You might want to ask whoever runs/owns it. I can tell you for sure that having a MoCo LDAP does not give you extra privileges regarding commit access, only access to some tools/webpages that are restricted to employees. Let me know if there's any action you need IT to take. Thanks!
Severity: major → normal
Right, in that case, we should disable tchien@mozilla.com then. It have not been disabled due to inactivity, but I figured I will probably never use it for repo access.
Summary: Remove/disable/combine duplicate commit access account → Disable repository access of tchien@mozilla.com
Component: Server Operations: Account Requests → Server Operations
QA Contact: tfairfield → shyam
Okay, done.
Assignee: server-ops → dgherman
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.