I don't think I needed a task like this for those rights. @Legoktm is a deployer he can probably still do cloudadmin stuff like adding himself to that group anyway.

We don't have a formal process for this (yet), but like +2 and production shell rights changes I felt that it would be a good idea to have a bit of documentation and probably a short discussion within the cloud-services-team.

+1

Support. Dis kat apurrvs :-)

Steps from https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin#What_makes_a_root:

• Project administrator: This allows a user to add and delete other users from the Toolforge project.
• sudo policy "roots": This allows a user to use sudo to become root on Toolforge instances.
• 'admin' tool maintainer: This allows a user to log into infrastructure instances and perform tasks as the admin tool.
• Gerrit groups "labs-toollabs" and "toollabs-trusted": These allow a user to +2 changes in repositories exclusive to Toolforge.

I did not grant @Legoktm into the labs-toollabs gerrit group because I myself am not in the group! Looks like help from @Andrew is needed to expand the list of folks there or we should drop it from the list.