Too many people with admin rights in the RootsDev GitHub Organization

52 views
Skip to first unread message

Justin York

unread,
Apr 23, 2014, 2:53:33 PM4/23/14
to root...@googlegroups.com
There are 29 people that have administrator rights for our GitHub organization. Here's the full list, for those that can see it: https://github.com/orgs/rootsdev/teams/owners

29 is too many. I think 5-10 is enough. I prefer 5. We should create a new team that has read/write access to all repos and put all of the remaining people there.

How do we choose who the 5-10 remaining admins are?

Dallan Quass

unread,
Apr 23, 2014, 2:55:37 PM4/23/14
to root...@googlegroups.com
I've been thinking that we need to create teams within the organization as well.

Is there a way to measure everyone's activity level?


--

---
You received this message because you are subscribed to the Google Groups "rootsdev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rootsdev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

todd.d....@gmail.com

unread,
Apr 23, 2014, 7:17:25 PM4/23/14
to root...@googlegroups.com
I remain a lowly non-team member. <weeping/>
--
Tod Robbins
Digital Asset Manager, MLIS

Justin York

unread,
Apr 23, 2014, 10:03:42 PM4/23/14
to root...@googlegroups.com
Dallan, do you mean to measure a user's activity within the organization? I don't know of any way.

It turn's out there's a difference between Owners and Admins. In that context, I'm concerned about too many owners. I'm okay with tons of admins because it's a pain to be part of an organization if you can't create repositories. I'm going to create a team with admin rights and add new people there for now.

Michael Bean

unread,
Apr 23, 2014, 10:04:35 PM4/23/14
to root...@googlegroups.com
You can take off my write access if you wish. I'm more of a watcher/beta tester when needed more than a developer for rootsdev (for now).

Michael Bean

unread,
Apr 23, 2014, 10:05:07 PM4/23/14
to root...@googlegroups.com
You can make me an admin instead of an owner if you wish.

Luther Tychonievich

unread,
Apr 24, 2014, 12:42:24 PM4/24/14
to root...@googlegroups.com
So, as I understand it what owners can do that admins cannot is add new users, switch who is on what team, and edit the account information itself. I don't even want the responsibility of doing those things, so I added myself to the admin account "members" and removed myself from "owners." I'd encourage others who don't see themselves administering the account as a whole to do the same. Perhaps this problem can go away by voluntary migration.


On Wed, Apr 23, 2014 at 10:05 PM, Michael Bean <Bean.M...@byu.net> wrote:
You can make me an admin instead of an owner if you wish.

--

Dallan Quass

unread,
Apr 27, 2014, 3:36:52 AM4/27/14
to root...@googlegroups.com
It's been a few days and we still have 28 owners. I'm thinking perhaps we ought to try the other approach and ask people to say something if they'd like to continue to be in the owners group. Would doing that be too presumptuous?

Ben Brumfield

unread,
Apr 27, 2014, 9:17:38 AM4/27/14
to root...@googlegroups.com
That'd be my vote.  I originally added a lot of the members to the admin group in order to let them edit wikis and github pages, so I can attest that most of the administrators didn't actually ask to be admins per se.

Ben

Daniel Zappala

unread,
Apr 27, 2014, 5:13:57 PM4/27/14
to root...@googlegroups.com
You can take me off the list if you like.

Justin York

unread,
Apr 27, 2016, 6:00:51 PM4/27/16
to rootsdev
Two years later and permissions were still a mess. Thankfully the recent changes to GitHub organization permissions make it easy. I removed all but 5 owners and turned everyone else into regular members that have permission to create new repos and push to repos they've created. Let us know if you need push access to a repo and don't have it.
Reply all
Reply to author
Forward
0 new messages