Due to the reasons listed on T90491, our current use of Operations as a policy/access control is sub-standard. It disallows volunteers from joining Operations, so they cannot easily follow all tasks if they so choose. As this is sub-optimal, other teams have begun to create acl*groups for policy access to address this.
We need to base access to acl*operationsteam for the #ops-access-review project tasks, as well as future procurement and S4 space access policies.
Additionally, I'll be creating an acl*procurement project for access for the S4 procurement vendor space. this space is for our quoting, and will be used instead of our current RT implementation. Procurement space access will need to be restricted to operations and wmf staff ONLY. As operations will have an acl group already, the acl*procurement will include acl*operations, plus individuals added to the policy by me (@RobH), which will be noted in the acl*procurement info page.
All of the above is basically correcting access on Operations and Ops-Access-Reviews, as well as then implementing replacing RT. None of the above should have anything but an overall positive benefit to other users (allowing them to subscribe and/or join Operations.)
I'll leave this sit for a day or so for potential objections/comments/insights I may have missed in 1:1 discussions about this.