search

w3c / using-github

Obsolete repo; see https://github.com/w3c/modern-tooling and https://github.com/w3c/w3c.github.io
MIT License
3 stars 7 forks source link

Eliminating staff intervention for low risk admin tasks #10

Closed AFBarstow closed 8 years ago

AFBarstow commented 9 years ago

As a chair of WebAppsWG (which has relatively large number of repos https://github.com/orgs/w3c/teams/webapps/repositories and more coming), I often need to do some admin related tasks for which I do not have sufficient permissions. As such, this means I must send a request to a W3C staff member (or some list) and then block while waiting for the task to be completed. This is of course not productive/efficient for me nor the staff.

To help address this problem, people like me should have permissions to do at least the following low risk tasks without staff intervention:

Perhaps others have additional tasks to add.

/Cc @ylafon @siusin

darobin commented 9 years ago

There are two aspects to this question.

The first is to check that the GitHub ACL system hasn't changed since our last appraisal. It is possible that it is now less tangled up than it used to be and that we could in fact grant some admin rights to chairs, who could then carry out these tasks. (I'm assigning this issue to myself to look into that).

The other is indeed creating a tool for this purpose. See http://w3c.github.io/modern-tooling/#de-facto-github

tripu commented 8 years ago

For this, worth looking into the improved organization permissions that were rolled out recently…

tripu commented 8 years ago

(OK, this is interesting… @darobin, I don't know what $%& I've done to unassign you; it wasn't intentional. And now I don't seem to be able to assign you again! :¬?)

tripu commented 8 years ago

@AFBarstow, after reading a bit more about the new permissions on GH, this is my understanding:

Only organisation owners can do that… but that's a very powerful role, that I believe we should not give to non-staff. So I'm afraid staff intervention is and will be required for this.

An owner can make any team member a team maintainer, and then that person can add and remove members to/from that team himself. I suggest that chairs request staff to have that status for a specific team from now on, and that should make them more autonomous.

WDYT?

tripu commented 8 years ago

I'll be closing this issue soon if there's no activity (as we're abandoning this repository in favour of w3c/w3c.github.io and w3c/modern-tooling).