Smoothest way to move Askar repos and artifacts to the OpenWallet Foundation

[swcurran]

With today's acceptance of Askar into OpenWallet Foundation as a project, we need to plan the move of the Askar 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 Askar. Opening this issue to get guidance from the maintainers to advise on the best approach to make is easy for those that use Askar 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, Cargo, NPM, 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 "Askar" and "askar". 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, where necessary, can we produce old and new name artifacts for a time period?

@TimoGlastra @berendsliedrecht @andrewwhitehead @jamshale

Thanks

[berendsliedrecht]

@andrewwhitehead can the libraries be renamed to askar instead of aries_askar? The JS wrapper is ready for this change, but I am unsure about the changes needed to be made to the Python wrapper.

[andrewwhitehead]

@berendsliedrecht It's a simple change in the Python wrapper to change the library name, I'll add a PR.

[andrewwhitehead]

Actually, there's a few more knock-on effects from renaming that would need some testing. I don't really see a need to rename the Python package, although we can rename the shared library that is produced by the build. The bundle produced by build-xcframework.sh produces a bundle with a hyperledger identifier which should be updated to foundation.openwallet.askar, although I don't know who would be affected by that change. Maybe we can get another release out first and then look at renaming the artifacts.

[berendsliedrecht]

All the JS related packages can be renamed (the iOS framework, etc.). We likely have to do a minor version update, but that is fine.