Change Details

This should help in various situations: - overuse of SQL resources (e.g. T114559), where the service group id needs to be mapped to service group name and a list of maintainers - overuse of bastion resources, where the service group name (and sometimes the uid) needs tobe mapped to a list of maintainers From the list of maintainers, it should then be easy to send out e-mails or talk page messages.

This should help in various situations: - overuse of SQL resources (e.g. T114559), where the service group id needs to be mapped to service group name and a list of maintainers - overuse of bastion resources, where the service group name (and sometimes the uid) needs tobe mapped to a list of maintainers From the list of maintainers, it should then be easy to send out e-mails or talk page messages. Manual steps: * service group id / name -> member list (shell name): `ldaplist -l servicegroups | grep 51053 -C 15` * service groups can be contacted via e.g. `tools.wikibugs@tools.wmflabs.org` * shell name -> wikitech user/email: `ldaplist -l passwd valhallasw` * users can also be reached directly using e.g. `valhallasw@tools.wmflabs.org`

This should help in various situations: - overuse of SQL resources (e.g. T114559), where the service group id needs to be mapped to service group name and a list of maintainers - overuse of bastion resources, where the service group name (and sometimes the uid) needs tobe mapped to a list of maintainers From the list of maintainers, it should then be easy to send out e-mails or talk page messages. Manual steps: * service group id / name -> member list (shell name): `ldaplist -l servicegroups | grep 51053 -C 15` * service groups can be contacted via e.g. `tools.wikibugs@tools.wmflabs.org` * shell name -> wikitech user/email: `ldaplist -l passwd valhallasw` * users can also be reached directly using e.g. `valhallasw@tools.wmflabs.org`