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:
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.
Sounds good to me.
cc @castrojo @parispittman
+1
On Thu, Dec 14, 2017 at 6:07 PM, Ihor Dvoretskyi notifications@github.com
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
https://github.com/kubernetes/community/issues/1511#issuecomment-351892755,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3JwYpa_VduLxcDVWVgScdjdt55gDmMks5tAdRagaJpZM4RC2yo
.
--
Michael Taufen
Google SWE
/close
teams have been removed as advertised
"I felt a great disturbance in the Force, as if millions of voices suddenly cried out in terror and were suddenly silenced."
/force close
Most helpful comment