Remove direct write access to this repo #1511

spiffxp · 2017-12-15T00:29:07Z

We now have sufficient automation in place to address most if not all of the use cases that would require direct write access to this repo:

https://community.submit-queue.k8s.io: we allow people without direct write access to merge via /lgtm, /approve, and OWNERS files
https://go.k8s.io/bot-commands: we allow people who are org members to assign, triage, and manage issues and their labels via /commands

I propose we revoke direct write access to this repo for the following github teams:

This would leave us with the following teams having direct write access:

And with the following teams having admin access:

If I get no wild objections by 2017-12-20 I will go ahead and remove as described above.

idvoretskyi · 2017-12-15T02:07:05Z

Sounds good to me.

mtaufen · 2017-12-16T01:42:02Z

+1

On Thu, Dec 14, 2017 at 6:07 PM, Ihor Dvoretskyi ***@***.***> wrote: Sounds good to me. cc @castrojo <https://github.com/castrojo> @parispittman <https://github.com/parispittman> — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#1511 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3JwYpa_VduLxcDVWVgScdjdt55gDmMks5tAdRagaJpZM4RC2yo> .

-- Michael Taufen Google SWE

spiffxp · 2017-12-20T21:42:15Z

/close
teams have been removed as advertised

cblecker · 2017-12-20T21:44:42Z

"I felt a great disturbance in the Force, as if millions of voices suddenly cried out in terror and were suddenly silenced."

liggitt · 2017-12-20T21:45:25Z

/force close

spiffxp mentioned this issue Dec 18, 2017

Add committee/foo label support to prow label plugin kubernetes/test-infra#4106

Closed

k8s-ci-robot closed this as completed Dec 20, 2017

spiffxp mentioned this issue Dec 21, 2017

deprecating wiki pages #116

Closed

18 tasks

Provide feedback