On Wed, Oct 27, 2021 at 6:19 PM Nir Soffer <nsoffer(a)redhat.com&gt; wrote: If that's all you want, I guess you should simply open an infra ticket, no? Perhaps do something slightly different: Use a subdir, or a subdomain, such as go.ovirt.org/imageio or ovirt.org/go/imageio, and ask for this place to be managed using a git repo somewhere (in gerrit or elsewhere), so that when you merge there stuff, something updates the namespace automatically. This way you do not need to ping infra per each project. Best regards, -- Didi

On Wed, Oct 27, 2021 at 6:18 PM Nir Soffer <nsoffer(a)redhat.com&gt; wrote: I found that this does not work, Go tools do not support a module not in the root directory of a git repo. We have several options to solve this: 1. Create new git repo for the Go imageio library 2. Publish the library using "github.com/ovirt/ovirt-imageio/imageio-go" 3. Serve the module from our web server (e.g. resources.ovirt.org) using the go proxy protocol. I don't like option 1 since adding more tiny repos makes it harder to work with the code and test it. We already have too many repos. I don't like option 2 since this import path is horrible, and I don't want to tie the project to github. Option 3 is easy to implement - for every release you create a zip file with the module, and few metadata files, and upload them to a web server pointerd by the "go-import" meta tag. We have the same problem with libnbd Go binding, and option 3 is likely the right solution for it for similar reasons. I want to get your input on this. Nir