How can we best handle local channels in WordPress global Slack?

In State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. 2023 (on December 11), Matt commented that it would be good to allow the local communities to have their own channels inside the global “Making WordPress” SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. instance.

The various “Local Slack” teams the Polyglots’ mentors are currently aware of are listed in https://make.wordpress.org/polyglots/handbook/translating/teams/local-slacks/

Having an approval for central channels is a good start. But for this to work, we need to figure out:

1. How many (and what) channels we’re going to need in the global instance?
2. Should bigger localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ be allowed to have several channels (say: marketing, support, translations, etc…) in the global instance?
3. How are we going to administrate all this?
4. Do we still need to keep (at least some of) the local teams (actually – I know this is a yes, since Slack blocks certain countries and territories from service.)
5. What else do we need to figure out, and whom do we need to involve.

I’m going to cross-post a bit to some more teams and would like feedback until around Jan 3rd (or so).

Then in January we may start some more organized activity on this.

Tobi ( @tobifjellner )