Skip to content
This repository was archived by the owner on May 15, 2023. It is now read-only.

Discord

Pi edited this page May 4, 2023 · 10 revisions

Warm Welcome to Our Communication Channels! ๐ŸŽ‰

We're thrilled to have you here, and we're eager to share our communication best practices with you! We use Discord for our lively chats and GitHub as our trusty project management tool.

Here's a friendly guideline to help you navigate our communication channels effectively:

If it's relevant for more than 24-48 hours, skip Discord and head straight to GitHub.

Our goal is to foster a more transparent, equitable, efficient, and open style of communication. That's why we love asynchronous conversations (like those on GitHub) over synchronous ones (like Discord or calls). Here's why:

๐Ÿค” Asynchronous chats give everyone time to process and contribute thoughtfully to the topic or issue at hand.

โณ They can easily span a longer time period, unlike calls, which have time limitations.

๐ŸŒ Asynchronous communication is inclusive โ€“ anyone can join at any time, even if you didn't know who the relevant parties were beforehand.

๐Ÿ“ž You can effortlessly transition from asynchronous chats to calls if needed, but the reverse is more challenging.

๐Ÿ” Conversations are easily searchable and stored for future reference, unlike calls.

๐Ÿ“– Catching up on an asynchronous conversation is more efficient and easier than watching a video or reading a transcript.

๐Ÿ’†โ€โ™€๏ธ Discord can sometimes create anxiety due to the sheer volume of messages. Asynchronous chats on GitHub help separate the "good to know" from the "needed right now."

๐Ÿ“ Remember, for items that are useful for more than 1 month, we encourage you to use documentation.

We hope this friendly guide helps you embrace our communication culture, and we can't wait to see you flourish in our community! ๐ŸŒŸ

Clone this wiki locally