Once done I'd recommend renaming it without alias to something like privacy-archived and add privacy as "additional hastag" (alias) to https://phabricator.wikimedia.org/tag/privacy_engineering/. That way, generic links and existing workflows will continue to work and end up in a useful place.
@Krinkle if I understand this correctly, resurrecting the privacy tag as an alias for privacy_engineering is not what we are ultimately looking for. We want privacy_engineering to only include work requests that are specifically being surfaced to the PE function of the Security team. There will likely be many tasks that may have some privacy implication which do not necessarily require PE services. @chasemp can I get a sanity check? This is my understanding of where security is going as well - many things may be tagged security but only tasks that need to have the security team look at them will be tagged security-team.
I'm merely proposing that if someone follows an old url like https://phabricator.wikimedia.org/tag/privacy/ or https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=privacy that instead of ending up somewhere they are definitely not looking for, they end up in a place that is related and actively looked at.
@Krinkle: Sounds like there is a misunderstanding here?
Privacy remains Privacy. This task is only about disabling the workboard of Privacy. This is not about disabling the Privacy project tag: Going to https://phabricator.wikimedia.org/tag/privacy/ , you would end up on https://phabricator.wikimedia.org/project/profile/1205/
Privacy Engineering is something separate and unrelated to this task. :)