Requested access: mailman3-roots group (currently no hosts, but will have full sudo access to lists1002.wikimedia.org soon)
Reason: Part of T52864: Upgrade GNU Mailman from 2.1 to Mailman3, Following up to T276712: Request for creation of mailman3-roots group and needed to test and work on upgrading the old mailman.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| admin: add ladsgroup to mailman3-roots | operations/puppet | production | +1 -1 |
Related Objects
Related Objects
Event Timeline
Comment Actions
I would guess that the addition of ladsgroup to the mailman3-roots group was implicitly approved too during the last SRE meeting that approved the creation of the group, but for audit log purposes is better to have the approval here on task too.
Given that the group doesn't have an explicit approval list of people, I'm asking for @mark or @faidon to approve the request here on task.
Comment Actions
Change 673971 had a related patch set uploaded (by Volans; owner: Volans):
[operations/puppet@production] admin: add ladsgroup to mailman3-roots
Comment Actions
While the ownership of mailmain within SRE is being discussed, I've raised this request in today's SRE meeting and got approved so that @Ladsgroup is unblocked.
Comment Actions
meanwhile there is a VM, lists1002, that this should be applied to. So far it has the "insetup" role but the _actual_ step to give Amir access after he is in the group will be to apply the mailman3 role to it. cc @Legoktm
Comment Actions
Change 673971 merged by Volans:
[operations/puppet@production] admin: add ladsgroup to mailman3-roots
Comment Actions
Until yesterday it was supposed to stay open because the role was not applied yet on any machine. But now it is. Closing this as resolved.
[lists1002:~] $ id ladsgroup uid=3182(ladsgroup) gid=500(wikidev) groups=500(wikidev),827(mailman3-roots)