From 7664de0ce66aa416c695570e4f021a3d00b5e60b Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Mon, 20 Feb 2023 18:21:16 -0600 Subject: [PATCH] add year prefix for temp channels (#9965) --- handbook/business-operations/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/handbook/business-operations/README.md b/handbook/business-operations/README.md index f61bea098..a33f46a6b 100644 --- a/handbook/business-operations/README.md +++ b/handbook/business-operations/README.md @@ -210,10 +210,11 @@ We configure our [working hours in Slack](https://slack.com/help/articles/360025 #### Slack channel prefixes We have specific channels for various topics, but we also have more general channels for the teams at Fleet. We use these prefixes to organize the Fleet Slack: - * ***g-***: for team/group channels *(Note: "g-" is short for "grupo")*. + * ***g-***: for team/group channels *(Note: "g-" is short for "grupo" or "group")*. * ***oooh-***: used to discuss and share interesting information about a topic. * ***help-***: for asking for help on specific topics. * ***at*** or ***fleet-at***: for customer channels. + * ***2023-***: for temporary channels _(Note: specify the relevant year in four digits, like "YYYY-`)_ #### Slack communications and best practices In consideration of our team, Fleet avoids using global tags in channels (i.e. @here, @channel, etc).