From 34f2e3c77d6a09073e16b53d6b078462b5a2fc7a Mon Sep 17 00:00:00 2001 From: Marcin Owsiany Date: Wed, 18 Oct 2017 07:46:38 +0200 Subject: [PATCH] Change channel name for the rename. --- contributors/devel/scalability-good-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/devel/scalability-good-practices.md b/contributors/devel/scalability-good-practices.md index 23ed7e2aa..5769d248c 100644 --- a/contributors/devel/scalability-good-practices.md +++ b/contributors/devel/scalability-good-practices.md @@ -160,7 +160,7 @@ When designing new features/thinking about refactoring you should: - when adding complex logic make sure that you don't add it on a critical path of any basic workflow ## Closing remarks -We know that thinking about performance impact of changes that all of us write is hard, this is exactly why we want you to help us cater for it, by always having problems that we mentioned here in the back of your mind. In return we'll answer all your question and doubts about possible impact of your changes if you post them either to #sig-scale Slack channel, or cc @kubernetes/sig-scalability-pr-reviews in your PR/proposal. +We know that thinking about performance impact of changes that all of us write is hard, this is exactly why we want you to help us cater for it, by always having problems that we mentioned here in the back of your mind. In return we'll answer all your question and doubts about possible impact of your changes if you post them either to #sig-scalability Slack channel, or cc @kubernetes/sig-scalability-pr-reviews in your PR/proposal. * * *