VRMS Onboarding

[JackHaeg]

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 (@Jack_Haeger) 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 the Team Roster document, VRMS Google Drive, and will add you to the calendar invites for our Monday 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 (do not worry about 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:
• Make a Pull Request with any improvements to the Contributing Document.
• 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.

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.

Resources/Instructions

• Contributing Document
• Our VRMS Active Project Board can be found here

[ntrehan]

As pointed out last week in the call, me and @nora-zajzon weren't able to access the file with environment variables. So that was the only improvement I was able to find in this otherwise super clear Contribution Document
However, I see that @jbubar has already created a separate issue for that (#1687). I have assigned that to myself and would be making the required changes

[JackHaeg]

Thanks for your work on this and #1687 @ntrehan! Closing this issue as completed 👍