+1 for giving sysadmin to Jiří, he has been contributing to Copr playbooks for more than 2 years already.

@praiskup @kevin Wouldn't it be better to give commit access to specific copr group? I see https://pagure.io/group/copr as potential candidate. That way COPR team can manage the access to playbooks by themselves.

Maybe sysadmin-copr (more matching group)? But note we have rights to add people to these copr-related groups, so we in turn would have the rights to allow people to commit (which might not be desired).

This is why I'm also mentioning @kevin I would like to hear his opinion on this.

sysadmin-copr is not in pagure.io. The groups are not automatically synced to pagure.io (we have a tool that can do that for you if needed), so not every group in FAS will work.

@praiskup is on PTO now, so please let me weigh in so this issue doesn't get blocked. I would say, that basically, we don't care. Whatever is the best solution for you as Fedora Infra, we are fine with that. We just need @nikromen to be able to push directly to https://pagure.io/fedora-infra/ansible

99% of our work is done within:

• https://pagure.io/fedora-infra/ansible/blob/main/f/roles/copr
• copr-* playbooks in https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups
• copr_* files in https://pagure.io/fedora-infra/ansible/blob/main/f/inventory/group_vars

so if you want to somehow limit his permissions to only these files, that would be fine too. But it is IMHO not needed because we have a gentlemen's agreement that if we do changes outside Copr, we submit them as PRs.

The changes should still be submitted as PRs, you will just have the permission to merge them.

No objections here... I will add them in pagure.io for the ansible repo.

Added them to fedora-sysadmins there. ;)