This seems like it would be pretty useful.

Security tasks are generally kept to a limited audience of MediaWiki developers plus a few other people. We created an ACL for stewards because there was a repeated need to add them to individual tasks, and they're already an incredibly trusted group of people who are relatively well known to developers, and are familiar with our workflows.

I don't think adding all oversighters and all checkusers to individual security tasks is a good idea. There's no need for everyone to be CC'd to T207085. A few of them? Sure.

I would suggest nominating one to two people as liasons for each group who can be cc'd as necessary and inform other oversighters/CUs about the presence of bugs that are pertinent. In the past we've done it informally.

@Legoktm on reflection, I'm agreed entirely i.r.t "I don't think adding all oversighters and all checkusers to individual security tasks is a good idea" - there are a few other cases where general, non-security tasks are of immediate interest to the greater CU/OS community, but I'm not sure using an acl* project would be useful there.

Appears that this task can be closed...

In T207323#4687063, @Samtar wrote:

@Legoktm on reflection, I'm agreed entirely i.r.t "I don't think adding all oversighters and all checkusers to individual security tasks is a good idea" - there are a few other cases where general, non-security tasks are of immediate interest to the greater CU/OS community, but I'm not sure using an acl* project would be useful there.

I would suggest watching the CheckUser, MediaWiki-Revision-deletion, and/or Stewards-and-global-tools projects depending on what you want.