Name conflict

[lee-b]

harbor is a very well-known name in containerisation circles, for https://goharbor.io/. Difficult step, but I'd suggest renaming this (even in a small, subtle way, like to harbor-ai, to avoid confusion/conflict. I think it would be better to do this sooner rather than waiting until the project gets bigger, as it will only get harder to change as more people know the name.

[av]

Thanks for raising this, I'm considering a few possible options:

• domainify the name: harbor.sh for example, exactly after the CLI name
• use a self-expanding acronym that'll include Harbor in it's name, for example HBR - Harbor Bash Resource

I agree that it could be a concern, but I doubt that Harbor will ever be big enough for people to actually confuse it with the docker registry counterpart, similarly to how there are libraries with identical names in different languages and the naming conflict isn't a big problem due to semantic distinction