Per-package merge permissions in foreman-packaging for plugin maintainers

[nadjaheitmann]

Sure. I am cool with ATIX people breaking ATIX plugins

We now have an atix-foreman-packaging Team

Build software better, together

[evgeni]

I can’t see that group (not being part of the ATIX org, I guess).
It needs to be in the theforeman namespace

[nadjaheitmann]

Not sure if we can create groups there.

[evgeni]

You can’t, that’s why I said give me a list of GH usernames

[evgeni]

Actually, not true!
I’ve just created Sign in to GitHub · GitHub and made you a maintainer of that team, so you should be able to add everyone

[nadjaheitmann]

I’ve just created Sign in to GitHub · GitHub and made you a maintainer of that team, so you should be able to add everyone

Perfect, thanks!

[ekohl]

@evgeni

@ekohl

I restricted creation of branches, but release owners will need to create those branches at some point. They’ll need to be able to bypass that. We probably need a specific ruleset for that.

I thought about that, but our branching process says the release engineer is branching packaging, and those are already on the bypass list via the “maintain” role.

That’s true. I was thinking about applying similar rulesets in more repositories. I think the Base ruleset also makes sense in our core repositories, but then with a slightly adjusted bypass list. Of course, out of scope for this RFC but I like being consistent and currently we’re not.

[evgeni]

add codeowners

add codeowners

add codeowners

[evgeni]

This is now implemented for REX, Discovery, Bootdisk and “ATIX”

@nadjaheitmann also suggested Puppet, Salt, Proxmox and Kernel Care, which I’ll gladly add once a few PRs got merged and the flow as such seems to work fine enough