Rename the repo to `safe-smart-account` about safe-smart-account

[nlordell]

Regarding:

• https://github.com/safe-global/safe-core-sdk

Can we notify the SDK team in Slack about this?

[akshay-ap]

Create npm release of 1.4.1, 1.3.0 builds?

Not required by SDK team. We will consider deploying old version if required.

[akshay-ap]

Going with the second approach:

To do

• Rename repository
• Find and replace all links in this repository
• Update README.md: https://github.com/safe-global/safe-contracts/blob/b140318af6581e499506b11128a892e3f7a52aeb/README.md?plain=1#L1 and links as well
• Update links in CHANGELOG.md
• Update package name and links in package.json: https://github.com/safe-global/safe-contracts/blob/b140318af6581e499506b11128a892e3f7a52aeb/package.json#L2
• Create npm release of 1.4.1, 1.3.0 builds? Answer: No

Safe repositories that need to be updated for future releases:

• https://github.com/safe-global/safe-modules
• https://github.com/safe-global/safe-core-sdk
• Update links in docs: https://docs.safe.global/safe-smart-account/signatures/eip-1271#example-verify-signature

Other potential other sources on Github that need to be updated for future releases: https://github.com/search?q=%40safe-global%2Fsafe-contracts&type=code&ref=advsearch

[compojoom]

What does "easier discoverability" mean? Repos are not "app stores" where you look for the coolest name. Not sure what is requiring such a change, but I think it is useless and would just burden developers who would think - there is no new release where in reality the code lives under a new package name.

It's the same situation with @gnosis.pm/safe-contracts. There are projects that use those and never update to @safe-global/safe-contracts.

I hope that you've realy thought out that well.

[mmv08]

Repos are not "app stores" where you look for the coolest name.

Yes, but at the same time, names should be descriptive. What does safe-contracts mean? Is it the safe{core} protocol? Are they safe token contracts? Is it the vesting contract? Is it modules? We grew past the stage where safe-contracts could only mean the account contracts.

It's the same situation with @gnosis.pm/safe-contracts. There are projects that use those and never update to @safe-global/safe-contracts.

They should pay more attention to the output when installing dependencies then. Usually, there's a message if the package has migrated to a new one.

I do not buy the argument because the existing tools allow us to perform the migration smoothly with aliases, warnings and stuff.