Review and update github access for read/write/maintainers

[edwinjue]

Overview

We need to clean up the GitHub team permissions on this project, so that everyone has the appropriate level of access.

Action Items

• Open the roster (resource 1.01.01)
• find a row that is blank in column M
• click on the link in column L (same row)
• annotate what you find
  • If user is on read and write team, add the following text to column M
  • if user is on write team and not on read team, add to read and the following text to column M

  write
  

  • user is on read team but not on write team, add to read and the following text to column M

  read
  

  • if user is on neither team, add the following text to column

  none
  

• view the roster by inactive (resource 1.01.02)
• look up each GitHub username on the write team, and if there, remove them update the value in column M to "read"
• Add to agenda for review with org rep

Resources/Instructions

• 1.01 311-data team roster
  • 1.01.01 311-data team roster, Permissions to update and document filter
  • 1.01.02 311-data team roster, inactive filter

Teams

• 311-data
  • 311-data-write
    • 311-data-maintainers
      • 311-data-admin

Permission Rules

breakdown of who should be granted access to the three tiers of permissions for our repo:

Details by team

311-data (read access):
All users (should include ex-311 data members, if removed from write/maintainers, make sure to add them here)

311-data-write:
All active 311 participants marked active as per roster (may need to update who is active/inactive on roster as well)

311-data-maintainers:
(this is different from being a maintainer on another GitHub team e.g., write-maintainer, read-maintainer, which enables you to add and remove people from the team)
Confirm with @ExperimentsInHonesty (Bonnie) to determine who should still be here no one, we don't use this team, but we are leaving it for now

311-data-admin:
One PM (so that they can edit issue templates), possibly the tech lead if they need it for something specific like setting up branch protections. Permission should be removed when they no longer need it.

[ryanfchase]

Updating labels assigning current PMs.