VRMS Onboarding: Andrew Shin

[Tharunya07]

Overview

Each new member should complete the following steps to onboard onto the VRMS team.

Action Items

All Members

• Join our All Team Monday Meeting at 7pm PST (Zoom Link)
• Send a Slack message to the current Product Manager (@tharunya Pathipati) with your name, email address (gmail if possible), and GitHub handle.
  • During the All Team call, the Product/Project Manager will then provide you with access to:
    • Team Roster document
    • VRMS Google Drive
    • Calendar invites for weekly meetings
  • Dev Lead will also add you to our GitHub repository team (i.e., both the VRMS and VRMS-write teams)
• Fill out your information on the team roster.
  • Click on the "Roster" tab at the bottom of the spreadsheet, and fill out empty cells highlighted in RED. Phone numbers are optional. Do not worry about filling out the grayed-out section).
• Review the VRMS Wiki Highlights

Developers Only:

• Carefully read the Contributing Document, taking notes where it could be improved.
• Set up your environment variables following these steps:
• Optional If you see anything that could use improvement on the Contributing Document (e.g., spelling/grammar issues, additional information required, updated links, etc.) please submit a Pull Request.
• Create an account on VRMS Dev, send the email address linked to your account to the Dev Lead (Trillium) or the lead PM (Jack) on Slack and request that they provide your account with Admin access. This will allow you to QA issues.

UI/UX Only

• Send current design lead (Julia Gab) a Slack message access to relevant Figma files
• Create an account on VRMS Dev, send the email address linked to your account to the Dev Lead (Josh or Trillium) and request they provide your account with Admin access. This will allow you to QA issues.

PM Only

• Create an account on VRMS Dev, AND on VRMS Prod. Then send the email address linked to your accounts to the Dev Lead (Josh or Trillium) and request that they provide your account with Admin access on both DEV and PROD versions of VRMS. This will allow you to QA bugs and resolve admin issues in the future.
• Add to 1password (zoom and VRMS vaults)
• Carefully read the Contributing Document

Resources/Instructions

• Contributing Document
• VRMS Active Project Board
• VRMS GitHub
• VRMS Google Drive
• VRMS Wiki

[Tharunya07]

-- @trillium need to add the member to VRMS team and assign this ticket. Thanks!