VRMS: All Team Meeting Agenda and Meeting Minutes

[drubgrubby]

Overview

This issue tracks the agenda for the VRMS Team's Monday meeting

Issue Template

[Date ] Meeting Agenda

Pre-work to prep for meeting

• Update issues

Recurring items:

• Review project board
• Assign issues

Things we plan to discuss

What we actually discussed

Additional notes

Upcoming Milestones

Previous Meetings (link to each comment with the date)

February 14, 2022
February 21, 2022
March 7, 2022

[drubgrubby]

February 14, 2022 Meeting Agenda

Pre-work to prep for meeting

• Update issues

Who was there?

David, Walter, Shaun, Glen, Evan and Bonnie for a second

Recurring items:

• Review project board
• Assign issues

Things we plan to discuss

• Research stats for the Design System #1048
• Discuss node-sass PRs
• adding NODE_ENV=test to your backend .env file
• How to comment when creating a new PR

What we actually discussed

• Bonnie explained what she wants on Research stats for the Design System #1048
• Comment out slack call so we don't get the error anymore (create ticket)
  -[ ] We need to create a ticket to make sure that the production db has the user.email field as a unique value

Additional notes

Upcoming Milestones

Previous Meetings (link to each comment with the date)

[drubgrubby]

February 21, 2022 Meeting Agenda

Pre-work to prep for meeting

• Update issues

Who was there?

Shaun, Evan, David

Recurring items:

• Review project board
• Assign issues

Things we plan to discuss

• Make user.email field unique in production database #1065
• Discuss the use of Prettier / eslint for code consistancy

What we actually discussed

• We need to discuss with Bonnie how to think about merging users so we can remove duplicate email addresses from the database.
• We're going to suffer through the ugly prettier PRs for a minute for the greater glory of having our code look prettier.
• We should add an eslint pipeline step that fails on eslint errors
• Also we should update the readme to mention installing eslint and prettier ide plugins (Create a ticket for that).
• Create a ticket for having db calls refer to new endpoints

Additional notes

Upcoming Milestones

[drubgrubby]

Monday, February 28, 2022 Meeting Agenda

Pre-work to prep for meeting

• Update issues

Who was there?

Recurring items:

• Review project board
• Assign issues

Things we plan to discuss

-[ ] What is there still to do to get v3 done?

What we actually discussed

[drubgrubby]

Monday, March 7, 2022 Meeting Agenda

Pre-work to prep for meeting

• Update issues

Who was there?

Jeanette, Josh, Shaun, Evan, Haira

Recurring items:

• Review project board
• Assign issues

Things we plan to discuss

What we actually discussed

• We discussed with Jeanette the data that she is looking for and how to get it.
• We discussed the issue of making the user.email field in the production database unique. There are two prevailing theories: 1) Make a copy of the users database so we have all of the information somewhere, and then make the change to the new main users db, 2) write a script that will append something to the duplicate users email, ex.
• We talked about the auth PR from v.4 that Shaun is going to take a look at.

Additional notes

Upcoming Milestones

[jbubar]

VRMS Tech meeting

• went over Evan's PR and decided that he could do it again with out bootstrap.
• scheduled a meeting with josh and Walter to work on walter's issue
• created a new issue for the annoying magic link Stay logged in for longer #1080
  • evan's idea

[jbubar]

VRMS Team Meeting

Questions and requests for Bonnie:

• Can we give @FoxShaunR access to the AWS
  • Ops is not responding (has been over a month)
• What do we need to deliver to get v0.3 out the door?
  • current list of things to do
    • Clean up the duplicate email addresses in the db Make user.email field unique in production database #1065
      • Back up database, clean up prod database and keep newest one, update newer registration missing data with data from older registration (including login history!!), delete older registration
    • Restyle the admin portal to look like the figma Style Project Management Component #1049 (v.3.1)
    • Create github issue when someone wants to edit a restricted field in the projects info Create a Github Issue when a Non-Admin User Wants to Change a Restricted Project Field #796
    • ... (unfinished)
• Can someone be promoted to Admin to make github secrets so that we can make the deployment github actions work
• Can we get more thorough requirements for this issue?(Slackbot messaging Proposal 100Automations/futureautomations#8)
  • @tmshkr is interested in taking this on