Note: for historical task protection to remain we need to usurp the /existing/ project used as an acl and create a second project for tagging purposes only. This is in the same spirit as T90491. We currently have hundreds of tasks that would be useful for volunteers to follow tagged with Security. Related blog post.
- Determine #acl*security access subgroups
- Create first subproject of acl*security_volunteer (this will inherit all users)
- Create subsequent subprojects and add members as appropriate
- Create a new security project for tagging only (security-related)
- Add security-related to all existing tasks tagged with #security
- add a herald rule to add #security-related to all tasks if tagged with #acl*security (H353)
- Add all members of original security project to transitional security-related
- security-related still needs to be protected until the protect as security issue is changed
- update security forms to add Security
- rename #security to #acl*security (remove security alias)
- rename security-related to security
- T245201. Update protect as security issue to use acl*security (since this is by name and not phid)
- $projects = WMFSecurityPolicy::getProjectByName('security');
- https://phabricator.wikimedia.org/rPHEX9ec849c6ea4af2b55732dfd928f59e62d4f289cd
- remove #acl*security from all tasks as a tag
- fix herald rule H353 (T245773)
- convert Security to an open group
- email to wikitech-l as an FYI