Repo membership permissions

[flicstar]

On Thu, 7 Nov 2019 at 09:21, Felicity felicitybrand@gmail.com wrote: We need to broadly agree how we want to structure permissions.

Without knowing anything about GitHub permissioning:

We've got our PSC - I imagine they should all be administrators. We've got trusted project team members who need/want to contribute. We're about to have a whole lot of public folk who may contribute.

We've got a couple of repos:

• templates
• websites
• brand assets
• various meta

I know you can have 'teams' in GitHub - I've set up a couple for us but I don't think I've done it right.

So my questions are:

• Who gets what permission?
• How do we set that up?

Happy to do it, also happy to hand it over to someone.

---

On Thu, Nov 7, 2019 at 6:41 PM Cameron Shorter cameron.shorter@gmail.com wrote:

Re restrictions:

• I think that we only let trusted and proven writers to approve pull requests into our master branch (and possibly to a few other core branches). For the moment we can call this group our Project Steering Committee, although later we might find a need to create a new group. This link seems to show how: https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions
• External developers can branch into the personal git repositories, however there is a technical hurdle involved in working out how to do this.
• Currently external developers cannot create new branches in our repository. I think that we should enable this for a group of users we could call "contributors". People can ask to become a contributor, and with minimal vetting we then allow them to create branches in our repositories.

[flicstar]

@mgan59 check it out, just came across this. We talked about what you looked at today back in November. That's how long it's been hanging around. :-)