Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

VRMS: ALL: Monday Meeting Agenda 📝 #1280

Open
jbubar opened this issue Jan 31, 2023 · 55 comments
Open

VRMS: ALL: Monday Meeting Agenda 📝 #1280

jbubar opened this issue Jan 31, 2023 · 55 comments
Assignees
@JackHaeg
Labels
feature: Agenda role: Product size: 0.5pt Can be done in 2-3 hours or less
Projects
VRMS - Active Project Board
Milestone
03.01 Project Man...

Comments

@jbubar
Copy link
Member

jbubar commented Jan 31, 2023 •
edited by JackHaeg

Overview

Bonnie came to our meeting today and requested that we do our agendas on a single issue, so I created this one!

Here is the old one:
#1051

and our old system on the wiki that needs to be updates:
https://github.com/hackforla/VRMS/wiki/Team-Meetings

## [DATE] Meeting Agenda and Notes

### Prework to prep for meeting
- [ ] Review the QA
- [ ] Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

### Role Call (who is here - add team names)
- [ ] Jack
- [ ] Trillium
- [ ] Julia
- [ ] Josh
- [ ] Bonnie
- [ ] Rohan
- [ ] Brad
- [ ] Nayan
- [ ] Evan
- [ ] Daniel
- [ ] Jo
- [ ] Chandler
- [ ] Angela
- [ ] Katiuska

### FYIs (nothing needs to be done, just keeping each other informed)

### Recurring items: 

### New Items 
add issue numbers to be discussed and any notes that will be helpful

**Issue assignment cleanup:** 
- [ ] [Jack](https://github.com/hackforla/VRMS/issues/assigned/JackHaeg)
- [ ] [Trillium](https://github.com/hackforla/VRMS/issues/assigned/Spiteless)
- [ ] [Julia](https://github.com/hackforla/VRMS/issues/assigned/juliagab56)
- [ ] [Josh](https://github.com/hackforla/VRMS/issues/assigned/jbubar)
- [ ] [Rohan](https://github.com/hackforla/VRMS/issues/assigned/vaidyarohan)
- [ ] [Brad](https://github.com/hackforla/VRMS/issues/assigned/bkmorgan3)
- [ ] [Nayan](https://github.com/hackforla/VRMS/issues/assigned/freaky4wrld)
- [ ] [Evan](https://github.com/hackforla/VRMS/issues/assigned/evanyang1)
- [ ] [Daniel](https://github.com/hackforla/VRMS/issues/assigned/danieldkim42)
- [ ] [Jo](https://github.com/hackforla/VRMS/issues/assigned/josiehandeveloper)
- [ ] [Chandler](https://github.com/hackforla/VRMS/issues/assigned/lcchrty)
- [ ] [Angela](https://github.com/hackforla/VRMS/issues/assigned/awlfccamp)
- [ ] [Katiuska](https://github.com/hackforla/VRMS/issues/assigned/chukalicious)

### Notes from meeting

### Tasks

### Items for next week's agenda

Old Team Meetings:

Previous Team Meeting Agendas (from 2022) that were previously stored on the VRMS Wiki have been preserved in this issue.
@github-actions github-actions bot added this to New Issue Approval in VRMS - Active Project Board Jan 31, 2023
@jbubar
Copy link
Member Author

jbubar commented Jan 31, 2023 •
edited

Jan 30th:

Bonnie jumped on and brought up the following:

Hi PMs - ill be coming to Monday's VRMS meeting. I don't see an open agenda issue to add this to, so here are my items
Talk about why you migrated agenda locations and how its working for your team
in issues #1051
to wiki https://github.com/hackforla/VRMS/wiki/Team-Meetings
Org recently adding feature: agenda label to all project repos that don't have it and how VRMS can use this information
I updated this issue #1274
This page needs updating: https://www.hackforla.org/projects/vrms it looks like you opened a change request but it needs refining hackforla/website#3694

@heyitsalexander
Copy link
Member

heyitsalexander commented Jan 31, 2023 •
edited by ExperimentsInHonesty

Template

## [DATE] Meeting Agenda and Notes

### Prework to prep for meeting
- [ ] Review the QA
   - [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
     - [ ] Check to see how new team members are doing 
       - [ ] [UX writing](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+writing%22#column-15490305)
     - [ ] Can we improve the prework template based on something we see as a pattern?  

### Role Call (who is here)

### FYIs (nothing needs to be done, just keeping each other informed)

### Recurring items: 
 - [ ] review any issues that are in the new issue approval column for 
    - [ ] [UX Writing](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+writing%22#column-15235217)
    - [ ] [Product] - that are related to writing
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each PM
       - [ ] [Bonnie](https://github.com/hackforla/website/issues/assigned/ExperimentsInHonesty)
       - [ ] [Zoe](https://github.com/hackforla/website/issues?q=assignee%3Azzhoje+is%3Aopen)

### New Items 
add issue numbers to be discussed and any notes that will be helpful


### Notes from meeting

### Tasks

### Items for next week's agenda

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 4, 2023 •
edited by heyitsalexander

2023-02-06 Meeting Agenda and Notes

Prework to prep for meeting

  • Judy's prototype work

Role Call (who is here)

FYIs (nothing needs to be done, just keeping each other informed)

  • Onboarding Event

Recurring items:

Notes from meeting

Tasks

--0)    Sign in to VRMS by following the prompts to arrive at the “Project Management” screen.
 
1)    Add a new project name “Testy Test” and its project details. Also, add some recurring team meeting times for this project. After you finish, return to the “Project Management” screen and make sure it is added to the database and stop there.
 
2)    Oops! You just realize that Testy Test’s Team Meeting 1 starts at 7PM vs. 8PM. Find project Testy Test and change the recurring Team Meeting 1 time accordingly. After you finish, return to the “Project Management” screen and stop there.
 
3)    Find David Rubinstein with email david@grubbylogic.com and add him to project Testy Test. After you finish, return to the “User Management” screen and stop there.
 
4)    David Rubinstein just emailed you that he cannot be on project Testy Test. So, remove him from this project. After you finish, return to the “User Management” screen and stop there.

Items for next week's agenda

@AmandaGlover-PM
Copy link
Member

2023-02-06 Meeting Agenda and Notes

Prework to prep for meeting

  • Judy's prototype work

Role Call (who is here)

FYIs (nothing needs to be done, just keeping each other informed)

  • Onboarding Event

Recurring items:

Notes from meeting

  • Amanda & Julia getting added to VRMS
  • Matt from the web team is interested in joining the VRMS team (a 7 out of 10)
  • All PMs are updated in VRMS so we can add PMs and have them adjust meeting times and have project level access. Matt confirmed meeting times are being reflected on VRMS and the website so we can now teach PMs how to use the system and test their experience - YAY!!!
  • Alex & Amanda will create a step-by-step guide on how to edit meeting times on VRMS for the lunch & learn and also to document how to make the edits so PMs can follow the steps on their own
  • Food Oasis Meeting updates from the chat in the meeting:
    ADD Food Oasis, Developer Meeting, Monday 6.30pm, 30 mins
    ADD Food Oasis, PM Meeting, Tuesday 5pm, 1 hour
    ADD Food Oasis, UXR Meeting, Tuesday 6:30 pm, 1 hour
    DELETE Thu 6:00 pm - 7:00 pm Team Meeting
    ADD Food Oasis, Leads and PM Meeting, Thursday 6pm, 1 hour
    ADD Food Oasis, All Team Meeting, First Thursday of the month 6pm, 1 hour
    ADD Food Oasis, Design Meeting, Thursday 7pm, 1 hour
  • No new developers from the last onboarding event / Julia to talk to some new UX volunteers who haven't been assigned a project yet; Developers look for an updated Repo and if we update that to explain the defined priorities that could help
  • Judy live tested her clickable prototype with Matt
    First Task: Sign in to VRMS by following the prompts to arrive at the “Project Management” screen
    Second Task: Add a new project name “Testy Test” and its project details. Also, add some recurring team meeting times for this project. After you finish, return to the “Project Management” screen and make sure it is added to the database and stop there.
    Third Task: Oops! You just realize that Testy Test’s Team Meeting 1 starts at 7PM vs. 8PM. Find project Testy Test and change the recurring Team Meeting 1 time accordingly. After you finish, return to the “Project Management” screen and stop there.
    Fourth Task: Find David Rubinstein with email david@grubbylogic.com and add him to project Testy Test. After you finish, return to the “User Management” screen and stop there.
    Last Task: David Rubinstein just emailed you that he cannot be on project Testy Test. So, remove him from this project. After you finish, return to the “User Management” screen and stop there.
    Matt's Feedback: Personal preference to have less total clicking on the page with the identifiers once he saves something, he would rather have confirmation that it was saved without having to click out of that screen; forms look good, inputs are solid. Haven't seen a logout that is in parenthesis versus a button. When adding someone to VRMS he would prefer it to say submit versus save.

Tasks

  • Lunch & Learn (dinner) guide / Alex creating the guide, Judy & Julia will pretty it up
  • Need to delete Food Oasis meetings, then project, then re-add the Food Oasis project; need to tell Food Oasis that there is an issue with their data in the database so we can't update their data right away but we are working on it
  • Figure out testing for live prototypes and then schedule time with Bonnie for review - planning for usability testing with Bonnie next Monday. Judy's new schedule makes evenings difficult. We will get a script and either Julia, Alex or Amanda can run the user-test per the script and we will record this. Here is the post prototype survey to give Bonnie: https://docs.google.com/forms/d/e/1FAIpQLScuFPl0bbNuPGOWLsImRjJ9TvMqsHmwCCOwSpy8R7TFL3AHRA/viewform

Items for next week's agenda

@heyitsalexander
Copy link
Member

heyitsalexander commented Feb 9, 2023 •
edited

2023-02-13 Meeting Agenda and Notes

Prework to prep for meeting

  • Judy's prototype reviewed and usability testing script

Role Call (who is here)

FYIs (nothing needs to be done, just keeping each other informed)

  • Lunch n' Learn Deck ready
  • New dev joining VRMS

Recurring items:

  • PM/Design/Dev updates if any
  • Judy asks Josh about user count / usage for VRMS and if there’s a way for us to gather this data now and track the improvements over time once the updated changes are live.
  • Food Oasis update? We haven't been able to figure out what's happening, but Josh was able to edit the meeting times in the database.

Resources for meeting

Notes from meeting

Tasks

  • Ask for permission to record

  • Usability testing with Bonnie part 2

  • Post test survey

  • UX researcher responsbilities?

Items for next week's agenda

  • Josh update on ways to track VRMS usage
  • Josh needs time with devs in breakout room
  • Update from Stephanie regarding Lunch n' Learn Scheduling
  • Update from Julia regarding UX researcher and issues

Feb. 27th Usability test with Bonnie
March 6th Lunch n' Learn

@ExperimentsInHonesty
Copy link
Member

@heyitsalexander I could not find another issue for the slide deck creation. So I am adding my notes from the review here:

Lunch n' Learn deck VRMS - How to Add/Edit Meeting Times slides

create an account

  • logo warped
  • Prerequisites should be moved to previous slide
    • creating an account
      • having that account upgraded by the org admin (currently Bonnie) to project editor status

Log In

  • I added text to this slide

Three Important Notes/Quirks:

  • What do you mean when you say "(Remember: Event Name will not show up on website)"

Edit Meeting Time slide

  • I added text to the second bullet

@ExperimentsInHonesty
Copy link
Member

@heyitsalexander Are you having a meeting on the 27th. If yes, I can come for the usability test then. If not I can come on 03-06

@heyitsalexander
Copy link
Member

@ExperimentsInHonesty Yes, usability testing with you on the 27th! Lunch n Learn on 3/6

@ExperimentsInHonesty
Copy link
Member

@heyitsalexander I dont see that you made the logo change yet. See #1280 (comment). I will want to review/revise the Lunch n' Learn deck VRMS - How to Add/Edit Meeting Times slides with your team on the 27th, so it can be ready for the 6th.

@heyitsalexander
Copy link
Member

heyitsalexander commented Feb 25, 2023 via email

@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Feb 28, 2023 •
edited

2023-02-27 Meeting Agenda and Notes

Role Call (who is here) - Julia, Josh, Trillium, Matt, Ellen, Stephanie, Fang, Phillip & Micah

Recurring items:

  • Dev Update - Future of the Dev team (then separate breakout session)
    • Part 2 - User Testing w/Bonnie (will need to record)
    • Review Lunch & Learn Presentation
    • Review assignments for next week

Notes from meeting

  • Bonnie announcement - Matt will be the tech lead on this project; there have been multiple tech leads on the web team which has been really helpful and Matt brings that learning on what worked really well for the website team to VRMS

  • User Testing notes (Usability Testing 2 for VRMS)

  • Task 1 - sign into VRMS by following prompts and arrive to project management screen - no issue

  • Task 2 - add a new project "testy test" and add some reoccuring meeting times and return to the project management page: Remote should be default veresus In-Person; not sure what we are asking for with the Github Identifier - is the identifier the ID of that URL? If that's true you can go and find it yourself. If this is something we ask she wants to be asked it after inputting the URL. Slack URL is confusing to me - I think you mean the Slack Channel would be helpful if it said Slack Channel URL. In the box where the URL goes we could say what it begins with. What do you want from the drive URL? The link to the VRMS drive or to the VRMS folder. HFLA Website URL - would pull this from the project page online; this is clear. Wants to save this first becuase she adds reoccuring events. Not clear that we wanted the Zoom link under the Remote or In-Person selection. After she saves it jumps her up to the top - not sure if that is just a Figma issue.

  • Task 3 - Team meeting 1 starts at 7pm instead of 8pm find testy test and update the meeting time - recommends we paste the user test instructions into the chat if we test other people. Easily updated the meeting time.

  • Task 4 - Find David Rubenstein's email and add him to project testy test and then return to the project management screen. Easy to find his email but he had 3 emails. So she didn't know which one to select. She would like to see which is the last active email so she knows what to select. When the changes saved confirmation pops up you could have a choice - like save and continue or save and close to eliminate number of clicks. Another option is when I click save instead of taking over the screen it hovers just above where she clicked save and then it could disappear so you don't have to close it.

  • Task - David Rebenstein needs to be deleted from Testy Test - was able to remove Testy Test from David's name, liked the confirmation of that. Did not lick the big save confirmation once saved.

  • Other comments:

    • Gray out the login on the page until someone puts their email in then the color can show
    • Design elements like the login button will need to be within a certain Hack of LA color scheme
    • Wants to be able to hit save on the project page and not get picked out - wants save and continue to keep working in the project to add a new event
    • Expectation is when you click add a new event, that
    • When you add an event find it confusing that the blue button says apply
    • You could but a trash can next to the pencil icon on the product page to delete a specific meeting
    • Says the GitHub Identifier is the repository number - okay to have a guide in the MVP that pops up and tells people how to find it; most people won' tknow how to find it.
    • Would like to add, edit and remove people from the project page - like a plus sign to add a new member etc.
    • The primary Hack for LA color could work for buttons - each team that will use VRMS will have it in colors that represent their location. There is also a gray button she shows in the video toward the end that show what was selected initially - so it works across many color schemes. This is the link Bonnie shared that shows the gray button and how VRMS would be applied across different chapters. https://www.figma.com/file/VlsfGn1qZOAzpDymDQoTiy/VRMS-V4-Old-Files-(this-page-is-for-reference-only)?node-id=24403%3A2528&t=x0xjona30wkvFrE5-0

  • Feedback on Lunch & Learn Presentation
    - [ ] Need to update logo
    - [ ] Need to make sure that when you add a meeting name it appears versus asking for it to be in the description - Bonnie says she needs to fix that. For now the event name should be in the event name and description. This should never say meeting in the name.

Tasks

  • To be added during the meeting

Items for next week's agenda

  • Discuss updates to Github tickets between dev & design

@heyitsalexander
Copy link
Member

heyitsalexander commented Feb 28, 2023 •
edited

Writing this here. Add to meeting agenda for March 6th

From: @MattPereira (#1241 (comment))

I have not worked on this issue because I talked to Bonnie and we agreed that it would be better for her to test and approve the new user flow before devs start implementing it with code

I also think it might be a good idea to consider more clearly defining how we hand off issues from design to development

My proposal ( open to however you want to handle this ) :

Closing out UI/UX issues when they are finished to separate design issues from development
Have a UX or PM lead leave a comment at end of design issues as they are closed explaining the situation like "We tested this with the stakeholder and she approved, this is now ready to be decomposed into issues for developers"
And then add a ready for dev lead label and move the closed issue into the New Issue Approval column in order to communicate that the issue is ready for developers to start creating new issues to implement these beautiful designs

That way the action items of an issue won't already be checked off and can be tailored to the steps that need to be taken by developers to implement the code

Also it would be really helpful if there are figma links that could be included in addition to the screenshots

@MattPereira MattPereira moved this from New Issue Approval to General Information/Resources in VRMS - Active Project Board Mar 7, 2023
@MattPereira MattPereira changed the title VRMS Agenda All Teams: Meeting Agenda Monday 📝 Mar 7, 2023
@MattPereira MattPereira changed the title All Teams: Meeting Agenda Monday 📝 ALL TEAMS: Monday Meeting Agenda 📝 Mar 13, 2023
@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Mar 14, 2023 •
edited

2023-03-13 Meeting Agenda and Notes

Role Call (who is here) - Micah, Julia, Matt, Phillip, Trillium, Stephanie

Agenda items:

  • Bonnie Community of Practice Update
  • Dev Open Items - Questions from Brad on Open Issues / Any other specific issues?
  • Separate breakout sessions
  • PM/Design Session - Next Steps after Bonnie User Test
  • Follow-up on PM lunch & learn? Is another outreach needed?

Notes from meeting

  • Resolved issue Add edit icon to each users' name on user search page #1225 Brad was inquiring about - the edit he is recommended is okay
  • Issues between what shows in Figma and what Bonnie said in the video - some items in the prioritized backlog reflect what was found in the first user test. The recent user test reflects different information so we need to make sure the issues in the prioritized backlog, reflect the recent user testing. PM and design to remove issues from prioritized backlog that need to be updated. Dev. team will work on backend updates in interim.

Tasks

  • Updated prioritized backlog
  • [ ]Backend updates

Items for next week's agenda

  • Updates on the above

@jbubar
Copy link
Member Author

jbubar commented May 23, 2023 •
edited

Facilitator: Amanda
Time wizard: Trilluim
Scribe: Josh

  • Update on the dns problems - website not showing up for some ppl (10 min)
    • need to come up with a plan to fix it
  • Reflect on what bonnie needs from VRMS (10min)
    • Review it.
  • Plan to get some designers (10m)
    • need to add a few cards to open roles
  • Breakoutrooms

Notes:

DNS stuff - Bonnie is going to try it out tomorrow on onboarding

Getting designers

  • need design issues
  • need cards on open roles

Possible design issues:
Bonnie suggested that we have little nudges or error messages, such as "we dont recommend the use of the word meeting in your meeting time" - some more design work
Screen Shot 2023-05-22 at 7 31 03 PM

Bonnies reviewing project data changes - video: https://drive.google.com/file/d/1VkqlwJKVWQU4LuPfY9tvasOEDJI5F6Ud/view?usp=share_link

@Spiteless
Copy link
Member

Spiteless commented May 23, 2023 •
edited

Meeting minutes from timecop:

  • Intro - 7:00 - 7:10
  • DNS issues - 7:10 - 7:20
  • Discusion of last session - 7:20 - 7:20 ?
  • Plan to get designers - 7:10 - 7:20
  • Hear from Vanessa? - 7:20 - 7:25
  • Bonnie interjection about name/description of team meetings - 7:25 - 7:30 -- (⭐ WE ARE HERE ⭐)
  • Bonnie asks that interpersonal people should be dealt with PMs first, if it's with the PM then go up a level
    • No one should wait until it's a giant problem
  • Breakout rooms - 7:35 ++

@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Jun 6, 2023 •
edited

2023-06-05 Meeting Agenda and Notes

Role Call (who is here) - Julia Gab, Trillium Smith, Amanda Glover, Micah Elm, Vanessa Vun, Stephanie and Jack Haeger (Potential new PM!!), Kevin Moutoucarpin (lead of the onboarding team)

Agenda Items:

  • Overview of VRMS - goal of the project, what it includes
    • Next steps; how to move forward
    • Onboarding site map and user flow
    • Review high-level priorities for VRMS and next tasks

Notes from meeting

  • Trillium got the keys to his house
  • overview notes
    • API documentation: change this to integrating with other apps
    • Change product management: managing who is managing the product
    • have the code of conduct happen before they get the link to the zoom??
    • people need to remove the word meeting from the meeting title (Josh)
      • those rules are in the slide deck
    • have a popup that explains the meeting time bug with the 30 min
    • Bonnie shared that a top priority in onboarding would be to have volunteers check-in and read the code of conduct on VRMS before joining - this would help automate a manual process and save 15 minutes in onboarding
      -She also mentioned that updating meeting times fields need validation (immediate opportunity)
      -Josh/Amanda to meet weekly to go through the requirements doc and simplify next steps for an updated now, next later roadmap
      -Kevin - a UX researcher may be able to help VRMS a-sync

Items for next week's agenda

  • We will review the onboarding site map and user flow in the next meeting

@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Jun 11, 2023 •
edited by jbubar

2023-06-12 Meeting Agenda and Notes

Role Call (who is here):

Agenda Items:

  • Latest VRMS issues - high-level tickets for two big issues (Adding approval process for web content to VRMS & Using VRMS to complete Code of Conduct before onboarding) other new issue - removing Hack Night question
    • Discuss approach for larger issues & assign next tasks
    • Onboarding site map and user flow
    • Discuss what to prioritize in the onboarding process (based on what we know outside of adding the Code of Conduct feature)
  • Julia's deliverables: review the onboarding site map and user flow

Notes from meeting

Items for next week's agenda

  • TBD

@JackHaeg
Copy link
Member

JackHaeg commented Jul 6, 2023

Moving these items to Product Agenda:

  • review any issues that are in the new issue approval column for
    • UX Writing
    • [Product] - that are related to writing
  • Accountability and Support Check.

@JackHaeg
Copy link
Member

JackHaeg commented Oct 20, 2023 •
edited

2023-10-23 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Micah
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Oct 30, 2023 •
edited

2023-10-30 Meeting Agenda and Notes

Prework to prep for meeting

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Micah
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan
  • Nayan

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items:

Issue assignment cleanup:

Notes from meeting

  • New developer joined (Nayan), onboarded by Trillium
  • Trillium working on bug fix in the coming week.
  • Reviewed issues missing the size label, discussed next steps.

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Nov 13, 2023 •
edited by Steph112792

2023-11-13 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here: Feature link updated with new feature label, 0 issues are missing labels.

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Micah
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan

FYIs (nothing needs to be done, just keeping each other informed)

  • Jack is out of the country for throughout the rest of November, and will be unable to attend our next 3 Monday evening meetings (Monday meeting = 4am). However, he will continue to work on the project async, attend Thursday planning meetings, and will be available via Slack. Jack will plan to collaborate with / support PMs Rohan and Stephanie in their roles.

New Items

  • Julia: present new screens / flows to the team & clarify additional specs with Bonnie (recommend clarifying specs with Bonnie in a Breakout room to make best use of time)
  • Julia: to discuss 2 new issues mentioned on Slack (potentially in breakout room)
  • Trillium: check in on bug issue progress, explore next steps with team: Bug: Users Cannot Check In #1411
  • Trillium: split into breakout rooms, assign tasks to devs in attendance.
  • Josh: discuss issue cleanup of remaining issues with Bonnie. Recommend discussing if issues from "VRMS v0.4 Development" should remain open in this deprecated project, or moved to a newly created column in the Active Project Board.

Issue assignment cleanup:

Notes from meeting

  • Julia to go over her flows in FIGMA. (recorded)
    o There are two flows.
     Issue Create/Edit Events Details screens #1404
    • Creates an edit event form.
    o Problem arises when people don’t know how to edit meetings.
    o This would be a new form for a new event.
    o 2 New meeting mock ups ( Create new meeting 21 & 23)
    o Frequency of creating an event
    • Product details – Viewing form.
    o Bonnie gave input on Project details
     Issue Project Details screens (Create, Edit, View) #1408
  • Then Breakout rooms for Devs

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Nov 20, 2023 •
edited by juliagab56

2023-11-20 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here - All issues are labeled appropriately with size, role, feature, & milestone.

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Micah
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan

FYIs (nothing needs to be done, just keeping each other informed)

  • Hack for LA will be on break throughout December, and thus our last Monday night group call will be next week (November 27th). We will also hold a final PM/Design Lead Planning meeting the following Thursday (November 30). The PM/Design Lead Planning meeting for this week will be cancelled due to Thanksgiving.

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Nov 27, 2023 •
edited

2023-11-27 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here: All issues have been labelled appropriately.

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Micah
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan

FYIs (nothing needs to be done, just keeping each other informed)

  • Tonight's call will be our Monday night All Team call for 2023. We will return to conducting regular Monday night calls beginning in January 2024 (timing TBD - see the "New Items" section for more below). Jack will also be returning to all future VRMS meetings in January :)
  • We will hold the final PM/Design Lead Planning meeting on Thursday, November 30th.

Recurring items:

New Items

  • SCHEDULING: Ask the group when the would like to restart our Monday night calls in 2024. The first Monday call falls on a holiday (January 1st, 2024). Would the group like to (check winning answer):
    • 1). Keep the scheduled call
    • 2). Reschedule the call to Tuesday (Jan 2nd) at a time that fits Bonnie's and everyone on the team's schedule (if possible, please collect any specific times that could work for Bonnie on the call so that we can set up a poll),
    • 3). Cancel the call and meet the following week (Jan 8th).
    • Note - We can also set up a poll on Slack so that everyone can be included - this is just to get an idea of everyone's availability
  • Trillium: check in on bug issue progress, explore next steps with team (any steps in particular to fix daylight savings issue mentioned in last update): Bug: Users Cannot Check In #1411
  • Julia: To present any new screens / request feedback as needed (if she can attend)
  • Trillium - check in on any relevant PRs, split up between devs: https://github.com/hackforla/VRMS/pulls
  • Trillium / Josh - assign prioritized issues amongst devs.
  • Josh: Check in on this issue's progress / if there are any issues in particular that need more clarification: Issue Cleanup: Review old issues assigned to inactive projects #1538

Issues that were not checked off from the last call:

Issue assignment cleanup:

Notes from meeting

  1. Bonnie came through and asked for VRMS to host the in person signup and checkin for 3 events over the holiday break.
  • linkedin workshop part 1, part 2, and holiday party (in the project called Hack4LA)
  1. Trillium is making progress on the timing bug
  2. Rohan is being peer pressured to fly in for the holiday party
  3. Evan is going to try to make a backend migration file (this is a big step because we will need to do this for a lot of other features)
  4. The whole team wants to skip the meeting on the 1st and come back on the 8th.
  5. The team forgot to ask bonnie about the gmail migration while we had the chance 🤦‍♂️
  6. Josh has not made any progress on his issue, but has it in his calendar for when he gets back from his awesome trip
  7. did a quick recap of the year and what was merged into the product. Mad props to the team for making the app look a lot better, work better, and decreasing technical debt

Tasks

Items for next week's agenda

@JackHaeg JackHaeg mentioned this issue Nov 30, 2023
Open
@JackHaeg
Copy link
Member

JackHaeg commented Jan 23, 2024 •
edited

2024-01-22 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

add issue numbers to be discussed and any notes that will be helpful

Issue assignment cleanup:

Notes from meeting:

  • Onboarded new dev, Daniel Kim.
  • Josh & Trillium worked to export a CSV of people who attended the holiday party, which will be shared with Bonnie.
  • 3 of the new devs who attended the first meeting of the year did attend. It appears we are looking for at least 1-2 more full stack developers going forward.
  • Reviewed designs from Julia, discussed next steps in design review and handoff.

Tasks

  • Inform Bonnie that we could request 1-2 more full stack developers at the next Hack4LA onboarding meeting
  • Provide Bonnie with CSV of holiday party attendees
  • Update Engineering roles to mention full stack developers, and repost.

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Jan 30, 2024 •
edited

2024-01-29 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Evan
  • Daniel
  • Brad
  • Stephen
  • Julia
  • Jack
  • Rohan

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

  • Discuss project details bug and removal of project location
  • Discuss new dev role postings (back end and full stack)
  • What are current UALs on Hack For LA
  • Julia will work on new designs with modal for project member selection on new "Project Details" screen

Tasks

  • Discuss project details bug and removal of project location
  • Discuss new dev role postings (back end and full stack)
  • Gather feedback on new project details screens
  • Trillium - what are current UALs?

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Feb 6, 2024 •
edited

2024-02-05 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan
  • Daniel Kim

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Feb 13, 2024 •
edited

2024-02-11 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here: No open issues missing labels. ALL issues (including closed issues) have been labeled with appropriate feature labels.

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan
  • Daniel
  • Jo (new developer)

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Currently, it looks like check ins are not matching up
Check in Bug

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Feb 27, 2024 •
edited

[2024-02-26] Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Trillium
  • Josh
  • Nayan
  • Brad
  • Evan
  • Stephen
  • Julia
  • Jack
  • Steph
  • Rohan
  • Daniel
  • Jo
  • Vincent

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

  • Introduce new team members, make sure new joiners have onboarded okay from the last week.

New Items

Trillium / group:

Ask Josh / Julia:

Issue assignment cleanup:

Notes from meeting

  • See notes in italics in the "New Items" section above

Tasks

  • Check in bug to be resolved and implemented in PROD
  • Jack & Julia to meet to discuss next steps for updated designs
  • Jack & Trillium to meet to discuss next QA, review board together, discuss design handoff
  • Onboard Vincent (add to Google Drive)

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Mar 5, 2024 •
edited

2024-03-04 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Vincent

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

--
Split up between Dev / PM & Design

Issue assignment cleanup:

Notes from meeting

Tasks

  • Julia, Trillium, Jack to meet to discuss design system on Thursday at 10am PST

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Mar 12, 2024 •
edited

2024-03-11 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here - All issues have been appropriately labeled.

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Vincent

FYIs (nothing needs to be done, just keeping each other informed)

  • Trillium unable to join until 7:40pm

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

  • Explored Jo's blocker on her issue, Josh and team worked on the issue together with her.
  • Trillium unavailable until the end of the call, will follow up on points missed during call.
  • Jack & Rohan discussed privacy policy, assigned Rohan to start working on the issue.
  • Jack, Rohan & Julia discussed next steps on design issues, plan to connect with Trillium again this week and set up another meeting to discuss next steps on MUI updates.

Tasks

  • Message Trillium re: questions mentioned above (did not have time to discuss at end of meeting)

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Mar 19, 2024 •
edited

2024-03-18 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Vincent

FYIs (nothing needs to be done, just keeping each other informed)

  • Trillium and Josh unable to join tonight due to scheduling issues. Trillium will follow up with the team's developers to assign issues, review PRs and answer questions over Slack this week.

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

  • Jack to meet with Trillium to catch up on issues and planning

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Mar 26, 2024 •
edited

2024-03-25 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here - All open issues have been labeled appropriately.

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Trillium / devs:

Issues from previous All Team to discuss with Trillium

Design / PMs

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Apr 2, 2024 •
edited

2024-04-01 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler (new dev)

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Apr 9, 2024 •
edited

2024-04-08 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Separate into rooms, assign new issues, review PRs

Issue assignment cleanup:

Notes from meeting

  • Completed tasks above
  • Commented on ongoing check in bug issues (will develop with Trillium into smaller issues)
  • Answered Jo's questions on her assigned issue
  • Created several issues for MUI epic and assigned to Nayan
  • Discussed Project Status design changes with Julia

Tasks

  • Trillium to meet with DevOps this week
  • Jack / Trillium to create additional issues related to Check In bug and Create A Profile
  • Jack / Julia to continue to work on finalizing Project Status requirements

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Apr 16, 2024 •
edited

2024-04-15 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Breakout rooms:

  • Julia / Jack to discuss issue creation for "project status" feature with Trillium / set up a separate meeting to work on this when time allows.
    • Julia presented mockups to the team, changes recommended for "Delete" flow, adding link to project view / events screen within Recurring Events need to be removed modal, etc.

Issue assignment cleanup:

Notes from meeting

Tasks

  • Jack / Trillium to create additional issues related to Check In bug and Create A Profile

Items for next week's agenda

@josiehandeveloper josiehandeveloper moved this from General Information/Resources to In progress in VRMS - Active Project Board Apr 21, 2024
@JackHaeg JackHaeg moved this from In progress to General Information/Resources in VRMS - Active Project Board Apr 23, 2024
@JackHaeg
Copy link
Member

JackHaeg commented Apr 23, 2024 •
edited

2024-04-22 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

  • Assigned Onboarding issue to Chandler, discussed next steps
  • Reviewed Brad's PR together, made comments on required changes
  • Live troubleshooting of Nayan's Environment. Could not come up with fix during meeting, plan is for Trillium & Nayan to meet later this week to explore alternative fixes.

Tasks

  • Nayan & Trillium to meet to explore resolutions to Environment issue.
  • Trillium & Jack to meet to refine issues.

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Apr 30, 2024 •
edited

2024-04-29 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here:

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

New issues to review & assign (some may be good first issues):

Trillium - if time permits (otherwise will discuss async)

Issue assignment cleanup:

Notes from meeting

  • Julia unavailable due to scheduling conflict

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented May 7, 2024 •
edited

2024-05-06 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here: All issues have been labeled appropriately (new issue has been labeled)

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items & Notes

Split up into breakout rooms

  • Julia - to present final designs on Project Status changes, work on writing up issue with specs, to handoff to devs next week.
    • Julia briefly presented issues - discussed "delete" project function & will work on finalizing annotations / cleaning up screens over the next week. She will be unable to meet for Thursday's call.

Issue assignment cleanup:

Notes from meeting

  • See notes in italics within "New Items" section above
  • Tagged Trillium on Check In Bug & will provide next steps
  • Trillium & Josh assisting Nayan on addressing setting up local dev environment.

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented May 14, 2024 •
edited

2024-05-13 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here (e.g., A improving, B needs work, etc.)

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

  • Trillium & Josh
    • check in on status of writing up additional issues for Epic: DB accepts capital and lower case email creditals for email login #1456 so that we can unblock this epic.
      • Trillium & Josh plan to meet this week to work on these issues.
    • Want me to follow up with Bonnie on questions listed on this issue: Address security concerns raised by #1086 #1469. If questions are already addressed, let's revise the issue and place in prioritized backlog or epics accordingly.
      • No need to ask Bonnie - these answers will be found in the DevOps meeting. Moved issue to prioritized backlog for now per Trillium
    • Noticed that a lot of the Package Update issues within the "security" milestone are outdated with package version numbers. Let me know if you'd like some assistance updating these.
      • Trillium & Josh reported no need to update package version numbers. Per Trillium - plan is to switch to Vite, and then close some of these React update package issues within this security milestone
  • Josh:
  • Trillium
    • Check in on status of writing up comment next steps for Check In Bug.
      • Plans to work on it this week.
    • DevOps meeting to discuss secrets?
      • Josh will attend the meeting this week
    • Set up a time to review new issue approval and work on issue mentioned last week (e.g., removing all Projects from Dev Instance and clone projects from PROD instance).
  • Team (PRs) - Revisiting reviewing PRs more regularly. (spend time during call to review / merge).
    • Trillium & Chandler - noticed that PR feat: Add disabled logic, update classnames for buttons #1629 was reviewed by Chandler last week and Brad approved these changes yesterday. Discussed how to streamline this process and how to merge changes.
    • Evan - requested status on his PR review: update: no longer use bodyparser #1622 (Looks like Josh is requested as reviewer). Looks to address Drop depricated bodyParser #1524. Reminder - team please pick from issues in the prioritized backlog.
    • Chandler - great work on submitting another PR: Remove ability for PMs to edit Project Information on VRMS #1634.
      • This PR addresses a fairly major issue, so it would be great if we could merge this PR as a priority.
      • Took a look at this as a team, discussed merge process.
    • Brad - Great work on this PR: Change btn text #1635. Note that the issue asked for the text to read "Create Profile" and not "Create A New Profile"
      • Brad pushed a new PR with this fix
    • Trillium/team - looks like we also have some older PRs that are waiting to be reviewed as well (see if additional labelling required: e.g., "waiting to merge").
      • Reviewed PRs, none are missing labels, plan to have team split up review process
  • Jo - any new issues with Remove "Hack Night" Question From New User Check In and Create a New Profile #1399?
    • Please feel free to ask any questions, and we can work on building out this issue further, as additional steps were mentioned by Trillium in our last call.
    • (Jo was unavailable during the call, however issue was reviewed by Trillium and appears sufficient)
  • Nayan - any updates on setting up environment?
    • Nayan reported his dev environment started working again
  • Assign Create loading state for save buttons on forms related to projects #1574 if anyone is interested. Completing this issue would finally close the epic, which another team is waiting for feedback on.
    • Chandler assigned
  • Separate into breakout rooms.
  • Julia - to discuss project status specs

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg JackHaeg mentioned this issue May 16, 2024
Closed
4 tasks
@JackHaeg
Copy link
Member

JackHaeg commented May 21, 2024 •
edited

2024-05-20 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here: All issues have been labeled appropriately.

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler
  • Angela Lee (new developer member)

FYIs (nothing needs to be done, just keeping each other informed)

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg JackHaeg self-assigned this May 21, 2024
@JackHaeg
Copy link
Member

JackHaeg commented Jun 4, 2024 •
edited

2024-06-03 Meeting Agenda and Notes

Prework to prep for meeting

  • Review the QA
  • Perform Label Audit and add summary here: All issues have been labeled appropriately.

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Rohan
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Jo
  • Chandler
  • Angela
  • Kat

FYIs (nothing needs to be done, just keeping each other informed)

  • Daniel still on the project?
  • HfLA will be taking a break throughout the month of July (meetings will be updated in the calendar, still okay to continue work and discuss async over Slack/GitHub).
  • Old version of GitHub projects that we are currently using will be sunset in August. We will be transferring over to the new experience in the coming weeks. Will updated team after further discussion with Bonnie.
  • When reviewing issues, please pick from issues in the "prioritized backlog" column, never issues from the "New Issue Approval" column, as many of these are draft issues or older issues that may have already been resolved.

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

  • Kat re-joined the team (Full Stack Dev)
  • Appears Daniel is no longer on the project - will plan to get in touch to check in.
  • Nayan's Dev environment is not working again. Trillium to reach out to assist. May re-assign MUI issue to another dev if the dev environment issue cannot be resolved. Check in again next week.

Tasks

Items for next week's agenda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JackHaeg JackHaeg

Labels
feature: Agenda role: Product size: 0.5pt Can be done in 2-3 hours or less
Projects
VRMS - Active Project Board
General Information/Resources
Milestone
03.01 Project Management
Development

No branches or pull requests
8 participants
@Spiteless @ExperimentsInHonesty @heyitsalexander @jbubar @Steph112792 @AmandaGlover-PM @JackHaeg @vaidyarohan