- [project-leads] Proposal to change GH org permission structure for committers
Re: [project-leads] Proposal to change GH org permission structure for committers
Gabriel Rosenhouse <grosenhouse@...>
toggle quoted messageShow quoted text
Ok, so one thing that appears unobjectionable is that cloudfoundry-incubator org is only for incubation projects. If your team is a core project then you shouldn't be putting any repos in cloudfoundry-incubator.
On Thu, Dec 7, 2017 at 2:43 PM, Matthew Horan <mhoran@...>
I think this is an interesting idea. I have a couple of questions/concerns.
If I am in the runtime PMC and need to PR code to another PMC, where do I put my branch? It would seem that in the proposed configuration, I could not create a branch in another PMC's repo. Currently, this can be enabled on an ad-hoc basis as determined by individual teams, given the flexible model afforded by GitHub permissions. I'd hate to lose that ability.
Second, I have concerns about who would be able to modify repo settings under this proposed configuration. It wouldn't make sense to have everyone in a PMC have admin permissions to all repos belonging to the PMC. However, with our current configuration, it's possible to allow much finer grained admin control over repositories. I wouldn't want to introduce an additional burden on our teams for enabling integrations that require admin permissions, so I'm interested to know who would be selected as admins in your proposal.
Join email@example.com to automatically receive all group messages.