An ongoing communication channel

[codehippie1]

Hi Outreach committee,

Suggestions

1. Stream line onboarding process for members/volunteers. As of now, there are no steps outlined in github space to be a member/volunteer
2. A better communication channel is needed for conversations with all parties involved. Creating github issue for communications is not a viable option. This helps asking for status of a specific item/issue or even related discussions without bloating up the github issue comment history.

We can do either of these

• A discord/slack channel with all members and volunteers, as this allows everyone to join with a private email account. Slack work across the board, regardless of member or volunteer.
• A microsoft teams channel with members and volunteers(Heard about issues in adding private emails accounts to team channels during last meet though)
• github team discussion (Volunteers needs to be part of github for this, Problem- Volunteers are not necessarily be engineers who need to be on github)

[codehippie1]

Currently the discord channels are open to everyone. This produces chats which get buried quickly in the feed.

Proposal: 

1. Add an #inroduction channel and direct new members here instead of #general channel
2. Add a welcome message stating purpose of each channel and direct users to specific channels to chat based on their interests.
3. Add a channel where committee members can effectively communicate with each other. Make this available to only committee members. This helps with things like sharing a document, powerpoint etc. This also ensures the messages don't get buried under everyone's chats.
4. Add introduction to each channel and set up roles within the channel. This helps everyone to direct questions to the members with specific roles if necessary.

[codehippie1]

A discord channel is available for communication now