Try   HackMD

Discord Guide

This guide provides details on how to setup and use WATonomous Discord.

Getting onto the WATO Discord Server

If you do not have a Discord account, first create one by going to https://discordapp.com/register. We suggest that you make your
username your preferred full name but any username works.

Next, log into Discord (via their web client, or downloadable desktop app), and then click on the following invite link to WATO's DiscordServer: https://discord.gg/jVx2dKX

If following the above invite link does not connect you to our server, login to Discord and click the + sign (at the top left of your Discord screen, below the direct messages square) and select "Join a Server" and paste in the invite link above. You should then see the WATO logo appear above the + symbol.

If you set your Discord username to the preferred name you gave us, then you are done! If not, then you must set your WATO Discord Server nickname to your preferred name. Instructions on how to set a server-specific
nickname are here: https://support.discordapp.com/hc/en-us/articles/219070107-Server-Nicknames

If neither your Discord Username, nor your WATO Discord Server nickname are equal to your preferred name, our automation scripts will not be able to assign your Discord tags, and you will not be able to use WATO's
Discord Server.

This section explains how to configure Discord for how you will be using
it on WATonomous. Simply follow the steps!

Downloading the apps

  1. Download the desktop Discord app: https://discordapp.com/download
  2. Download the mobile Discord app
    1. Android: https://play.google.com/store/apps/details?id=com.discord&hl=en_US
    2. iPhone: https://apps.apple.com/us/app/discord/id985746746

Configuring notifications

Since Discord is how everyone in WATonomous communicates, it is very important that you get the notifications you care about, and not the hundreds of notifications that you do not care about! You do this by configuring your notification settings on your desktop and mobile apps.

First:

  1. Learn how to configure notification settings on the desktop
    app: https://support.discordapp.com/hc/en-us/articles/215253258-Notifications-Settings-101
  2. Learn how to configure notification settings on the mobile
    app: https://support.discordapp.com/hc/en-us/articles/218892547--Mobile-Notifications-Settings-101

Now that you understand how to configure your notification settings, here are the required and recommended configurations for WATonomous:

  • You must keep** @mention notifications** turned on. It is essential that you get notified when someone is speaking to you directly.
  • You must keep the notifications for the your **squad's channel, your group's channel, and your division's channel **turned on.
    • For example, if I am a Core Member in the Path Planning Group, working on Trajectory Planning, I would keep notifications turned on for #trajectory-planning, #path-planning-general, and #software-general channels.
    • Another example, if I am the Manager of the External Sponsorship Group, I would keep notifications on for the#external-sponsorship, #business-general, and #business-group-leads channels.
  • It is also recommended that you keep notifications turned on for the channels in the COMMON category, since these are channels that concern everyone on the team. #server-use will notify you if there is a problem with WATonomous' Servers, #team-progress will notify you when we accomplish some cool shit, #memes will notify you about the dankest WATO has to offer, etc...
  • In general, use your common sense when muting a channel. If you find yourself caring deeply about what is being talked about in a certain channel (maybe you're an key stakeholder of the #sensor-placement-project), turn on notifications for that channel!

Customizing your profile

Some notes about how to make your profile feel like your own

  • Most people choose to upload a picture of themselves as their Discord avatar. This helps other team members know who they are talking to!

WATonomous Discord FAQs

What to use Discord for

  1. You are free to read and participate in whatever conversations on whatever channels you like! If you have questions about something, or want to contribute to any conversation happening on Discord, there is no need to be shy!
  2. Technical discussions with other team members
  3. Giving easy access to documents, using the pinning feature (see below)
  4. Organizing meetings (with help from when2meet.com)
  5. Random discussions, but only in #random

What not to use Discord for

  1. Do not use private messages for anything that is appropriate to be talked about in WATO public channels. We strive for transparency and to help others who have the same questions.
  2. Technical documentation. If you are talking about anything on Discord that you think is useful technical information, make a HackMD note for it

Tips and Tricks

Check it frequently! I predict that you will learn the most this term if you read all of the Discord messages sent in every channel

You can set your status (bottom left profile picture) to Do Not Disturb to mute all notifications instead of closing Discord, but do remember to turn it off

You can pin messages (like I will pin this onboarding message) for future ease of access. See the kebab menu (3 dots) that pop up when you hover over a message

You can use @<YourGroup> or @<Somebody> in messages to tag everyone on your group or to tag a specific person. This will guarantee they are notified about the message

You can use #<some-channel> in messages to link to another channel. Use this to link another channel if people are using the wrong one

Post in the correct channel. The rule to follow is to post in the most general channel that makes sense. Example violations: Posting onboarding questions in your squad's channel (go more general, in #onboarding), talking about your squad's implementation details in #software-general (too general, go to #your-squad).

All #*-general (e.g. software-general, perception-general) have the same channel description with 4 very useful bits of information:

  • Group / Divisional Weekly Meeting times
  • A link to the Group's / Division's Workboard
  • A link to the Group's / Division's F19 OKR Document
  • A link to the Group's / Division's F19 Gantt Chart

Becoming a Discord Wizard

Knowing how to navigate and communicate with ease using Discord is one of the most important things to learn. Luckily, there are many Discord support pages that have been written to help you along your way. My personal tip is to use the quick switch function to find your way around quickly: https://support.discordapp.com/hc/en-us/articles/115000070311-Quick-Switcher-T-A-Y-N-E-

You can find many other useful topics to help you on your journey to becoming a Discord Wizard here:Discord Starter Guide

Last changed by 
 
WATonomous
0
263

Read more

Creating Purchase Requests

To create purchase requests, we use this link: https://jira.watonomous.ca/secure/CreateIssue.jspaNote that you MUST use this link because clicking the &quot;Create&quot; button on the top navbar will not redirect you to the correct create issue page.

Jul 21, 2024
Teleport Server Access

Member form First, confirm that you have filled out the Member Form with your Github information. You have accepted the WATonomous Github Org invite that gets sent to you. You can confirm if you have completed this step by finding yourself in the member list. If you don&apos;t see yourself in the member list, visit here to accept your invitation. (WATonomous team members only) You have merged the merged request that gets created for you (WATonomous team members only) The CI provision_teleport job that gets spawned by the merge action succeeded. You have gone into the job (example) and confirmed that your user-&lt;username&gt; role has been created. Setup tsh Follow the guide for installing and using tsh, Teleport&apos;s CLI.

Mar 14, 2022
CAN Launch Procedure

Updated on 2022-02-03 by Stephen and Kushant This procedure is confirmed to work for the Kvaser USB-CAN interface. Make sure the connections on CAN controller interface look like this Vehicle-to-Computer connections by the driver seat Backside of the PCB

Feb 17, 2022
WATcloud Incident Log

HOWTO As soon as an issue arises, create a page from the on-call incident template Don&apos;t be afraid to post scrap notes. Prefer to overpost rather than underpost. Record: What service was down? What was the problem? Why was the service down? How was this problem discovered? How was it solved?

Feb 17, 2022
Read more from WATonomous
Published on HackMD