To be honest, I think we’re taking this the wrong way. I think, commit access to foreman core should be justified by helping to maintain the codebase. I don’t want to have a loop-hole. I can only speak for myself, but the way I see it is the following: I have commit access to core, but don’t have commit access to packaging. And I think, that’s totally fine. I haven’t earned that right in foreman-packaging. This is not an issue of not trusting people (I do) or not needing help (we do), but contributors should get a proper review and people need to know the codebase and product well to make a proper review. I think commit permissions should be earned.
When releasing a plugin, one of my release todos is to send PRs to foreman-packaging to update the packages. Can’t we agree, that we only merge core PRs that have a corresponding packaging PR when needed? Ideally, a contributor would file the PR with the core PR. If that’s too much to ask, a maintainer can either help and file the PR or as someone from the packaging team for help. We don’t need any special permissions or loop-holes permissions for that.
Just my 2 cents. I hope, we find an easy solution for our issue. That is broken nightlies.