Closed vanillacandy closed 2 months ago
This is fine. Additionally, I think we should adjust the description to the POLICIES.md doc. (This represents a change in behavior that should be explicitly highlighted).
Update this blub
Legacy policies are useful when you want to search for and report on applications deployed to a legacy stack (e.g., windows2012R2, cflinuxfs2) or service offering (e.g., using a product slug name like p-config-server, p-service-registry, p-mysql), notifying both the operator and for each application the author and/or his/her space compadres.
to be
Legacy policies are useful when you want to search for and report on applications deployed to a legacy stack (e.g., windows2012R2, cflinuxfs2) or service offering (e.g., using a product slug name like p-config-server, p-service-registry, p-mysql), notifying both the operator and for each application, users with the [space developer](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/roles.html#user-roles-2) role.
^ Please make this update to your PR.
There are sometimes hundreds of users listed as org auditors, and all of them don't do any development. The legacy policy helps us to aim to communicate to developers to migrate from legacy cflinuxfs3, and often time the hundreds of org auditors receive the notification are confused with the notifications. We'd like to focus on org developers exclusively on this notification.