From cca9a053a2cbdb11cc942747df9ec68400e86bd6 Mon Sep 17 00:00:00 2001 From: Evan Anderson Date: Fri, 15 Jun 2018 12:50:16 -0700 Subject: [PATCH] Rename Elafros to Knative in community. (#1041) * Rename "Elafros" to "Knative" in community docs. * Update code-of-conduct address to separate from maintainers address. --- code-of-conduct.md | 2 +- config/config-logging.yaml | 2 +- sample/autoscale/sample.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 9c3b95c64d19..d94fbdf18708 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -56,7 +56,7 @@ further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at -knative-maintainers@groups.google.com. All complaints will be reviewed +knative-code-of-conduct@googlegroups.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of diff --git a/config/config-logging.yaml b/config/config-logging.yaml index 3f22c20114e9..059442de871e 100644 --- a/config/config-logging.yaml +++ b/config/config-logging.yaml @@ -18,7 +18,7 @@ metadata: name: config-logging namespace: knative-serving-system data: - # Common configuration for all Elafros codebase + # Common configuration for all Knative codebase zap-logger-config: | { "level": "info", diff --git a/sample/autoscale/sample.yaml b/sample/autoscale/sample.yaml index 27defc563077..4ca531a33b38 100644 --- a/sample/autoscale/sample.yaml +++ b/sample/autoscale/sample.yaml @@ -36,7 +36,7 @@ spec: # This is the Go import path for the binary to containerize # and substitute here. image: github.com/knative/serving/sample/autoscale - # When scaling up Elafros controller doesn't have a way to + # When scaling up Knative controller doesn't have a way to # know if the user container is good for serving. Having a # readiness probe prevents traffic to be routed to a pod # before the user container is ready.