Slack workspace reorg proposal

[derberg]

Proposed official channels:

01_introductions (NEW)
    topic: Welcome to our AsyncAPI Slack! Take a moment to introduce yourself.
02_general (old general)
    topic: Talk here if your topic is not only about the spec, nor tools but kinda mix and not only but involves AsyncAPI :)
03_specification (NEW)
    topic: All around the spec discussions. It is ok to ask for support here.
04_tooling (old tooling)
    topic: All around the spec tools discussions. It is ok to ask for support here.
05_promotion-and-marketing (old promotion-marketing)
    topic: Purpose of this channel is to help us with AsyncAPI promotion. Share your ideas for marketing and learn what we are working on at the moment. We use “channel” annotation here when we want to ask you to share our specific resources on different social media.
06_training (old training)
    topic: All about trainings, workshops, courses, etc. — https://github.com/asyncapi/training.
07_events (NEW)
    topic: At least once a year we need to organize an event that makes a lot of noise around AsyncAPI. Sometimes it is a conference, meetup or a hackathon. This is the place where we regroup and organize. This is also a place where you should always let others know what events are you involved in, where and when do you present a topic related to AsyncAPI. Looking for a speaker that can talk about AsyncAPI? Ask here.
08_jobs (NEW)
    topic: Looking for a job that will let you work on AsyncAPI? Let others know. Looking for AsyncAPI expert to join your company, post your offer here and also on the AsyncAPI website https://www.asyncapi.com/jobs.
09_not-humans (NEW)
    topic: Sometimes you're just tired of humans. Share your love to non-humans. Pics or it didn't happen!
10_watercooler (old random)
    topic: Talking about things that are off-topic. Get to know folks' other interests that aren't around AsyncAPI :) When you have a need to talk to someone "in person", join this zoom meeting, if no one is there, ping folks in the channel that you are looking for a connection. Talking to another human solves many problems.
97_bot-github-new-issues-prs (old github-new-issues-prs)
    topic: Bot sends notifications about every new issue and pull request in any AsyncAPI repository.
98_bot-github-releases (old github-releases)
    topic: Bot sends notifications about every new release in any AsyncAPI repository.
99_bot-twitter-mentions (old twitter-mentions)
    topic: Bot sends notifications about every new tweet where AsyncAPI is mentioned.

Why N_ prefix. I copied it from one of my favorite workspaces (the community club) where everything is well organized:

• Prefix brings order and structure
• Prefix indicates that a given channel is officially maintained
• We all can easily and proactively educate all members about where to go with a given topic

Other comments:

• Channels that are not on the above list will be removed
• Every new joiner gets a welcome message from a bot that introduces channels and the protocol
• We will use @channel annotation in general channels once all the changes are done in the system, so members that are already here are aware of the reorg
• There will be a new repository called support where only Discussions will be enabled. We will use it as an archive for topics we discuss on Slack. How? I will write a bot that reacts to specific emoji (a sign of infinity) called infinity/forever. If emoji is added to a main message, bot will save it with entire thread as new discussion item in the support repository. This is important even if someday we can afford Standard subscription on slack and unlimited messages history. This solution will make it very easy to access all the important discussions we had in slack from one location. Another cools stuff about this solution is that we will be able to write another bot that suggests answers to questions in Slack basing on the data from Discussions ❤️
• the etiquette will be part of .github repository, so any changes to it will go through a usually approval process over pull request
• why Slack and not something else? why not? every tool has its advantages and disadvantages, so let us just optimize Slack. why we need Slack or any other messaging tool? because we want to stay close with those that are most active in the community, have an option to establish connection other than email

Slack Etiquette aka Protocol:

• Respect each other. Choose empathy over judgement. Act according to the AsyncAPI Code of Conduct
• Run discussions in threads. Every singe message in a main thread triggers notification, another message about the same triggers another notification. Let us not ping each other when it is not necessary. Always reply to a message in a thread.
• Avoid using @channel and @here unless the description of a given channel states differently.
• Once you post a message with links. Remove generated previews. Leave them only if they add some more context to the message.
• In case you need a dedicated channel for some discussion, feel free to create it but don't use N_ prefix that is allowed only for officially maintained channels.
• When you mute some channel, we encourage you to configure alerts for discussions that are most interesting for you. We do not want to loose your input. Go to Settings -> Notifications -> My keywords section.

[MikeRalphson]

Unsure about the N_ prefix, but that's probably just unfamiliarity. 👍🏼 to everything else.

[aayushmau5]

How about a help channel as well? Are we going with tooling and general for people to get help?

[derberg]

Unsure about the N_ prefix

@MikeRalphson yeah, you just need to see it in action, but basically, channels are by default ordered by name. So if you do not mess with orders, the prefix clearly separates official channels from others

How about a help channel as well? Are we going with tooling and general for people to get help?

@aayushmau5 yeah, my idea was to not have a separate help/support but allow this in general/specification/tooling so topic description say It is ok to ask for support here.

my motivation was to not segregate people but engage in the same channels where we discuss other things.

[derberg]

If anyone has time for review, I've just opened a PR with slack etiquette asyncapi/.github#53

[derberg]

all done:

• channels created/renamed/removed
• bot welcome message reconfigured
• all new members will now always join the new official channels
• existing members notified in general channel about the reorg and new channels
• history preserving bot moved to a separate issue Create a slack bot that stores selected threads in Discussions .github#54 as priority is not that high anymore due to Slack enabling standard subscription for us

closing 🎉