Paul,

 

I'm happy to help you with the GH things.  Your asks seem reasonable to me.  I'll talk with the team about the quay.io/containers stuff but I don't believe we have given folks access to that before; so there is no precedent.

 

Of the core containers repositories, we do require DCO signoff and will generally fail the PR if it is not included.  If you are indifferent about it, my preference would be to require it.

 

On Thu, Apr 25, 2024 at 9:20 AM Paul Nettleton via Podman <podman@lists.podman.io> wrote:

Hello everyone!

I'm not sure if this is the best place to ask, but I have a few questions regarding finalizing the migration of podlet to the containers org.

I would like to create a "podlet-maintainers" team so that I can add it as an owner of podlet on crates.io. This would allow anyone on the team to publish new versions, improving the bus factor. Is it ok for me to do this? I asked about it on the migration issue, but didn't receive a reply.

I was thinking that it would make sense to move the podlet container image from quay.io/k9withabone/podlet to the quay.io/containers org. What would be the process for getting that started?

It seems that I have lost some privileges in the transfer of the podlet repo as I can no longer access the repository settings, including setting secrets for use in CI. I will probably need to be able to update those if quay.io/containers/podlet is created. Would it be possible to give me the "maintain" role for the podlet repo?

I noticed on my PR for switching compose libraries that a check for commit sign off was added. Is this a requirement for all repositories in the containers org? I don't mind having to sign off commits, but a CONTRIBUTING.md file should be added to the podlet repo explaining this if it is required.

Thanks for your time,
Paul / k9withabone

-- 
Paul Nettleton
k9@k9withabone.dev _______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io