+1 from me here... I don't have access to the pypi account tho I don't think. I am not sure who does. ;(

@abompard and @asaleh are both listed as maintainers on the main bodhi pages on pypi.

@mattia i see you now in the bodhi team on fedora-infra github (i guess @kevin did that yesterday):

https://github.com/orgs/fedora-infra/teams/bodhi/members?query=role%3Amember

so that should give you commit access.

chasing up someone to get you access to the pypi packges. just so we don't miss any, these are all the bodhi packages, right?

• https://pypi.org/project/bodhi/
• https://pypi.org/project/bodhi-client/
• https://pypi.org/project/bodhi-server/
• https://pypi.org/project/bodhi-messages/

@mattia i see you now in the bodhi team on fedora-infra github (i guess @kevin did that yesterday):

https://github.com/orgs/fedora-infra/teams/bodhi/members?query=role%3Amember

so that should give you commit access.

I've been in the bodhi group since a couple of years, I can approve PRs and manage bugs, but I've never had powers to push commits directly in any branch.
I'd like to be able to push directly to the main branch when tests are failing or we need to change required settings in the mergify file.
I think for being able to do that I need to be added in the bodhi-admin group... or a change to the bodhi group permission is needed.

chasing up someone to get you access to the pypi packges. just so we don't miss any, these are all the bodhi packages, right?

• https://pypi.org/project/bodhi/
• https://pypi.org/project/bodhi-client/
• https://pypi.org/project/bodhi-server/
• https://pypi.org/project/bodhi-messages/
  

Yes

I have rights to these, just to doublecheck, @mattia - https://pypi.org/user/mattia/ is you?

I have rights to these, just to doublecheck, @mattia - https://pypi.org/user/mattia/ is you?

yes, it's me.

Invitiations have been sent :)

Thank you all!
The only Bodhi related thing which is left is the Jenkins instance used to perform tests upon PR submission. I don't understand if I need a CentOS account to be able to login and manage it...

Also, the Jenkins instance we're using there has a banner that says we need to migrate to the new openshift CI cluster because "it will disappear soon". We also need the migration because the old instance is using CentOS 7 (as far I understand) and there's a bug which prevents f35 or newer docker based VM to run, so tests are failing.

But I think I should open a separate issue for that?

Current idea is to move to zuul, as there are few people at Red Hat dedicated to maintainig it, which could serve as a good middle ground between the barely maintained Jenkins we have and moving entirely to a hosted CI that wouldn't have budget for :)

Yeah, for jenkins you will want a centos-infra ticket... but yes, moving to zuul sounds like a great idea. ;)