Time: 8pm - 9PM Location: Online Attendees: John, Tony, Adam, May, Kot, Nate

Agenda

  1. Quick Stand Up
    1. Home Page branch - May
    2. Forms Component - Adam
    3. Github Actions - John
    4. Vercel deployment preview
  2. SESA Project
    1. Friday 2PM Meeting - Adam Probably, Kot Probably, Nate, May, John, Tony (sesa side)
    2. Pre Client Questionnaire Preview
    3. SESA Allocations
  3. Next Sprint Work Allocations
    1. Velocity ? Do we want it as an allocation, or work together async?
    2. SESA Figma
    3. More components for our website?

Minutes

  1. Stand-up

    1. Home Page branch
      1. Add more stuff to page
      2. make About Us page
    2. localhost name change ?
    3. Adam was deathly ill and could not do Forms Component 🙏
    4. John GitHub Actions + Prettier
      1. Will activate on PR?
      2. Prettier updates when you ctrl-s on VSCode
      3. Testing - Jest for Unit tests? (VTest is better?)
      4. To add unit tests for components
      5. Adding e2e testing in the future?
      6. Future: terraform, custom deployment
    5. Vercel deployment
      1. keep eyes and ears out for getting a domain, maybe once we have 1-3 projects under our belt

  2. SESA

    1. We are working on SESA project confirmed!
    2. Friday 2pm meeting with SESA
      1. everyone try to attend since its the first meeting
      2. Designate someone to take minutes
    3. Client questionnaire can be found in Google Drive
      1. They fill it out before the meeting (will be sent out today)
      2. We make a Figma design for them by Friday ideally?
      3. May, Adam, Nate — SESA
      4. John, Kot — localhost
      5. John to make a repository to hold our components
      6. Want some way to package/avoid copy pasting components
      7. Possible solutions:
        1. Nested git repository with components (parent git repo has a pointer to the components repo)
        2. package imports

  3. Next sprint work allocations

    1. We all work together for Velocity? Nate might opt out. Kot hates writing.’ After Friday Meeting
    2. SESA Figma — no need since very similar to current SESA website
    3. New work
      1. Nate + Adam - Form refactoring ? + backend for form
      2. May - About us page
      3. John - Hamburger menu
      4. Kot - 3D animation
      5. Tony - SESA stuff