Closed swcurran closed 1 year ago
I like aries-(a)capy-askar-migration, maybe aries-cloudagent-python-migration and then it could be reused later for other migrations.
I think we use aries-acapy-migration
. acapy
because we have precedence in using that for Aries Cloud Agent Python related repos, and migration for Andrew’s last point of using it again in the future if needed. I don’t think we need to do anything now to structure for future migrations — we’ll deal with that when the time comes.
Any objections or suggestions?
Another option might be aries-acapy-tools
?
Interesting. Would you suggest we restructure the repo ahead of that. Move the askar-wallet-upgrade
related items down a level, to leave room for more tools?
@dbluhm — would it take much effort to move things around and document accordingly?
The repo files — MAINTAINERS.md, CONTRIBUTORS.md, LICENSE.md etc. remain at the top, almost everything else moves down a level.
Nope, wouldn't be too bad to shuffle directories if we want to go that way. I think I lean towards bookmarking the repo as a good place to turn into a general tools repo but wait until we have another tool that needs a home
OK — so just rename it for now.
@ryjones — I don’t have the power to change the repo name — could you please do that? aries-acapy-tools
Thanks
@swcurran edit this file
Thanks — PR submitted. Nice!
The use “wallet” in this repo is likely confusing. How about we rename it now while it is new?
Other options:
@dbluhm @cjhowland @andrewwhitehead — thoughts?