VRMS: ALL: Monday Meeting Agenda :memo:

hackforla / VRMS

Volunteer Relationship Management System: This is an ambitious project to create a system that will help us measure our human capital development, reduce repetitive tasks and processes, and improve outcomes.

GNU Affero General Public License v3.0

40 stars 78 forks source link

VRMS: ALL: Monday Meeting Agenda :memo: #1280

Open jbubar opened 1 year ago

jbubar commented 1 year ago

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: https://github.com/hackforla/VRMS/issues/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
- [ ] Bonnie
- [ ] Trillium
- [ ] Julia
- [ ] Josh
- [ ] Brad
- [ ] Evan
- [ ] Chandler
- [ ] Angela 
- [ ] Katiuska
- [ ] Nora 
- [ ] Nikhil
- [ ] Mudassir
- [ ] Sankshay
- [ ] Vorleak
- [ ] James

### 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: 
**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)
- [ ] [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)
- [ ] [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)

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

JackHaeg commented 5 months ago

2024-04-29 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here:

Role Call (who is here - add team names)

[x] Jack
[x] Trillium
[ ] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[x] Brad
[ ] Nayan
[x] Evan
[ ] Daniel
[ ] Jo
[x] Chandler

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

Recurring items:

New Items

[x] Trillium / Nayan - Has Nayan's environment issue been resolved?
[x] Trillium - Re: check in bug... able to fiddle with service workers & write/run tests? (Note - check in requirement)
[ ] Trillium & Team - review MUI issues, ensure that sufficient information has been added
[x] FYI - I will be moving all OLD agendas from the Wiki to a github issue that can be archived, which will help clean up our wiki pages.
[x] Brad - PR review, discuss comment: https://github.com/hackforla/VRMS/pull/1627#issuecomment-2083815587
[x] Chandler - any issues on hackforla/VRMS#1624 - team, can we approve this PR (#1631) to close this issue?
- FYI - I will be reviewing onboarding/offboarding issue templates from other teams and may create an updated version in the future.
[x] Jo - any issues/questions on hackforla/VRMS#1574?
- [x] Trillium - given that hackforla/VRMS#1576 has a merged pull request, can we close this issue? (looks like automation failed to close based on PR)
[x] Josh - Re: hackforla/VRMS#1538 - Do you plan to close as unplanned all remaining issues on the old board and then close this issue?

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

[x] hackforla/VRMS#1630
[x] hackforla/VRMS#1399
[x] hackforla/VRMS#1632

Trillium - if time permits (otherwise will discuss async)

[x] Are these issues related / should we consolidate?
- hackforla/incubator#70
- hackforla/VRMS#1377
  - Note that hackforla/VRMS#1377 may need a rewrite to specifically mention the issue with https://vrms.io/
  - Bonnie suggested testing with the next onboarding group if this is an issue

Issue assignment cleanup:

[x] Jack
[x] Trillium
[ ] Julia
[x] Josh
[ ] Rohan
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[x] Chandler

Notes from meeting

Julia unavailable due to scheduling conflict

Tasks

Items for next week's agenda

JackHaeg commented 5 months ago

2024-05-06 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] 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)

[x] Jack
[x] Trillium
[x] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[x] Brad
[x] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[x] Chandler

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

Recurring items:

New Items & Notes

[x] Trillium - any updates re: Check In Bug - fiddling with service workers & write/run tests?
- Trillium has been tagged in the comments of this issue - he will post there to provide updates on next steps
[x] Trillium Can we merge PR for hackforla/VRMS#1629 & close hackforla/VRMS#1628?
- Yes, just needs a review - Chandler plans to review this during this week, and we should be able to merge.
[x] Trillium - any updates on hackforla/VRMS#1497
- Trillium plans to go to the DevOps meeting this week to discuss this issue further.
[x] Nayan & Trillium: hackforla/VRMS#1633
- Note that I have added labels ("role: Dev Lead" okay?) - also I have assigned you two to this issue and moved it to "In Progress"
- If time allows, troubleshoot?
- Reassigning issues (e.g., MUI) while this is being fixed?
- No time to troubleshoot during the call. Nayan reported potentially having a fix in place, and will continue to work on it this week.
[x] Trillium / Evan / Nayan: Given that hackforla/VRMS#1551 is essentially complete:
- [x] Can we review/approve the associated PR and Execute Script (mentioned here :#1456)
- [x] Can we move hackforla/VRMS#1480 out of the icebox, add to Prioritized Backlog & potentially assign? Looks like this is the only issue remaining within this epic: hackforla/VRMS#1456. Then we can complete this epic entirely and move forward.
- [ ] Evan could be assigned to this issue now that 1551 is complete...
- Trillium & Josh plan to write up two new additional issues that will be linked to this epic and will need to be completed before hackforla/VRMS#1480 can be moved out of the icebox/completed. Josh & Trillium are tagged in this issue. Issue 1480 will remain in the icebox for now
[x] Jo - updates / questions related to hackforla/VRMS#1574? (e.g., mentioned logic to communicate to the backend)
- Jo reported having difficulty with this issue, so she swapped out to a new issue for this week and will return to this one when she has the time.
[x] Chandler - Answer question on assigned issue here
[x] Josh - check in on issue review process.
- Josh confirmed that he will review the remaining 10 issues this week and then close this issue.
[x] Brad / Trillium - Check in on PR hackforla/VRMS#1627. Just missing a review?
- YES - correct, just needs a review and then issue will be closed. Discussed with team about splitting up PRs across team members (not all must be completed by Trillium).

Split up into breakout rooms

[x] 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:

[x] Jack
[x] Trillium
[x] Julia
[x] Josh
[ ] Rohan
[x] Brad
[x] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[x] Chandler

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 commented 5 months ago

2024-05-13 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] 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
[x] Trillium
[x] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[x] Chandler

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

Recurring items:

New Items

[x] Trillium & Josh
- [x] check in on status of writing up additional issues for hackforla/VRMS#1456 so that we can unblock this epic.
- Trillium & Josh plan to meet this week to work on these issues.
- [x] Want me to follow up with Bonnie on questions listed on this issue: hackforla/VRMS#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
- [x] 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
[x] Josh:
- [x] 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
- [x] Noticed this issue: hackforla/VRMS#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 hackforla/VRMS#1099, hackforla/VRMS#1497, hackforla/incubator#70, 1544 & 1496
[x] Trillium
- [x] Check in on status of writing up comment next steps for Check In Bug.
- Plans to work on it this week.
- [x] DevOps meeting to discuss secrets?
- Josh will attend the meeting this week
- [x] 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).
[x] Team (PRs) - Revisiting reviewing PRs more regularly. (spend time during call to review / merge).
- [x] Trillium & Chandler - noticed that PR hackforla/VRMS#1629 was reviewed by Chandler last week and Brad approved these changes yesterday. Discussed how to streamline this process and how to merge changes.
- [x] Evan - requested status on his PR review: hackforla/VRMS#1622 (Looks like Josh is requested as reviewer). Looks to address hackforla/VRMS#1524. Reminder - team please pick from issues in the prioritized backlog.
- [x] Chandler - great work on submitting another PR: hackforla/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.
- [x] Brad - Great work on this PR: hackforla/VRMS#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
- [x] 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
[x] Jo - any new issues with hackforla/VRMS#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)
[x] Nayan - any updates on setting up environment?
- Nayan reported his dev environment started working again
[x] Assign hackforla/VRMS#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.
[x] Julia - to discuss project status specs

Issue assignment cleanup:

[x] Jack
[x] Trillium
[x] Julia
[x] Josh
[ ] Rohan
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[x] Chandler

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 4 months ago

2024-05-20 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

[x] Josh & Trillium:
- [x] Check in on DevOps MTG from last week - noticed updates on a few of these issues.
  - Incubator took over this one (used to be #1493 on our board): https://github.com/hackforla/incubator/issues/70
  - 1099
  - 1497
  - 1544
  - 1469
- [x] Bonnie mentioned during our Thursday planning call that we need to write up an issue to: 'stop publishing the Zoom links to each HfLA event in the API that the website consumes.' Gather additional insights / requirements from the team.
  - Brad agreed to create an issue addressing this concern
- [x] Rebuild Prod so that PM project edit fix is in place?
- [x] Reminder J&T: Write up 2 new issues for #1456
- [x] Reminder T: add comment with next steps to: #1411
[x] Nayan
- [x] Heard your dev environment started working again - can we close this issue? #1633
[x] #241 Review and discuss if sufficient info for prioritized backlog.
[x] Review/approve PRs & split up into breakout rooms
[x] Julia/Jack
- [x] Review Julia's final updates on project status.

Issue assignment cleanup:

[x] Jack
[x] Trillium
[x] Julia
[x] Josh
[ ] Rohan
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 4 months ago

2024-06-03 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Jack
[x] Trillium
[ ] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[x] Chandler
[x] Angela
[x] 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

Trillium:
- [x] New issues: #1646 & #1645
- [x] Updates on adding next steps to check in bug issue
- [x] Okay to open up MUI issue to team?
- [x] Provide assistance to Nayan on #1626
- [x] Can we move #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)
- [x] If we were to validate the Github Identifier (not a , would that simply be a requirement of:
Josh:
- [x] Previously, you mentioned wanting to create a an epic issue for all of the security issues. Based on: #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
- [x] #1456
Brad:
- [x] #1659
- Also plans to take a look at Merge Vite Branch PR for Trillium
Angela:
- [x] Any issues with #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:
- [x] Discussion of new PR: https://github.com/hackforla/VRMS/pull/1650
- Plans to review Trilliums latest feedback.

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela

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 commented 4 months ago

2024-06-10 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Jack
[x] Trillium
[ ] Julia
[ ] Josh
[x] Bonnie
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[x] Angela
[ ] Katiuska

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

[x] Conducting GitHub migration: #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.
[x] 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

[ ] Nayan (unable to attend)
- [ ] checking in on Dev environment / reassigning tasks if no response
- [x] Trillium - please provide assistance on #1626
- [x] Josh - please review Nayan’s PR(#1612) and see original issue (#1551)
[ ] Trillium & Josh:
- [x] #1456 reminder to add issues requested by Josh to this epic
- [x] #1469 reminder to potentially create epic out of this issue per Josh.
- [ ] Happy to add comments in the issue if helpful.
[x] Daniel - any updates on status? Will plan to reach out this week and off board.
[x] Kat - able to set up dev environment? Any questions?
[ ] Review rest of the team via Issue assignment cleanup below:

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[x] Angela
[ ] Katiuska

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 3 months ago

2024-06-17 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] 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
[x] Trillium
[x] Julia
[x] Josh
[x] Bonnie
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Jo
[ ] Chandler
[x] Angela
[ ] Katiuska
[x] Steph

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

[x] (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.
[x] Team updates on Daniel & Rohan, offboarding.
[x] Will be conducting a review of GitHub Project teams.
[x] New GitHub project board!
- [x] Discuss views
- [x] Note, any change to a project board view will be reflected across the team.
- [x] 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 #1674

Recurring items:

New Items

[x] Kat
- [x] Any issues with setting up dev environment?
[x] Trillium
- [x] re: Brad's comment:
- [x] Please add next step comment to: #1411
- [x] Vite: #1639 Team - need reviewers?
- [x] Confirm continued recruitment for back end dev. (will add to open roles board)
[ ] Nayan
- [ ] Any more issues with Dev Environment?
- [ ] #1626 - any questions with Trillium's feedback?
[x] Josh
- [x] tagged in comments.
[x] Brad
- [x] API issue checkin (see above) - team discussed and elected to make a new route.
[x] Angela
- [x] #1667
[x] Julia
- [x] Welcome back!
- [x] Discuss Project Status flows on Figma:
- [x] For team: is "View" vs. "Edit" mode of project status okay for the team?
- [x] Modal flows
- [ ] Replicating modal designs across all statuses (update to new "delete" modals).
- [ ] Potentially review project status with the team.

BREAKOUT ROOMS

[x] Bonnie
- [x] #1660 - Confirm that Google Drive URLs is complete (appears to be so).
- [x] #1669
- [x] Open roles next steps for onboarding tomorrow. Only recruiting one role: Mid level Back End Developer.
- [x] #1670
  - [x] Next steps for homework.
- [ ] Planning to also backup within comments & a new issue: (inactive) VRMS Research board
[x] Steph
- [x] Great job on the Git transition tasks last week!

Issue assignment cleanup:

[x] Jack
[x] Trillium
[ ] Julia
[x] Josh
[x] Brad
[ ] Nayan
[x] Evan
[ ] Jo
[x] Chandler
[ ] Angela
[ ] Katiuska

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 3 months ago

2024-06-24 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Jack
[x] Trillium
[x] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[x] Chandler
[x] Angela
[ ] Katiuska

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

[x] Last team call before August break
[x] Two new team members:
- [x] Nikhil Trehan
- [x] Nora Zajzon
[x] Intros, onboarding, and assign onboarding issues:
- [x] #1685 & #1686

Recurring items:

New Items:

Trillium / Josh
- [x] Meeting last Friday to review Vite PR, security issues.
- [x] Once Vite PR is merged, close security issues associated with React. Question re: React Wiki page.
- [x] Noticed Chelsey's post on Slack re: Removing the DNS record causing a conflict, asking Trillium / team to "Please verify that navigating to vrms.io works as expected: https://github.com/hackforla/incubator/issues/70
- [x] Respond to Slack / GitHub comment
- [x] Reminder re: volunteering opportunity for the VRMS Full Stack Developer Role
- [x] Merge PR: #1650
- [x] Note - moved #1637 epic and associated first issue to prioritized backlog to be worked on. (research issue at the moment).
[x] Josh - assigned to issue #1674 during last call - okay or reassign?

Breakout rooms (review Issue assignment cleanup below).

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela
[ ] Katiuska

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 2 months ago

2024-08-05

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Jack
[ ] Steph
[ ] Bonnie
[x] Trillium
[x] Julia
[ ] Josh
[ ] Brad
[ ] Nayan
[x] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela
[x] Katiuska
[ ] Nora
[x] Nikhil

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

[x] 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.
[x] 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)
[x] Processes update:
- [x] Devs to use issue cleanup on Monday calls
- [x] Splitting up PRs amongst team members (2 approved reviews before merging). Aim to improve turnaround time to feedback / merged work.
- [x] 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

[x] Good first issue: #1674
Trillium
- [x] Vite merge? (if so, review issues that can be dropped)
- [x] Meet to review board / discuss internship.
- [x] Discuss Nora's PRs: #1702 & #1688
- Is the request to create a new issue to track these changes?
- Appears that additional formatting issues were introduced with button padding - recommend fix prior to merging commit?
- FYI again - Nora will be unable to respond to comments on PRs.
- [x] Did Bonnie get everything she needed form the summer party? I believe this is the "PICNIC" event in Hack4LA on VRMS.
- [x] Delete event?
- [x] Reminder on https://hackforla.slack.com/archives/D05REU5583U/p1718719205896659
Evan
- Need any help on #1689?
Julia
- [ ] Should we just close this issue as it will be a part of Julia’s latest designs? https://github.com/hackforla/VRMS/issues/1101
- Ask during next call.
- [x] Review issue we created on June 20: https://github.com/hackforla/VRMS/issues/1678
- [x] Should this be labeled as “in progress” given that it is a draft?
- [x] Can share with the team, or just Trillium later this week
- [x] Prep for permissions / fields discussion (note that we have existing and also future needs).

Issue assignment cleanup:

PMs / Designers

[x] Jack
[ ] Steph
[x] Julia

Developers

[x] Trillium
[ ] Josh
[ ] Brad
[ ] Nayan
[x] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela
[x] Katiuska
[ ] Nora
[x] Nikhil

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 2 months ago

2024-08-12 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here: All issues have been labeled appropriately, plan to discuss icebox

Role Call (who is here - add team names)

[x] Jack
[ ] Steph
[x] Bonnie
[x] Trillium
[x] Julia
[ ] Josh
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora - ON BREAK until August 26
[x] Nikhil

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

[x] People Depot team joining the call (Sarah Monks, PhD and team). As they are continuing to work on the database fields and permissions architecture, looking to hear more about VRMS needs. People Depot will serve as new backend in the future. Their team is ready to start talking about what preliminary APIs we need in order to be able to feed the functions that already exist in VRMS.
- [x] Trillium to discuss a list of requirements
[ ] Potential intro/onboarding of new dev Mudassir Hussain
[x] Open Role posts - any requests? Last week's recruitment was packed.
[ ] Note on Issue drafts:
[x] Reminder - first Monday MTG of each month will be a planning call with only the leads (Trillium, Jack, Julia, etc.)
[ ] Angela (awlFCCamp) is on break until September.
Recurring items:

New Items

[x] #1603 - close as unplanned, or should we move it out of the icebox into the prioritized backlog (low priority) and have someone debug? If we keep this issue in the icebox, discuss dependency.
[x] #1718 - okay to close, Trillium?
[ ] Trillium - planning to merge Nora's PRs? Streamlining PR reviews (2 reviewer system)
[ ] Check in on MUI component issue

Breakout rooms

[ ] Trillium to work with Developers to review Issue assignment cleanup, assist with issues, and assign PRs
[ ] Jack & Julia to discuss & review Project Status finalization: #1678

Issue assignment cleanup:

PMs / Designers

[x] Jack
[ ] Steph
[x] Julia

Developers

[ ] Trillium
[ ] Josh
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora
[ ] Nikhil

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 1 month ago

2024-08-26 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here - all issues labelled appropriately, will review Icebox together

Role Call (who is here - add team names)

[x] Jack
[ ] Steph
[ ] Bonnie
[x] Trillium
[x] Julia
[x] Josh
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[x] Nora
[x] Nikhil

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

[x] No Monday meeting next week - due to Labor Day
[x] Reminder to provide screenshots on PRs whenever an edit to the website’s UI is made (e.g., MUI update issues should include screenshots).

Recurring items:

New Items

[x] Onboarding new dev Mudassir Hussain.

Trillium:

[x] Vite Merge - any issues since merging?
[x] Can we go ahead and close #1330?
[x] PR to approve (only added code of conduct feature): #1734
[x] Saw that this issue was moved back to the Icebox (HFLA Website URL validation): #1370. This is a confirmed requirement. Note that this is only requesting that the HfLA link is validated ONLY if a user makes an entry into the field. The field itself is not required in order to create/edit a project’s information.
[x] See note on Nikhil’s PR: #1725 - Do you agree we should switch to outlined buttons or are we good to go as-is?
[x] Continued recruitment for open roles… (any specific)

Julia

[x] Should we drop this issue as unplanned (the check in page will change once MUI updates are made): #1597
[x] Potentially review project status designs with team

Issue assignment cleanup:

PMs / Designers

[ ] Jack
[ ] Steph
[ ] Julia

Developers

[ ] Trillium
[ ] Josh
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora
[ ] Nikhil

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 1 month ago

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 commented 1 month ago

2024-09-09 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
[ ] Steph
[ ] Bonnie
[x] Trillium
[x] Julia
[ ] Josh
[ ] Brad
[ ] Nayan
[x] Evan
[ ] Daniel
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[x] Nora
[x] Nikhil
[x] Mudassir

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:

[x] #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 #1486 in greater depth to ensure that it aligns properly.
  - Trillium will also look at #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".
[x] #1729
- Discuss requirements. - Jack to work on finalize from Product perspective and send over to Trillium for final review
[x] Project Status Issue Epic - to be assigned after completing creation of the User Permission Fix.

PR Review:

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

Nora’s PR:

[x] #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
- [x] Okay for Nora to submit another PR? - YES

Evan/Trillium:

[ ] #1526
[x] Confirmed with stakeholder that this is a required field. That said, the error message needs to be updated. NEW Requirements: The field itself is required to be filled out in order to edit/create a new project AND it meet the criteria of being a Google Drive link.
- [x] Does this PR only validate the field? This field is NOT a required field at the moment, but we need to make it a required field.
- [x] Noticed a number of changes to other files (beyond Validating Google Drive).
- Next steps:
  - [ ] Merge as-is and create a new issue (make Google Drive URL a required field, and change error message) OR keep existing issue open with several new action items.
  - [ ] Delay to update error message & merge, and create new issue requiring Google Drive URL.
  - [x] Delay to update error message and change this to a required field. - Trillium to discuss with Evan. Plan to make these changes first prior to merge. Will update the Issue and tag Evan in the comment with updates on both the PR and the Issue itself
[x] Need to discuss Validation requirements.
- [ ] Is this epic required prior to implementing validation of project fields? https://github.com/hackforla/VRMS/issues/1481 If so, do you recommend prioritizing over any other validation issues? - Trillium to review in greater depth
- [x] RE: #1425 it appears that some of the linked issues were closed while others were left open.
  - Based on testing on Dev and PROD on 9.9.2024, it appears that only the “Description” field is validating correctly (max character limit of 250).
  - For all other impacted fields, (GitHub URL, Slack URL, Google Drive URL, HFLA Website URL), there does not appear to be any validation of the URLs… only the field is required to be filled in order to move ahead. ( #1367, #1368, #1369, #1370 #1363, #1402)
  - [ ] Is this fix LIVE on Dev/Prod currently? Perhaps testing was insufficient… - Trillium believes so, but needs to review further.
  - [x] Should we re-open #1367? It appears this field is still not validating correctly (it throws an error because this is a required field, but does not validate that it is a GitHub URL). - Again Trillium to review further. Jack and Trillium to discuss and potentially re-open
- [x] Review other validation requirements:
  - NEW:
    - Project Name: #1268
      - Can we utilize dynamic error messages or do we need to use Generic error message “Doesn’t fit criteria”
      - YES, we should be able to use dynamic error messages. Keep these.
    - GitHub Identifier (Change to NO required field, and verify field - i.e., GitHub ID)
    - Potentially GitHub URL (re-open issue) and Google Drive URL (required field & validation).

Trillium:

[ ] #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)
[x] 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.
[x] 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
[x] 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? #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.
[x] Mention migration to Terraform… do we need to create any new issues to get this launched? (per discussion at end of last week) https://github.com/hackforla/VRMS/issues/1497 - Trillium said he will attend the ops call and discuss with them further.

Julia:

[x] Review edits to screens together, along with final flow… #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.
[x] Potentially review Bonnie’s mock ups again and get any immediate feedback / work through changes. - Reviewed, plan to discuss

Issue assignment cleanup:

PMs / Designers

[ ] Jack
[ ] Steph
[ ] Julia

Developers

[ ] Trillium
[ ] Josh
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora
[ ] Nikhil
[ ] Mudassir

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 4 weeks ago

2024-09-16 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here.

Role Call (who is here - add team names)

[x] Jack
[ ] Steph
[ ] Bonnie
[ ] Trillium
[ ] Julia
[x] Josh
[x] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[x] Chandler
[x] Angela
[ ] Katiuska
[x] Nora
[x] Nikhil
[x] Mudassir

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

Trillium out sick today, Julia unable to join.

Recurring items:

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

New Items:

[x] Believe this issue is not complete - discuss reopening #1367

Nikhil & Team

[x] Discuss latest PR: #1746
- [x] Ensure that "But not the admin that promoted you" requirement is not included in this PR (both from front end & back end)
- [x] Explore potentially holding off on merging until #1486 & this PR is revised to include the addition of a "super" admin. (important first step to ensure we do not lose control of the system.) - Will merge these changes
- Requirements = we have one specific user (vrms-admin-perm@hackforla.org) that will be protected from all other admin users and will be locked from having its admin status changed. WHEN another admin user accesses this super admin's EditUser's page, THEN super admin's EditUser's page will be disabled from the other admins (other admins can see it, but cannot change it).
- [x] Discuss front end and back end implementation of these changes.
- [x] Request Josh to promote vrms-admin-perm@hackforla.org to admin as a first step. - DONE
- [x] New issue created here tracking Super Admin User: #1747
[x] Discuss updates to the User Permission Epic #1737. Nikhil working on backend perspective.
- [x] Latest mockups updated, let's create some first issues.
- [x] Addition of #1486 to the epic (can refine so this is the initial step).
[x] Evan - discuss PR mentioned last week - https://github.com/hackforla/VRMS/pull/1526
- Confirmed with stakeholder that this is a required field. That said, the error message needs to be updated. NEW Requirements: The field itself is required to be filled out in order to edit/create a new project AND it meet the criteria of being a Google Drive link.
- Plan = Delay to update error message and change this to a required field. - Trillium to discuss with Evan. Plan to make these changes first prior to merge. Will update the Issue and tag Evan in the comment with updates on both the PR and the Issue itself
[x] PR assignment / review with Brad / Josh.

Issue assignment cleanup:

PMs / Designers

[ ] Jack
[ ] Steph
[ ] Julia

Developers

[ ] Trillium
[ ] Josh
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora
[ ] Nikhil
[ ] Mudassir

Notes from meeting

Josh, Brad & team reviewed existing PRs
Assigned Mudassir good first issue.
Jack & Nikhil created new issue: #1747
- Discussed next steps on the epic & explored minor changes to Nikhil's latest PR #1746
- Nikhil to continue working on #1486 & #1747. May hand off other issues on the epic #1737 to Mudassir due to new work schedule.
  Tasks

Items for next week's agenda

JackHaeg commented 3 weeks ago

2024-09-23 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] 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
[ ] Steph
[ ] Bonnie
[x] Trillium
[ ] Julia
[x] Josh
[ ] Brad
[ ] Evan
[ ] Daniel
[x] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[x] Nora
[x] Nikhil
[ ] Mudassir

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

Recurring items:

New Items

[x] See new issues in #1737
- [x] #1751
- [x] #1752
- [x] #1753
- [x] #1754
[x] Evan - check in about Google Drive URL issue.
- Closed PR, Chandler plans to take a look at PR and continue working on issue. Unassigned and moved issue back to prioritized backlog.
- Plan to check with Chandler to see if they want to
[x] Noticed a ton of great PR reviews over the week - well done team! Specifically, saw that Nora, Brad, Trillium, others Trillium:
[x] Review new issues..
[x] Are there any PRs in the pipeline that will fix current issues with DEV and need to be fixed/merged prior to releasing any of these User Permission Management issue s to PROD
- [ ] E.g., we should be sure to have someone assigned to review this issue this week, as we will need to include this fix when we push the user permission logic to PROD later (will need to be included in the__ https://github.com/hackforla/VRMS/pull/1658)
[x] Let’s get it approved and merged: https://github.com/hackforla/VRMS/pull/1734 Nikhil:
[x] Did you get an answer on how to implement this issue? https://github.com/hackforla/VRMS/issues/1747
- Discussed with Trillium - going to add a new permission level in the database. Also provide some backend changes.
[x] Saw Commit on #1750 - nice work! I assume the other PR was closed as this one replaced it, correct? Team:
[x] Split up PRs.
[x] Nora working on updating PRs based on feedback from Josh/Trillium
[x] Chandler working on fixing merge conflicts with her PR

Issue assignment cleanup:

PMs / Designers

[x] Jack
[ ] Steph
[ ] Julia

Developers

[x] Trillium
[x] Josh
[ ] Brad
[ ] Evan
[ ] Daniel
[x] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[x] Nora
[x] Nikhil
[ ] Mudassir

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 2 weeks ago

2024-09-30 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Jack
[x] Bonnie
[x] Trillium
[ ] Julia
[x] Josh
[x] Brad
[ ] Evan
[ ] Chandler
[x] Angela
[ ] Katiuska
[ ] Nora - unavailable for 9/30 & 10/7 meetings
[ ] Nikhil
[x] Mudassir

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:

[x] 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)
- [x] At all related to Chandler's PR? #1658
- [x] #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.
[x] #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 (#1751, #1752, #1753, #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!
[x] #1474
- [x] Discuss next steps with Trillium & Josh. Not sure how this is related to #1322
[x] Should we close Nora's PR? #1748
- [x] Cleanup of other PRs

Josh & Trillium

[x] Is this issue up-to-date? #1456
[x] 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

[x] #1551
- Josh closed Nayan's PR #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

[x] Had a question for Trillium re: her PR: #1658
[x] "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

[x] Updates on Super Admin User issue?

Angela

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

Brad

[x] Update on #1659

Team:

[ ] PR cleanup / assignment.

Issue assignment cleanup:

PMs / Designers

[ ] Jack
[ ] Steph
[ ] Julia

Developers

[ ] Trillium
[ ] Josh
[ ] Brad
[ ] Evan
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora
[ ] Nikhil
[ ] Mudassir

Notes from meeting

Tasks

Items for next week's agenda

ExperimentsInHonesty commented 1 week ago

Add this to your next agenda https://github.com/hackforla/incubator/issues/70#issuecomment-2334754369

JackHaeg commented 1 week ago

2024-10-07 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Jack
[ ] Bonnie
[x] Trillium
[ ] Julia
[ ] Josh
[ ] Brad
[x] Evan
[ ] Chandler
[ ] Angela
[ ] Katiuska
[ ] Nora - unavailable for 9/30 & 10/7 meetings
[x] Nikhil
[ ] Mudassir

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

[ ] Posted new roles for PM & Full Stack Engineers.

Recurring items:

New Items

[x] #1772
- [x] Discuss spreadsheet / plan of work re: starting with PROD, ending with DEV check.
- [x] What are the database table names for VRMS?

Nikhil / Mudassir

[x] Trillium & I have finished up writing a number of issues for #1737.
- [x] Please take a look and complete issues in order. Note that the following are all backend issues:
- 1770
- 1769
- 1771
- 1751 is a front end issue, and is also available to review

Nikhil

[x] re: #1765
- [x] Can we remove the promoted super user admin "mamoleo@gmail.com" after finalizing testing on this PR? Want to ensure that only vrms-admin-perm@hackforla.org is super admin user on VRMS. Assume this user is only a super admin user on Dev, correct?
[x] Still actively working on In Progress issues, or place back in "Prioritized Backlog"?

Trillium

[x] Is this issue fixed - if so, let's close as complete? https://github.com/hackforla/incubator/issues/70#issuecomment-2334754369
[x] Progress on: https://github.com/hackforla/VRMS/issues/1767
- [x] Need to bring in any assistance to resolve?
- [x] Once this issue is fixed, how do we plan on rebuilding PROD? Recommend testing DEV rebuild fully first for all existing functionality prior to rebuild of PROD
- [x] Also, do we plan to do a rebuild with all existing functionality first prior to rebuilding with new features (e.g., MUI changes, User Permission Search, and more).
[x] Want to check in on: https://github.com/hackforla/VRMS/issues/1758
- [x] Does this issue require additional information to be complete? Should status be updated to "In Progress"?
- Yes, requires additional information to be drafted more, likely based on the outcome of #1767
[x] Check in bug still ongoing and observed last week (meetings unavailable to check in, displayed duplicate times). Additional help from team? (note prioritization)
[x] #1497
- [x] Updates? Request updates from Chelsey directly in comments?
- RESPONSE: Yes, all updates should be from Chelsey. This is Chelsey's expertise, not Trillium's
[x] Do we need to update the tech stack on this page given shift to Vite?: https://github.com/hackforla/VRMS/wiki/Technology
- Yes, updated page with Vite and MUI links on front end tech stack

Angela

[ ] Can you please post a link to the list of AWS services found on #1474? Past in this "Development" Google Drive folder: https://drive.google.com/drive/u/3/folders/1m4pS3kidCY2VrcNQWhtpLThSKQSplkax
[ ] Any issues so far with: https://github.com/hackforla/VRMS/issues/1484

Julia

[ ] Closing this issue or keep open and place in icebox until MUI changes are complete? #1597
[ ] Closing #1678
[ ] Potential cleanup / refinement of old UI/UX issues on the project board.

Full Team

[x] Review & assign PRs.

Issue assignment cleanup:

PMs / Designers

[x] Jack
[ ] Steph
[ ] Julia

Developers

[x] Trillium
[ ] Josh
[ ] Brad
[x] Evan
[ ] Chandler
[ ] Angela - ON BREAK until September
[ ] Katiuska
[ ] Nora
[x] Nikhil
[ ] Mudassir

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 commented 3 hours ago

2024-10-14 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here

Role Call (who is here - add team names)

[x] Jack
[ ] Bonnie
[x] Trillium
[ ] Julia
[ ] Josh
[ ] Brad
[ ] Evan
[ ] Chandler
[x] Angela
[ ] Katiuska
[x] Nora - unavailable for 9/30 & 10/7 meetings
[x] Nikhil
[ ] Mudassir
[x] Vorleak Yek
[x] James Ng
[x] Sankshay Pusa
[ ] Imthiaz Hussain

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

[x] New devs joining the team / introductions.
[x] Onboarding

Recurring items:

New Items

[x] New/final issues written for https://github.com/hackforla/VRMS/issues/1737
[x] Review Nikhil's research API comment: https://github.com/hackforla/VRMS/issues/1769#issuecomment-2409132400
[x] Discuss next steps for following issue and splitting up Epic issues
[ ] Chandler - if you are looking for an issue, this may be a good one to check out: https://github.com/hackforla/VRMS/issues/1729
[x] Review of existing PRs, specifically:
- [ ] Nikhil: #1774
- [ ] Nikhil: #1765
- [ ] Angela: #1789
- [x] next steps on associated epic?
[x] Reminder to the team to continually review & assign PRs Angela
[x] Can you please post a link to the list of AWS services found on #1474? Past in this "Development" Google Drive folder: https://drive.google.com/drive/u/3/folders/1m4pS3kidCY2VrcNQWhtpLThSKQSplkax

Julia

[ ] Closing this issue or keep open and place in icebox until MUI changes are complete? #1597
[ ] Closing #1678
[ ] Potential cleanup / refinement of old UI/UX issues on the project board.

Issue assignment cleanup:

PMs / Designers

[x] Jack
[ ] Julia

Developers

[x] Trillium
[ ] Josh
[ ] Brad
[ ] Evan
[ ] Chandler
[x] Angela - ON BREAK until September
[ ] Katiuska
[x] Nora
[x] Nikhil
[ ] Mudassir

Notes from meeting

Tasks

[ ] Onboard new team members
[ ] Allocate good first issues for new members

hackforla / VRMS

VRMS: ALL: Monday Meeting Agenda :memo: #1280

Overview

Old Team Meetings:

2024-04-29 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

Notes from meeting

Tasks

Items for next week's agenda

2024-05-06 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 & Notes

Notes from meeting

Tasks

Items for next week's agenda

2024-05-13 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

Notes from meeting

Tasks

Items for next week's agenda

2024-05-20 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

1099

1497

1544

1469

Notes from meeting

Tasks

Items for next week's agenda

2024-06-03 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

Notes from meeting

Tasks

Items for next week's agenda

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

Notes from meeting

Tasks

Items for next week's agenda

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

Notes from meeting

Tasks

Items for next week's agenda

2024-06-24 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:

Notes from meeting

Tasks

Items for next week's agenda