From 287456a7d6f2fe42a3e76f82e6a3c2c1a292a575 Mon Sep 17 00:00:00 2001 From: Carolyn Van Slyck Date: Fri, 13 Jul 2018 12:53:31 -0500 Subject: [PATCH] Clarify that security contacts must adhere to embargo policy --- sig-service-catalog/charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-service-catalog/charter.md b/sig-service-catalog/charter.md index 5bf511701..62a856946 100644 --- a/sig-service-catalog/charter.md +++ b/sig-service-catalog/charter.md @@ -78,7 +78,7 @@ The following, non-exhaustive, items are out of scope: - Are a contact point for the Product Security Team to reach out to for triaging and handling of incoming issues. - Must be a maintainer. - - Must accept the Kubernetes [Embargo + - Must accept and adhere to the Kubernetes [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.md#embargo-policy). - Defined in [SECURITY_CONTACTS](https://github.com/kubernetes-incubator/service-catalog/blob/master/SECURITY_CONTACTS)