hackforla / admin-governance

Hack for LA's Core Team proceedings
2 stars 5 forks source link

Cleanup of the HackforLA github permissions #14

Open ExperimentsInHonesty opened 5 years ago

ExperimentsInHonesty commented 5 years ago

Updating the permission of people on the HackforLA github top level:

thekaveman commented 5 years ago

This is a timely review @ExperimentsInHonesty, thanks for bringing it up. Here's the current state of the hackforla organization:

  1. Should we change the base permission to Read or None?
  2. Should we allow all members to create new repos by default or not?
  3. Should we remove all other non-core members from the organization? We may risk someone losing access to a repo temporarily.

With more restrictive base permissions for members, we can look at using Teams to group for related access and permissions.

ExperimentsInHonesty commented 5 years ago

I have been reading up on good opensource repo management and I still have a lot of discovery to do before I really understand the best way forward. And then maybe you can provide more insight in person on Monday and we can come up with a strategy.

thekaveman commented 5 years ago

Open tasks:

Members

Teams

For projects, create at least three distinct teams, in a relationship as follows:

  1. project (parent - read access)
  2. project-managers (child - write access)
  3. project-admins (grandchild - admin access)

Outside Collaborators

There are currently 74 Outside Collaborators.