Proposed updates to GitHub teams

Justin Obara obara.justin at
Thu Aug 11 18:07:54 UTC 2016

When we first made the move to Git and started using GitHub to host our
source code we set up teams to help us organize the permissions for our
various repos. Over the years the contributors, maintainers, and
repositories have all undergone many changes. On top of that GitHub has
updated the way teams work and the permissions structure. (see: Setting up
and managing organizations and teams

I’d like to take some time to clean up our repository space so that it is
up-to-date. To that end, I propose the following changes:

   - Migrate all teams from legacy teams
   - Remove “Owners” team - owner permissions can now be set per user
   - Remove “Contributors” team - was an attempt to identify contributors
   to projects, but it’s hard to maintain and a list of contributors can be
   displayed in each repository
   - Rename “Committers” to “Maintainers” ( this is more idiomatic to dvcs )
   - Rename “Committer Emeriti” to “Maintainer Emeriti”
   - Update teams membership as needed ( note: this will not include
   changes that require formalized voting )
   - Transition of “acheetham” to the “Committer Emeriti” team
   - Restrict repository creation to the Maintainer and Ops teams.
   - Other minor tweaks as needed

One handy new feature from GitHub is that you can @mention public teams.
For example in a PR that needs some design help you could ping @Designers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list