# 💬 Slack

We use Slack (opens new window) for team-wide communication, announcements, and project-specific coordination. The workspace can be found at ubclaunchpad.slack.com (opens new window). You should receive an invite in your email to join the workspace - if you haven't, please reach out to your lead or one of the presidents for help!

# Slack Best Practices

  • Install Slack on your devices and enable notifications so you don't miss discussions and annoucements!
  • Use threads (opens new window) for conversations, especially in large channels! This helps prevent spam and makes it easier to catch up on missed conversations.
  • Name channels using our naming scheme to make it easier for others to find your channels.
  • If it is important, do not leave it in Slack! We are on the free tier of Slack, so messages eventually expire. Anything important or permanent should be in a GitHub issue or repository!
  • If a discussion pertains to club-wide decisions, please do not use direct messages - whenever possible, have the discussion in a relevant shared channel so that there is more visibility into what's going on, and to avoid excluding team members who might be able to contribute useful input. Good places to start discussions are relevant #tm- or #ask- channels.
    • If it doesn't feel like a discussion pertains to any specific channel, feel free to create a new channel (following our naming scheme) and link to it from other channels so that people can drop in on discussions they want to contribute to!

# Finding People

You can also ask around in #ot-random (opens new window), #ot-meetups (opens new window), or #ask-leads (opens new window) to meet everyone!

In Slack, you can also identify Launch Pad leads by finding people who have the Launch Pad logo next to their name (set as their Slack status), which you can hover over to learn more:

lead status

Keep our best practices in mind when reaching out to people - for example, use threads in channels and don't use direct messages for discussions pertaining to club-wide decisions.

# Naming Slack Channels

We use a channel naming scheme to make channels easier to find (based on ideas#13 (opens new window)) that leverages the following prefixes:

  • #ot- for "off-topic" discussions, such as those related to a particular hobby
  • #cop- for "community of practice" discussions, such as those related to a skill or technology
  • #ask- for question channels, mostly for questions aimed at teams to Launch Pad members that aren't a part of a team a space to ask questions
  • #tm- for teams
  • #nt- for notifications (some Slack bots and integrations can send updates to specific channels)

All channels should be named using this scheme.

Some channels are featured in this document, but you can easily find a full list of each category of channel by searching for a prefix!

# Community of Practice (#cop-) Channels

# Off-Topic (#ot-) Channels

# Ask Leadership and Teams (#ask-) Channels

# Bots & Apps

# Rocket updated

Rocket 2 (opens new window) is our very own Slack bot, used for managing our roster across Slack and GitHub. Members use it mainly to automatically add themselves to the GitHub organization, Google Drive, and more.

You can get started by writing /rocket user add in our Slack workspace! For more details on getting set up with Rocket, please refer to our onboarding guide.

Leads at Launch Pad also use Rocket to create and manage teams - learn more in the leads onboarding guide.

For more commands, type /rocket help. If you are interested in how it works, check out the documentation page (opens new window).

# GitHub

You can configure your GitHub notifications to be delivered to your Slack account via the GitHub Slack app - read this guide to learn how!