Smoothest way to move ACA-Py repos and artifacts to the OpenWallet Foundation

[swcurran]

With today's acceptance of ACA-Py into OpenWallet Foundation as a project, we need to plan the move of the ACA-Py repo to the OWF GitHub organization. While moving the repo will be easy (and the old URLs will automagically redirect), I'm more concerned about the artifacts that are generated from ACA-Py. Opening this issue to get guidance from the maintainers to advise on the best approach to make is easy for those that use ACA-Py to carry on through and after the transition.

Questions:

1. What are artifacts that we generate via GitHub actions, and what are they called?

• For example, PyPi, GHCR, and any others.

2. For each, how can we transition to a new name/namespace for those artifacts with the fewest impacts on downstream users?

• Note that we will be dropping the "Aries" part of the name, and just going with "ACA-Py" and "acapy". Please take that into account as we consider the transitions. We can retain "aries" if we need to, but ideally we transition away from that.
• For example, can we produce old and new name artifacts for a time period?

Thanks