🎉 Onboarding for Leads

Welcome to UBC Launch Pad, and congratulations (and thank you!) for joining us as a lead!

Checklist

Slack Channels

Everyone should join a private channel named #tm-leads-YYYY (for example, #tm-leads-2020). If this channel doesn't exist yet, coordinate to get it created. This will be the primary means through which Launch Pad leadership works together. In addition, make sure you join:

• #ask-leads: this is where members are expected to direct questions at leadership.
• #ask-rocket: our Slack bot Rocket is how teams are set up and managed - make sure you familiarize yourself with the app and ask this channel if you have questions or something is broken.
• #ask-design: questions for design
• #ask-strategy: questions for strategy

As a lead, you should also lead in Slack participation by example - please make sure you join any channels you find interesting and participate in them! See our Slack guide for more details.

GitHub Teams

Make sure you are a part of the following teams on GitHub:

• @ubclaunchpad/leads, and check that you can access the Leads repository - this repository primarily contains interview resources and tracking issues
• @ubclaunchpad/strategy, and check that you can access the Strategy repository - this repository contains sponsorship resources and event/sponsorship tracking issues
• @ubclaunchpad/design, and check that you can access the Design repository - this repository contains (some) design assets, resources, and tracking issues

Additionally, the presidents should also be a part of @ubclaunchpad/exec and familiarize themselves with the Exec repository, where we keep track of accounts and credentials.

TIP

Make sure that you are watching all relevant repositories so that you don't miss any updates! To learn more about setting up your GitHub notifications, check our GitHub guide.

Google Drive

Make sure all leads are given "editor" access to the shared Launch Pad folder, which is owned by the team@ubclaunchpad.com account (more details are in the Exec repository).

Within the shared Launch Pad folder, try to maintain the following structure:

• Projects - folders for project teams
  • Note that everyone should be granted access to this folder (part of Onboarding for Everyone)
  • Each tech lead should create a folder for their project inside a year subfolder ("Projects YYYY") of this folder
  • Inside each project folder, each lead should create a document for meeting notes. All their project meetings should go in this document. See Sprint Planning for more details.
• Strategy - see Onboarding for Strategy
• Design - see Onboarding for Design
• Leads - that's for us!
  • Leads should create a document for meeting notes titled "Leads: Meeting Notes YYYY". All leads meetings should go in this document.
• Exec - for the presidents
  • Presidents should create a document for meeting notes titled "Exec: Meeting Notes YYYY". All exec meetings should go in this document.

Workflows

TIP

We use GitHub and Slack for pretty much everything - make sure you are intimately familiar with both, regardless of your role, by reading our handcrafted guides:

• GitHub guide
• Slack guide

Projects

The handbook's Project Management pages are a must-read - for all leads:

• Scope - how to develop and scope ideas for Launch Pad projects, as well as the timeline for development
• Sprints - how to plan and collaborate with your team to deliver on your project

Additionally, technical leads will want to take a look at the Repository Management page to help them set up tooling for their projects.

Meetings

Leads meetings between all leads (technical and non-technical) should happen on a regular basis.

TODO: flesh out what we want meetings to be like