VRMS: ALL: Monday Meeting Agenda 📝 #1280

jbubar · 2023-01-31T03:10:41Z

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
- [x] 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)
- [x] Jack
- [ ] Bonnie
- [ ] Trillium
- [ ] Julia
- [ ] Josh
- [ ] Brad
- [ ] Evan
- [ ] Angela 
- [ ] Katiuska
- [ ] Nora 
- [ ] Nikhil
- [ ] Mudassir
- [ ] Sankshay
- [ ] Vorleak
- [ ] James
- [ ] Pluto

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


### Recurring items: 

### New Items 

### Issue assignment cleanup: 
**PMs / Designers**
- [ ] [Jack](https://github.com/hackforla/VRMS/issues/assigned/JackHaeg)
- [ ] [Julia](https://github.com/hackforla/VRMS/issues/assigned/juliagab56)

**Developers**
- [ ] [Trillium](https://github.com/hackforla/VRMS/issues/assigned/Spiteless)
- [ ] [Josh](https://github.com/hackforla/VRMS/issues/assigned/jbubar)
- [ ] [Brad](https://github.com/hackforla/VRMS/issues/assigned/bkmorgan3)
- [ ] [Evan](https://github.com/hackforla/VRMS/issues/assigned/evanyang1)
- [ ] [Angela](https://github.com/hackforla/VRMS/issues/assigned/awlfccamp)
- [ ] [Katiuska](https://github.com/hackforla/VRMS/issues/assigned/chukalicious)
- [ ] [Nora](https://github.com/hackforla/VRMS/issues/assigned/ntrehan)
- [ ] [Nikhil](https://github.com/hackforla/VRMS/issues/assigned/nora-zajzon)
- [ ] [Mudassir](https://github.com/hackforla/VRMS/issues/assigned/hussainmudassir)
- [ ] [Sankshay](https://github.com/hackforla/VRMS/issues/assigned/sankshaypusa)
- [ ] [Vorleak](https://github.com/hackforla/VRMS/issues/assigned/vorleakyek)
- [ ] [James](https://github.com/hackforla/VRMS/issues/assigned/jng34)
- [ ] [Pluto](https://github.com/hackforla/VRMS/issues/assigned/pluto-bell)

### 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.

The text was updated successfully, but these errors were encountered:

jbubar · 2023-01-31T03:31:42Z

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 · 2023-01-31T04:37:10Z

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 · 2023-02-04T00:28:49Z

AmandaGlover-PM · 2023-02-07T04:35:39Z

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:

PM Updates
- Design Review - Clickable Prototype: https://www.figma.com/proto/pIxFTL62Nx2XyQdZy1fR6f/VRMS-v.4?page-id=119%3A46&node-i[…]in-zoom&starting-point-node-id=1056%3A902&show-proto-sidebar=1
Dev updates / availability
- Review assignments for next week

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 [email protected] 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 · 2023-02-09T23:15:30Z

ExperimentsInHonesty · 2023-02-18T17:52:58Z

@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 · 2023-02-18T17:55:02Z

@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 · 2023-02-18T17:56:51Z

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

ExperimentsInHonesty · 2023-02-25T17:36:02Z

@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 · 2023-02-25T17:55:58Z

Sounds good. Working on the logo Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Bonnie Wolfe ***@***.***> Sent: Saturday, February 25, 2023 9:36:13 AM To: hackforla/VRMS ***@***.***> Cc: heyitsalexander ***@***.***>; Mention ***@***.***> Subject: Re: [hackforla/VRMS] VRMS Agenda (Issue hackforla/VRMS#1280) @heyitsalexander<https://github.com/heyitsalexander> I dont see that you made the logo change yet. See hackforla/VRMS#1280 (comment)<#1280 (comment)>. I will want to review/revise the Lunch n' Learn deck VRMS - How to Add/Edit Meeting Times slides<https://docs.google.com/presentation/d/1bv9QH-d5qKtFCaecgCvsv608IoeLIpHfW7cEEqijHyE> with your team on the 27th, so it can be ready for the 6th. — Reply to this email directly, view it on GitHub<#1280 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJLJ3Y357OAA376OQMDEDFDWZI7I3ANCNFSM6AAAAAAUL45B4Q>. You are receiving this because you were mentioned.Message ID: ***@***.***>

AmandaGlover-PM · 2023-02-28T02:38:18Z

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 · 2023-02-28T03:07:03Z

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

AmandaGlover-PM · 2023-03-14T01:37:53Z

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 · 2023-05-23T02:05:37Z

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

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

trillium · 2023-05-23T02:08:54Z

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 · 2023-06-06T01:33:22Z

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 · 2023-06-11T22:57:07Z

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 · 2023-07-06T23:14:00Z

Moving these items to Product Agenda:

JackHaeg · 2023-07-06T23:17:22Z

JackHaeg · 2024-05-07T01:31:13Z

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)

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 · 2024-05-14T01:30:35Z

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)

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:
- Status of old issue review.
  - Plans to review this week, noted that many of these issues will be closed due to package update changes suggested by Trillium
- Noticed this issue: Set Github Secrets for Production Environment #1099 has been placed in the prioritized backlog for a while with dependencies. Should we keep this here or move back to the icebox? Also what are the specific dependencies?
  - Josh (& maybe Brad) will attend DevOps meeting and discuss Set Github Secrets for Production Environment #1099, Assist with migrating deployment to Terraform #1497, Fix VRMS redirect link without subdomain incubator#70, 1544 & 1496
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 · 2024-05-21T01:02:10Z

JackHaeg · 2024-06-04T02:00:13Z

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)

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

Trillium:
- New issues: Fix display issue with TitledBox in Project Form #1646 & On admin login page, make error state " " to prevent layout shift #1645
- Updates on adding next steps to check in bug issue
- Okay to open up MUI issue to team?
- Provide assistance to Nayan on Update HTML components to MUI: ./src/components/auth/Auth.js #1626
- Can we move 401 Status Code at Launch #1320 out of Questions/Review column so that it can be worked on?
- We will require Google Drive URL on the Project Management screen (we will unblock the comment out request previously made)
- If we were to validate the Github Identifier (not a , would that simply be a requirement of:
Josh:
- Previously, you mentioned wanting to create a an epic issue for all of the security issues. Based on: Address security concerns raised by #1086 #1469
  - Add the rest of the security issues to this as "related issues"?
  - Input from Trillium
  - Let's set up a time to work on this
- Epic: DB accepts capital and lower case email creditals for email login #1456
Brad:
- Investigate and Block Zoom Links from VRMS API #1659
- Also plans to take a look at Merge Vite Branch PR for Trillium
Angela:
- Any issues with VRMS Onboarding #1643? Looks like the last step is the PR - please let us know if you have any questions.. Submitting this PR will close the issue.
  - Closed Onboarding issue - couldn't find anything to update on Contributing Document. Also closed MUI issue, because the component: ./src/components/user-admin/AddNewProject.js was not being imported
  - _Plans to continue on _
Chandler:
- Discussion of new PR: Create loading state for save button on ProjectForm.js #1650
- Plans to review Trilliums latest feedback.

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

JackHaeg · 2024-06-11T01:45:52Z

2024-06-10 Meeting Agenda and Notes

Prework to prep for meeting

Review the QA
Perform Label Audit and add summary here. All labels are up to date

Role Call (who is here - add team names)

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

Conducting GitHub migration: GitHub Project Migration (Active Project Board) #1661
- Any cards on active project board will be moved to the wiki.
- Non-active project boards will be cleared of all notes, Roadmap board cards will be copied over to a spreadsheet.
- On the Deprecated VRMS v0.4 Development board:
  - All closed issues will be moved to the done column, cards will be deleted, and any cards that appear to be issues will be converted to issues, closed as unplanned, and moved to the "done" column.
- On Thursday, Bonnie and Jack will be completing the migration.
  - Note that the project board link will change post-migration, and will be shared on Slack. So, everyone will want to update their bookmarks, and fix any links you have to the old board if you have them embedded in your tickets/wiki/docs.
- We will also perform an audit on the VRMS-write team on GitHub, and remove inactive members.
Any questions on these changes? This should not impact how we build / deploy apps generally. The biggest change will be the link update.
Will also provide an update on July break after meeting with Bonnie on Thursday.

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg · 2024-06-18T01:47:18Z

2024-06-17 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)

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

(confirmed) HfLA will be taking a break for the month of July. Next Monday's call will be our last meeting until August. Anyone is welcome to continue working and continue communicating async over Slack if they would like.
Team updates on Daniel & Rohan, offboarding.
Will be conducting a review of GitHub Project teams.
New GitHub project board!
- Discuss views
- Note, any change to a project board view will be reflected across the team.
- Trillium - Created 2 new issues related to MUI successfully, however still received an email "Run failed: Create card for new issues - development (3c33ea8)".
  - https://github.com/hackforla/VRMS/actions/runs/9557023238
  - https://github.com/hackforla/VRMS/actions/runs/9557007785
    - See warning: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: peter-evans/create-or-update-project-card@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
  - Despite these notifications, both cards were successfully created and added to the board.
    - _After review, it appears that this issue was caused by an old workflow, which will be removed by Josh in Remove .github/workflows/New-issue-create-card.yml from the project #1674 _

Recurring items:

New Items

BREAKOUT ROOMS

Bonnie
- Create Spreadsheet of Google Drive URLs for HfLA Teams #1660 - Confirm that Google Drive URLs is complete (appears to be so).
- Epic: Github Project Migration #1669
  - Open roles next steps for onboarding tomorrow. Only recruiting one role: Mid level Back End Developer.
  - Recruit volunteers for team open roles #1670
    - Next steps for homework.
  - Planning to also backup within comments & a new issue: (inactive) VRMS Research board
Steph
- Great job on the Git transition tasks last week!

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg · 2024-06-25T01:50:31Z

JackHaeg · 2024-08-06T01:57:41Z

2024-08-05

Prework to prep for meeting

Review the QA
Perform Label Audit and add summary here - all issues labeled accordingly.

Role Call (who is here - add team names)

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

Nora out of country / no internet for next 3 weeks - will be unable to respond to messages on PRs, okay to handoff work if necessary.
Next week, People Depot will attend our call to discuss VRMS needs for database fields and permissions architecture. Discuss next steps to prepare. (building VRMS on top of People Depot's backend)
Processes update:
- Devs to use issue cleanup on Monday calls
- Splitting up PRs amongst team members (2 approved reviews before merging). Aim to improve turnaround time to feedback / merged work.
- Reminder - Weekly update in issue comments:

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
 - remember to add links to the top of the issue if they are going to be needed again.

Recurring items:

New Items

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg · 2024-08-13T00:59:51Z

JackHaeg · 2024-08-27T01:35:37Z

JackHaeg · 2024-09-05T20:00:21Z

Reminder for next Monday's All Team Call (per Trillium):

Due to the Vite merge, the application now runs on node 18. Please install node 18 using nvm.
Please also reinstall all dependencies in the base folder, server, and client.

JackHaeg · 2024-09-10T01:35:31Z

2024-09-09 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)

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

Due to the Vite merge, the application now runs on node 18. Please install node 18 using nvm.
Please also reinstall all dependencies in the base folder, server, and client.

Recurring items:

New Items

New Issues:

Epic - User Permission Search #1737
- To be broken down into smaller issues with devs in order. Review Initial low-fi mockups from Bonnie.
- This will be top priority, so we are looking to finalize the issue this week and get into development work ASAP. Requested to skip UI/UX process as this is a momentary fix. Bonnie still needs to review Create ability for Admins to promote and demote Admins #1486 in greater depth to ensure that it aligns properly.
  - Trillium will also look at Create ability for Admins to promote and demote Admins #1486 again to see how it aligns / if necessary to include in epic given requirements.
- Also, discuss rebuild of Prod, and what PRs need to be merged prior to implementation.
- Speak with Julia further -
  - Julia to create some potential alternate options (with search bar included and potentially keeping everything to just the "User" tab while utilizing filters. Jack to meet with Trillium to help break down this epic into dev issues, and confirm with Bonnie that requirement = see a full list of users upon blank search for "results by Admin" and "results by Project Lead".
Update "Hack Night" Question & Date picker From New User Check In and Create a New Profile #1729
- Discuss requirements. - Jack to work on finalize from Product perspective and send over to Trillium for final review
Project Status Issue Epic - to be assigned after completing creation of the User Permission Fix.

PR Review:

Please split up PRs and take on 1x week if possible. Trillium to explain process of reviewing PRs to group.

Nora’s PR:

Replaced HTML components with MUI applicable components #1688
- PR was force-pushed, but appears no changes were made.
- Does this require a revert or are we okay leaving as is? - NO - nothing needs to be done
- Okay for Nora to submit another PR? - YES

Evan/Trillium:

Trillium:

Fix the api for projects to include project users #1163 - would this issue enable us to show a list of members on the project details page within VRMS (and a list of users X project on the User Permissions screen) or would fixing the API only impact something like what is displayed on the HfLA website? - Trillium mentioned this might enable showing a list of members by project, and could potentially be linked to the User Permission Management epic, but he will need to take another look (Jack to follow up)
Do Devs typically need to be added to the VRMS 1Password? If so, can add to onboarding issue - Answer = NO. Leave off of onboarding issue.
Any documentation we need to update on the GitHub in regard to the Contributing document post-vite merge (i.e., using node 18)? https://github.com/hackforla/VRMS/blob/development/CONTRIBUTING.md - Answer = NO changes necessary
This issue is in New Approval column, do we want to place it in the “Epic” column for now, or do we need to make further edits? Allow admins to update user information - email #1495 - Trillium to review further. Jack to tag Trillium in comments.
Newly Created issues:
- Let's set up a time to review People Depot requirements for VRMS this week, and to work on epics/issues for User Permissions, & Field Validations - Jack to reach out to Trillium to set up time to discuss.
Mention migration to Terraform… do we need to create any new issues to get this launched? (per discussion at end of last week) Assist with migrating deployment to Terraform #1497 - Trillium said he will attend the ops call and discuss with them further.

Julia:

Review edits to screens together, along with final flow… Finalize Project Status Designs #1678 - reviewed, Julia to respond to Jack's comments this week to finalize designs, and then we can close this issue.
Discuss next steps with All Projects view and issues… - Did not have time to discuss, will circle back next week.
Potentially review Bonnie’s mock ups again and get any immediate feedback / work through changes. - Reviewed, plan to discuss

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg · 2024-09-17T01:53:08Z

2024-09-16 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)

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

Trillium out sick today, Julia unable to join.

Recurring items:

Check in! How is everyone doing? Any questions / issues we'd like to discuss during the call?

New Items:

Believe this issue is not complete - discuss reopening Form Validation - Github URL #1367

Nikhil & Team

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Josh, Brad & team reviewed existing PRs
Assigned Mudassir good first issue.
Jack & Nikhil created new issue: Implement Super Admin User Feature #1747
- Discussed next steps on the epic & explored minor changes to Nikhil's latest PR 1486 - The ability to set a User as Admin on Edit Users Page #1746
- Nikhil to continue working on Create ability for Admins to promote and demote Admins #1486 & Implement Super Admin User Feature #1747. May hand off other issues on the epic Epic - User Permission Search #1737 to Mudassir due to new work schedule.

Tasks

Items for next week's agenda

JackHaeg · 2024-09-24T01:56:15Z

2024-09-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)

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

Recurring items:

New Items

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg · 2024-10-01T01:59:54Z

2024-09-30 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

Nora out due to schedule next 2 Mondays, but is still working on issues async and available by slack
Chandler out tonight
Dev rebuild broken at the moment. FYI - dev rebuild is manually triggered via GitHub actions currently.
Posting open role positions (full stack & backend developers, additional PM).

Recurring items:

New Items

Trillium:

Dev Rebuild issue next steps (creating issue). Aim to provide demo to Bonnie of Nikhil's merged PR on Thursday call if possible (Admin promotion / demotion feature)
- At all related to Chandler's PR? Fix display issue with TitledBox in Project Form #1658
- Change practice of building and deploying VRMS (with dev and prod) #1758
  - Also, any next steps required for this issue? Move to In Progress as part of these fixes?
  - Or place in icebox until Chandler's PR is merged - aim to avoid breaking functionality/usability of PROD with existing dev build.
Epic - User Permission Search #1737 Did you have a chance to take a look at this epic and specifically review & build out the action items for each of the issues (Redesign the "Users" Screen #1751, Create the "User Permission Search" screen #1752, Create Search Display Component #1753, Create filtered permissions data component #1754)?
- FYI - I have added the label "ready for dev lead" and assigned you to these issues that need a second look.
- Please take a look at these issues this week so that we can assign to devs and continue progress. Also, if you can please take a look at the epic as well, that would be super helpful!
Define and get appropriate access to AWS for VRMS #1474
- Discuss next steps with Trillium & Josh. Not sure how this is related to Admin Login Requires Multiple Attempts #1322
Should we close Nora's PR? replaced html with mui in index #1748
- Cleanup of other PRs

Josh & Trillium

Is this issue up-to-date? Epic: DB accepts capital and lower case email creditals for email login #1456
Previously mentioned needing to add points re:
- Connecting to backend
- Propagating the changes so that the new User ID remains in all of the checkins.

Trillium & Evan

Write a script for cleaning up backend emails #1551
- Josh closed Nayan's PR feat: script to clean up backend emails #1612 that was waiting for review the other week because Nayan is no longer on the team.
- Given that, Nayan has been unassigned from the issue.
- However, the issue is still in progress with Evan assigned.
- Is Evan still interested in working on this issue, or should we move this issue back to the prioritized backlog and unassign Evan?

Chandler

Had a question for Trillium re: her PR: Fix display issue with TitledBox in Project Form #1658
"Re: the failing tests on my PR. is this something with my PR specifically, a devops thing, or something that I haven’t considered?"

Nikhil

Updates on Super Admin User issue?

Angela

Noticed latest PRs - any questions or concerns? (other than the issue mentioned above)

Brad

Update on Investigate and Block Zoom Links from VRMS API #1659

Team:

PR cleanup / assignment.

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

ExperimentsInHonesty · 2024-10-07T21:01:28Z

Add this to your next agenda Fix VRMS redirect link without subdomain incubator#70 (comment)

JackHaeg · 2024-10-07T22:58:45Z

2024-10-07 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

Posted new roles for PM & Full Stack Engineers.

Recurring items:

New Items

Create Spreadsheet of VRMS Database Fields for People Depot #1772
- Discuss spreadsheet / plan of work re: starting with PROD, ending with DEV check.
- What are the database table names for VRMS?

Nikhil / Mudassir

Trillium & I have finished up writing a number of issues for Epic - User Permission Search #1737.
- Please take a look and complete issues in order. Note that the following are all backend issues:
- Redesign the "Users" Screen #1751 is a front end issue, and is also available to review

Nikhil

re: Added Super User Functionality #1765
- Can we remove the promoted super user admin "[email protected]" after finalizing testing on this PR? Want to ensure that only [email protected] is super admin user on VRMS. Assume this user is only a super admin user on Dev, correct?
Still actively working on In Progress issues, or place back in "Prioritized Backlog"?

Trillium

Angela

Can you please post a link to the list of AWS services found on Define and get appropriate access to AWS for VRMS #1474? Past in this "Development" Google Drive folder: https://drive.google.com/drive/u/3/folders/1m4pS3kidCY2VrcNQWhtpLThSKQSplkax
Any issues so far with: Adapt ValidatedTextField to accept custom validation functions #1484

Julia

Closing this issue or keep open and place in icebox until MUI changes are complete? Review and refine User Check In page UI #1597
Closing Finalize Project Status Designs #1678
Potential cleanup / refinement of old UI/UX issues on the project board.

Full Team

Review & assign PRs.

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Trillium provided a list of VRMS Database Table Names for People Depot Issue
Vite build issue is ongoing, no solution identified as of yet. Trillium plans to attend meetup to get assistance on the issue.
- Also confirmed that once Vite Build Issue is resolved, we will likely rebuild with all existing functionality first prior to rebuilding with new features (e.g., MUI changes, User Permission Search features, etc.).
Updated Wiki Technology page with Vite and MUI links on front end tech stack
Evan busy with school at the moment and may not be able to take on additional issues in the near future.

Tasks

Items for next week's agenda

JackHaeg · 2024-10-15T01:53:33Z

JackHaeg · 2024-10-22T02:00:54Z

2024-10-21 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)

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

Chandler offboarding from team
Welcome to our new member!! Pluto Bell (they/them):
- VRMS Onboarding - Pluto Bell #1800

Recurring items:

New Items

Sankshay:

VRMS Onboarding - Sankshay Pusa #1792
Vorleak & James - any questions with onboarding?

Trillium:

Angela:

Update "Hack Night" Question & Date picker From New User Check In and Create a New Profile #1729

Full team:

Please take on one PR to review this week, as we need to reduce the number of active PRs on our repo.

Issue assignment cleanup:

PMs / Designers

Jack
Julia

Developers

Notes from meeting

Trillium Demo’d how to review PRs with the team per request
Team plans to review PRs 1 per week at least
We will now be adding a label “ready for dev lead” once a PR is approved and we need Trillium to review/merge…
Onboarded Pluto
Offboarded Chandler
Nora got feedback on how to deal with commits from her local environment
Sankshay to work on MUI issues
Brad will help out on Super User Admin email issue (Jack to send additional info)
Trillium to review Hook in APIs to filtered permissions data component #1801 & [vrms.io] Most meeting times are stuck at "2024-03-xx" - "2024-04-xx" #1795 this week.

Tasks

Jack to create issue for Trilium to track Super User Admin email address bug on dev.
Trillium to review & refine Hook in APIs to filtered permissions data component #1801 & [vrms.io] Most meeting times are stuck at "2024-03-xx" - "2024-04-xx" #1795 this week.

Items for next week's agenda

JackHaeg · 2024-10-29T01:45:22Z

2024-10-28 Meeting Agenda and Notes

Prework to prep for meeting

Review the QA
Perform Label Audit and add summary here: All issues labelled appropriately, however several issues were assigned in the Prioritized Backlog

Role Call (who is here - add team names)

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

VRMS project board was closed near the end of last week, reopened
- Review GitHub Project Board Workflows with team (all were turned off until tonight): https://github.com/orgs/hackforla/projects/72/workflows/21484765
- Should “Code changes requested” status = Questions/Review
Great work on reviewing PRs - let’s keep this up!
- Trillium - Will we have the ability to merge some PRs this week? Last merge: 3w
- When can we rebuild PROD again?
  - Looks like maybe after Fix Super Admin User Login issue #1802 is completed, then we could at least get the promote/demote Admins feature and the Super Admin User feature into PROD.

Recurring items:

New Items

Trillium:

Issue assignment cleanup:

PMs / Designers

Jack
Julia

Developers

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg · 2024-11-05T02:50:56Z

2024-11-04 Meeting Agenda and Notes

Prework to prep for meeting

Review the QA
Perform Label Audit and add summary here: All issues labelled appropriately, no link changes required this week.

Role Call (who is here - add team names)

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

Winter break for HfLA (Thanksgiving + all of December)
Discuss final Monday meeting (meeting November 25th)
- Yes
- No
  - Trillium & Pluto out this whole week
  - Trillium will also be out during next week's call (11/11)
James Ng out for 11/11 & 11/18 calls
- Available by slack & to work on ongoing PRs?
- YES

Recurring items:

New Items

Trillium

Answer to Nikhil's question: Fix Super Admin User Login issue #1802 (comment)
- Keeping in mind that we are aiming to deliver the User Permission Search Epic in 2-3 weeks at most (needs to be delivered before break, so complexity may need to be small in order to deliver on time).
- Nikhil prefers option #2 because it provides less friction, will be a relatively quick fix, and PD will be revamping the backend in the future anyways
  - Trillium responded to comment and provided next steps to Nikhil
Review of final User Permission Search Issue: Hook in APIs to filtered permissions data component #1801
- Okay as-is?
  - NO - needs some additional action items re: fixing remaining dummy data objects, values from James' PR
- Okay to move out of Icebox or should we wait until all other issues are complete / PRs are merged in User Permission Search Epic? If so, then assign issue.
  - NO - can only be complete after other issues in this Epic are complete first
- Review of PRs labeled as "time-sensitive"
- Current status = not reviewed. Trillium plans to take some time to review this week
  - Note, Angela's PR (update question and date picker #1804) is not related to User Permission Search, but is still time-sensitive.
  - Confirm with Angela that this PR is ready for review & update PR comment
    - Angela and Trillium to meet on November 5th to work on finalizing mobile view & PR. Once complete, this PR will be ready for review.

Vorleak

Confirm that search results should be based on dummy data: Create filtered permissions data component #1754 (comment)
- YES - search results based on dummy data
Vorleak / James - Discuss question for Trillium: Filtered permissions data comp #1808 (comment)
- Per Trillium - leave this PR as is, and fix page when hooking in APIs via Hook in APIs to filtered permissions data component #1801

Team

Time permitting - split up into breakout rooms

JH to discuss UI/UX and marketing work with Julia
JH to provide update on project.

Issue assignment cleanup:

PMs / Designers

Jack
Julia

Developers

Notes from meeting

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

Tasks

Jack to create an issue to Trillium re: creating a guide to create Git Command on VRMS wiki.
Trillium to meet with Angela to work on her PR
Trillium and Jack to meet to work on VRMS tasks together this week.

Items for next week's agenda

JackHaeg · 2024-11-19T02:47:52Z

[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)

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

FYI - last team meeting for the year (pending vote)
- Yes
- No
HfLA winter break will extend through December.
First meeting back will be on January 6th

Recurring items:

New Items

Trillium:

Is this issue complete? Change practice of building and deploying VRMS (with dev and prod) #1758
Progress on reviewing [the PRs labeled as “time-sensitive”](https://github.com/hackforla/VRMS/pulls?q=is%3Apr+is%3Aopen+label%3Atime-sensitive)
Finalize that last User Permission Search Issue ([Hook in APIs to filtered permissions data component #1801](Hook in APIs to filtered permissions data component #1801)) - discussed in next section
- Make sure that by not fixing the objects/properties on Hook in APIs to filtered permissions data component #1801 that we are okay on:
Possible to rebuild PROD with admin permissions feature and latest fixes to Dev or do we have to wait for super user fix?
Plan to unassign Bug: Users Cannot Check In #1411, anybody up for looking into this further?
Created this issue we discussed during last meeting. Ready for your review / revision. Document Git Commands for Pull Request Workflow and Add to VRMS Wiki #1814

Vorleak / Trillium:

Trillium - can you please confirm if this is okay? Filtered permissions data comp #1808 (comment)
Are you currently working on Hook in APIs to filtered permissions data component #1801?
- If so, need to change status to “in progress”
- Technically, this issue is not in the prioritized backlog as of yet, and Trillium also needs to review this issue to fix things up.
- Trillium, please take a look at this issue to make sure that it looks good to go AND please notes to make sure it is up to date
- Available to work on this in the coming weeks?

Nikhil:

Progress update / next steps with: Fix Super Admin User Login issue #1802

Nora:

Is there an active PR associated with this issue? Update HTML components to MUI: ./src/components/auth/HandleAuth.js #1640
Status of: Update HTML components to MUI: ./src/components/dashboard/AddTeamMember.js #1680

Angela:

Please follow up with DevOps re: Vrms client terraform migration incubator#29 (comment)
Re: add form validation for zoom google meet #1812 (comment)
- Relative links:
  - We should not allow relative links, as this does not align with best practices
  - BUT, we should probably provide users with a clear error message and examples if they input an incomplete link.
  - Discuss complexity with the team
  - e.g., “It looks like you have
- Subdomains:
  - I don’t believe HfLA will use Zoom meetings with subdomains like ucsd
  - Most links for HfLA are: https://us06web.zoom.us/j/……
  - I believe we should do the following:
    - Ensure link starts with https:// to ensure al links use HTTPS for security
    - Domain check: Verify that the domain ends with .zoom.us
    - Path Check: Ensure the path includes /j/

Evan:

Let’s close this issue as completed if already converted to MUI: Update HTML components to MUI: ./src/components/parts/form/ValidatedTextField.js #1705 (comment)
Already converted to MUI - okay to close? Update HTML components to MUI: ./src/components/parts/boxes/TitledBox.js #1707 (comment)

Breakout Rooms:

Julia:

Update from Jack on project -
Potentially close as completed: Finalize Project Status Designs #1678

Issue assignment cleanup:

PMs / Designers

Jack
Julia

Developers

Notes from meeting

Tasks

Items for next week's agenda

jbubar added the feature: Agenda label Jan 31, 2023

MattPereira changed the title ~~VRMS Agenda~~ All Teams: Meeting Agenda Monday 📝 Mar 7, 2023

MattPereira changed the title ~~All Teams: Meeting Agenda Monday 📝~~ ALL TEAMS: Monday Meeting Agenda 📝 Mar 13, 2023

ExperimentsInHonesty added role: Missing size: missing labels Jun 13, 2023

JackHaeg added role: Product size: 1pt and removed role: Missing size: missing labels Jun 23, 2023

ExperimentsInHonesty added the milestone: missing label Jul 4, 2023

ExperimentsInHonesty added the size: 0.5pt Can be done in 2-3 hours or less label Jul 13, 2023

JackHaeg mentioned this issue May 16, 2024

Remove old Meeting Agendas from Wiki #1636

Closed

4 tasks

JackHaeg self-assigned this May 21, 2024

JackHaeg added this to P: VRMS: Project Board Jun 13, 2024

JackHaeg moved this to General Information/Resources in P: VRMS: Project Board Jun 13, 2024

JackHaeg pinned this issue Jul 16, 2024

ExperimentsInHonesty mentioned this issue Oct 7, 2024

Fix VRMS redirect link without subdomain hackforla/incubator#70

Open

3 tasks

ExperimentsInHonesty mentioned this issue Oct 19, 2024

Epic: Marketing: VRMS hackforla/marketing#70

Open

17 tasks

jng34 unpinned this issue Nov 28, 2024

VRMS: ALL: Monday Meeting Agenda 📝 #1280

VRMS: ALL: Monday Meeting Agenda 📝 #1280

Comments

jbubar commented Jan 31, 2023 • edited by JackHaeg Loading

Overview

Old Team Meetings:

jbubar commented Jan 31, 2023 • edited Loading

Jan 30th:

Bonnie jumped on and brought up the following:

heyitsalexander commented Jan 31, 2023 • edited by ExperimentsInHonesty Loading

ExperimentsInHonesty commented Feb 4, 2023 • edited by heyitsalexander Loading

2023-02-06 Meeting Agenda and Notes

Prework to prep for meeting

Role Call (who is here)

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

Recurring items:

Notes from meeting

Tasks

Items for next week's agenda

AmandaGlover-PM commented Feb 7, 2023

2023-02-06 Meeting Agenda and Notes

Prework to prep for meeting

Role Call (who is here)

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

Recurring items:

Notes from meeting

Tasks

Items for next week's agenda

heyitsalexander commented Feb 9, 2023 • edited Loading

2023-02-13 Meeting Agenda and Notes

Prework to prep for meeting

Role Call (who is here)

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

Recurring items:

Resources for meeting

Notes from meeting

Tasks

Items for next week's agenda

ExperimentsInHonesty commented Feb 18, 2023

ExperimentsInHonesty commented Feb 18, 2023

heyitsalexander commented Feb 18, 2023

ExperimentsInHonesty commented Feb 25, 2023

heyitsalexander commented Feb 25, 2023 via email

AmandaGlover-PM commented Feb 28, 2023 • edited Loading

2023-02-27 Meeting Agenda and Notes

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

Recurring items:

Notes from meeting

Tasks

Items for next week's agenda

heyitsalexander commented Feb 28, 2023 • edited Loading

AmandaGlover-PM commented Mar 14, 2023 • edited Loading

2023-03-13 Meeting Agenda and Notes

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

Agenda items:

Notes from meeting

Tasks

Items for next week's agenda

jbubar commented May 23, 2023 • edited Loading

trillium commented May 23, 2023 • edited Loading

AmandaGlover-PM commented Jun 6, 2023 • edited Loading

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:

Notes from meeting

Items for next week's agenda

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

2023-06-12 Meeting Agenda and Notes

Role Call (who is here):

Agenda Items:

Notes from meeting

Items for next week's agenda

JackHaeg commented Jul 6, 2023

JackHaeg commented Jul 6, 2023 • edited Loading

2023-07-10 Meeting Agenda and Notes

Prework to prep for meeting

Role Call (who is here - add team names)

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

Recurring items:

New Items

jbubar commented Jan 31, 2023 •

edited by JackHaeg

Loading

jbubar commented Jan 31, 2023 •

edited

Loading

heyitsalexander commented Jan 31, 2023 •

edited by ExperimentsInHonesty

Loading

ExperimentsInHonesty commented Feb 4, 2023 •

edited by heyitsalexander

Loading

heyitsalexander commented Feb 9, 2023 •

edited

Loading

AmandaGlover-PM commented Feb 28, 2023 •

edited

Loading

heyitsalexander commented Feb 28, 2023 •

edited

Loading

AmandaGlover-PM commented Mar 14, 2023 •

edited

Loading

jbubar commented May 23, 2023 •

edited

Loading

trillium commented May 23, 2023 •

edited

Loading

AmandaGlover-PM commented Jun 6, 2023 •

edited

Loading

AmandaGlover-PM commented Jun 11, 2023 •

edited by jbubar

Loading

JackHaeg commented Jul 6, 2023 •

edited

Loading

JackHaeg commented May 7, 2024 •

edited

Loading

JackHaeg commented May 14, 2024 •

edited

Loading

JackHaeg commented May 21, 2024 •

edited

Loading

JackHaeg commented Jun 4, 2024 •

edited

Loading

JackHaeg commented Jun 11, 2024 •

edited

Loading

JackHaeg commented Jun 18, 2024 •

edited by chukalicious

Loading

JackHaeg commented Jun 25, 2024 •

edited

Loading