Describe the feature
Switch Go module paths for OpenCHAMI repos from github.com/OpenCHAMI/* to github.com/openchami/*.
Why do you want this feature?
The canonical path for Go modules in OpenCHAMI has been determined to be github.com/openchami/* instead of github.com/OpenCHAMI/*.
According to https://go.dev/ref/mod#goproxy-protocol:
To avoid ambiguity when serving from case-insensitive file systems, the $module and $version elements are case-encoded by replacing every uppercase letter with an exclamation mark followed by the corresponding lower-case letter. This allows modules example.com/M and example.com/m to both be stored on disk, since the former is encoded as example.com/!m.
Meaning that Go treats module paths is case-sensitive when storing the modules on the filesystem.
Certain import errors have also come up (e.g. "module imported as github.com/openchami/... when module is declared as github.com/OpenCHAMI/..."). The newer, fabrica-based services have started using the lower-case path while the older services are still using the title-case one. They should be made consistent to avoid confusion.
Alternatives you've considered
- Leaving inconsistent (cause of confusion in first place)
- Keeping "OpenCHAMI" (canonical paths tend to be lower case)
Additional context
No response
Code of Conduct
Describe the feature
Switch Go module paths for OpenCHAMI repos from
github.com/OpenCHAMI/*togithub.com/openchami/*.Why do you want this feature?
The canonical path for Go modules in OpenCHAMI has been determined to be
github.com/openchami/*instead ofgithub.com/OpenCHAMI/*.According to https://go.dev/ref/mod#goproxy-protocol:
Meaning that Go treats module paths is case-sensitive when storing the modules on the filesystem.
Certain import errors have also come up (e.g. "module imported as github.com/openchami/... when module is declared as github.com/OpenCHAMI/..."). The newer, fabrica-based services have started using the lower-case path while the older services are still using the title-case one. They should be made consistent to avoid confusion.
Alternatives you've considered
Additional context
No response
Code of Conduct