Per T788.
Description
Related Objects
- Mentioned In
- T1273: Create "Repository-Admins" group
- Mentioned Here
- T788: Propose to make @chad an administrator in Phab
Event Timeline
Standard policy: Roots get access to systems.
Edit: And this is just transfer of existing active admins of gerrit into Phabricator.
Wrong account comment^
System level access sure. AFAIK "roots" do not get all access to all things in all places. I am not, for instance, an admin in OTRS. Nor why would I be? Another example, I only got admin privs in bugzilla when needed. I'll leave that to @mark.
This discussion is not about @Catrope, but about principles to accept new admins here.
If Gerrit admins need the equivalent superpowers in Phabricator, this can be probably solved with a "Differential Admins" team with the corresponding permissions granted, isn't it? Or is there any permission that Gerrit admins would need that can't be satisfied this way?
PS: the whole #Code-Review is in low priority now, so setting this priority here accordingly.
The equivalent of "gerrit admin" would be admin access to Audit, Diffusion and Differential.
We should just make a group called "Repository Admins" or somesuch that gets admin powers to these applications. Easily done.
Something like "Repository-Admins" sounds good to me (note the dash/hyphen). With a nice description what this covers.
I trust Roan with this. Two caveats at the moment that anyone having repo admin access should understand:
- Repo imports are on a slight hold as we iron out the remaining callsign conventions on-wiki
- No repo should be locally hosted. We're only mirroring from Gerrit/elsewhere
- Throw the policies in a wiki page
- Add Roan to the Diffusion-Repository-Administrators group
- ???
- profit
seems good dude