Merge branch 'master' of https://github.com/kubernetes/community into sc-election-2020

Author: jberkus

.github/ISSUE_TEMPLATE/support.md

@@ -1,7 +1,7 @@
 ---
 name: Support Request
 about: Support request or question relating to Kubernetes
-labels: triage/support
+labels: kind/support
 
 ---
 

CLA.md

@@ -1,6 +1,6 @@
 # The Contributor License Agreement
 
-The [Cloud Native Computing Foundation](https://www.cncf.io/community) (CNCF) defines
+The [Cloud Native Computing Foundation](https://www.cncf.io) (CNCF) defines
 the legal status of the contributed code in two different types of _Contributor License Agreements_
 (CLAs), [individual contributors](https://github.com/cncf/cla/blob/master/individual-cla.pdf) and [corporations](https://github.com/cncf/cla/blob/master/corporate-cla.pdf).
 

OWNERS_ALIASES

@@ -77,7 +77,7 @@ aliases:
     - tabbysable
   sig-service-catalog-leads:
     - jberkhahn
-    - mszostok
+    - jhvhs
   sig-storage-leads:
     - jsafrane
     - msau42
@@ -116,11 +116,6 @@ aliases:
     - bartsmykla
     - dims
     - spiffxp
-  wg-lts-leads:
-    - imkin
-    - quinton-hoole
-    - tpepper
-    - youngnick
   wg-multitenancy-leads:
     - srampal
     - tashimi
@@ -132,11 +127,10 @@ aliases:
   wg-policy-leads:
     - ericavonb
     - hannibalhuang
-  wg-security-audit-leads:
-    - aasmall
-    - cji
-    - jaybeale
-    - joelsmith
+  wg-reliability-leads:
+    - deads2k
+    - stevekuznetsov
+    - wojtek-t
   ug-big-data-leads:
     - erikerlandson
     - foxish
@@ -164,10 +158,10 @@ aliases:
     - cblecker
     - derekwaynecarr
     - dims
-    - lachie83
+    - liggitt
+    - mrbobbytables
     - nikhita
     - parispittman
-    - spiffxp
 ## BEGIN CUSTOM CONTENT
   provider-aws:
     - d-nishi

incubator.md renamed to archive/incubator.md

@@ -0,0 +1,26 @@
+Dear Steering Committee:
+
+
+We propose the creation of a new Kubernetes SIG: SIG Security.
+
+
+In managing the Third-Party Security Audits, the Working Group realized that its efforts didn’t end with the completion of each audit. The audit’s process and findings demonstrated the need to advocate for stronger security defaults, facilitate outreach for both developers and end-users, and drive structural security improvements.
+
+At KubeCon San Diego, we presented the results of the audit with a call to action for the broader community to take the findings and drive them into a better, more secure, Kubernetes. We were met with far more support than we could reasonably channel in our current form.
+
+We worked with members of SIG Auth, the Product Security Committee, the SIG Docs Security subproject, and the CIS Benchmark maintainers to identify underserved aspects of their domains. To express the scope and responsibilities of the new SIG, we all collaborated on a draft charter for your consideration. 
+
+We hope that the entire group behind this draft charter can serve the Kubernetes project via this SIG.
+
+Thank you.
+
+Signed,
+
+
+Aaron, Craig, Jay, Joel, Tim, Ian, Micah, Seth, Peter, Rory, Liz 
+
+
+
+You can find our proposed charter in this pull request:
+
+https://github.com/kubernetes/community/pull/4962/commits/535d9eab9c37826edd39d79f70e94f51330bb15c

wg-lts/README.md renamed to archive/wg-lts/README.md

@@ -0,0 +1,43 @@
+# Onboarding and offboarding new Code of Conduct Committee members
+
+Different actions on this list must be carried out by different members: 
+
+- **Outgoing members:** members who are ending their term
+- **Incoming members:** members beginning their term
+- **Carryover members:** members mid-way through their term
+
+## Permissions 
+
+### Slack
+
+**Who executes:** When offboarding, outgoing members must remove themselves from Slack channels. When onboarding, carryover members must add incoming members.
+
+- [ ] Code of conduct committee Slack channel on `kubernetes.slack.com`
+- [ ] Code of conduct sync Slack channel on `cloud-native.slack.com`
+
+### Kubernetes/community permissions and google permissions
+
+**Who executes:** Carryover members should ensure that outgoing members are removed and incoming members are invited. 
+
+- [ ] Update `kubernetes/community` [`sigs.yaml`](https://github.com/kubernetes/community/blob/master/sigs.yaml) 
+- [ ] Update `kubernetes/k8s.io` [`groups.yaml`](https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml)
+
+    > **Note:** This file controls access to the mailing list and Google Drive! If you do not update this file, adding people manually (via the UIs) continually revert until this file is updated.
+
+    - [ ] `[email protected]` mailing list
+    - [ ] Google drive
+
+## Communications 
+
+**Who executes:** Anyone but outgoing members!
+
+- [ ] Give an update at the monthly Community meeting
+- [ ] Send an email to the `kubernetes/dev` mailing list
+
+## Knowledge transfer and group procedures
+
+**Who executes:** Carryover members should lead
+
+- [ ] Introduce new members to relevant contacts
+- [ ] Re-evaluate weekly meeting time
+- [ ] Schedule training and knowledge management sessions for new members