Re-structuring the Community Slack channels plus Feature suggestions

[anitaokoh]

Hey @thgnw ,

Below is a proposed slack channel structure as well as some features we can plan to add

Channel Structure

• Announcements: Announcements of new versions, webinar , blog, feature etc . Only read mode for the community
• Intro: Introductions of community members
• Suggestions: This revolves around suggestions on features, bugfixs etc
• Random: This will include interesting reads or gifs or memes ( random as the name implies) or shameless plugs
• Support: This includes supports from both side i.e from the user side: code support or from our side: functionality clarifications

IMO the general channel , although common, is too vague. So we can rename make the general channel as the announcement channel with only read mode or the Support channel

Features to consider

• Welcome Bot for new comers
• Our doc bot integrated to the slack

**Note
For the welcome bot, we would need to be on a paid slack subscription to use it **

Welcome Bot Template

Hey <name>
Welcome to the SuperDuperDB slack community where all the fun happened

We have 5 channels specially tailored for your use:
- Announcement : Blah Blah
- Intro: Blah Blah
- Suggestions: Blah Blah
- Support: Blah Blah
- Random: Blah Blah


Excited?

Introduce yourself to the rest of the community in the `intro` channel. Tell us
-  About yourself , 
- How to connect with you 
- And what is one PainPoint about  the ML process for you

Dig deeper on SuperDuper functionality by exploring our <documentation> and <our comprehensive Readme> . Give our <doc chat> bot a spin and let us know what you think.

Feeling inspired, already?
 
Then checkout our <contributor's guide> on how to contribute to the Superduperdb and then dive straight into your <first issue> . 

We will be there with you all the step of the way

What do you think about the channels, the features mentioned and the template?

cc @guerra2fernando @blythed

[guerra2fernando]

I checked other slack channels of DBs and similar companies and they follow something very close to this, which is good as devs are familiar with this structure. For me it looks good and we can procede, wyt @thgnw @blythed ?

[blythed]

Agreed