Undefined role 'github Administrator'

[bastelfreak]

Hi,
right now every PMC member as the Administrator status. Besides that there are 4 other people with that permission set:

• @rnelson0
• @daenney
• @ffrank
• @danzilio

It isn't clearly defined in our governance.md who is allowed to have these permission. Possible solutions:

• Only PMC role is allowed to have admin perms
• We create another role in our governance document
• something else

@voxpupuli/project-maintainers how do you think about that?

---

I'm fine with the first solution. Admin perms are rarely needed, also this seems to be the simplest solution.

[bbriggs]

also this seems to be the pimpliest solution.

I think we want to avoid those.

[roidelapluie]

If the PMC picks me as Security Officer, it might make sense for me to have access to the security logs etc...

[bastelfreak]

@bbatsov ups, fixed the typo

---

@roidelapluie good point. I think that should be discussed in another issue/pr to update the Security Officer role

[alexjfisher]

IIRC, I think it was @roidelapluie who around the time of the elections explained to me on IRC that...
One of the most important roles of the PMC, is to uphold the community code of conduct.

People shouldn't be running in PMC elections because they primarily are interested in getting admin rights.

PMC should probably all have admin rights, but I think they should also be able to 'elect' other admins in the same way they might elect a security officer/team, communications officer/team etc.

[nibalizer]

We should work out which tasks actually require admin permissions in github, then we should look at those and figure out if we think they should be pmc-only or not.

Some obvious things:

• Adding a collaborator
• Migrating in a repository
• Updating labels on a repository

We lay out in our governance document that adding a collaborator is a pmc only task.
The document is silent on a process to migrate a repository in.
Updating labels on a repository should be part of the migration process and will probably always require an administrator.

My sense is that the PMC should exist only to provide leadership and enforcement if normal self-organizing processes fail to work. In that mind, I'd say if a trusted individual wants to be an administrator, then that is fine by me. Lets make sure that person is a) willing to do the admin only tasks and b) willing to stay mostly plugged in to the happenings of the project so that they act in line with the rest of the administrators. I also think that all current PMC members should be admins.

[ffrank]

I follow along with what @nibalizer and @alexjfisher point out.

There should probably be some (very very little) process around managing these bits. Should we add some clause to the docs that describe what could prompt the ("forceful") removal of the bit from a person. (This should probably not be super specific. I would not want to paint negative scenarios in the guidelines.)

[bbriggs]

So someone gets nominated and a mail goes to pmc@? Someone in chat says "yeah, sure"? Both are fine with me.

[nibalizer]

We added roidalupe as he is security officer