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

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

### Recurring items: 

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

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

**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)
- [ ] [Nayan](https://github.com/hackforla/VRMS/issues/assigned/freaky4wrld)
- [ ] [Evan](https://github.com/hackforla/VRMS/issues/assigned/evanyang1)
- [ ] [Daniel](https://github.com/hackforla/VRMS/issues/assigned/danieldkim42)
- [ ] [Jo](https://github.com/hackforla/VRMS/issues/assigned/josiehandeveloper)
- [ ] [Chandler](https://github.com/hackforla/VRMS/issues/assigned/lcchrty)
- [ ] [Angela](https://github.com/hackforla/VRMS/issues/assigned/awlfccamp)
- [ ] [Katiuska](https://github.com/hackforla/VRMS/issues/assigned/chukalicious)

### Notes from meeting

### Tasks

### Items for next week's agenda

Old Team Meetings:

Previous Team Meeting Agendas (from 2022) that were previously stored on the VRMS Wiki have been preserved in this issue.

jbubar commented 1 year ago

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 https://github.com/hackforla/VRMS/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 https://github.com/hackforla/VRMS/issues/1274 This page needs updating: https://www.hackforla.org/projects/vrms it looks like you opened a change request but it needs refining https://github.com/hackforla/website/issues/3694

heyitsalexander commented 1 year ago

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

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

Tasks

[ ] Reach out to PMs of different projects (https://docs.google.com/spreadsheets/d/1ZSyCkO3XgD19EzmpLPkmz196vpwNnjjNMZZqXUV8Wqw/edit#gid=0)
[ ] Prepare deck to show how to use VRMS
[ ] Schedule "Lunch n' Learn" for Feb 13
[ ] Usabiity testing with Bonnie Feb 13 -

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

Items for next week's agenda

AmandaGlover-PM commented 1 year ago

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 david@grubbylogic.com and add him to project Testy Test. After you finish, return to the “User Management” screen and stop there. Last Task: David Rubinstein just emailed you that he cannot be on project Testy Test. So, remove him from this project. After you finish, return to the “User Management” screen and stop there. Matt's Feedback: Personal preference to have less total clicking on the page with the identifiers once he saves something, he would rather have confirmation that it was saved without having to click out of that screen; forms look good, inputs are solid. Haven't seen a logout that is in parenthesis versus a button. When adding someone to VRMS he would prefer it to say submit versus save.

Tasks

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

Items for next week's agenda

heyitsalexander commented 1 year ago

2023-02-13 Meeting Agenda and Notes

Prework to prep for meeting

[x] Judy's prototype reviewed and usability testing script

Role Call (who is here)

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

[x] Lunch n' Learn Deck ready
[x] New dev joining VRMS

Recurring items:

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

Resources for meeting

Notes from meeting

Tasks

[ ] Ask for permission to record
[ ] Usability testing with Bonnie part 2
[ ] Post test survey
[ ] UX researcher responsbilities?

Items for next week's agenda

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

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

ExperimentsInHonesty commented 1 year ago

@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 commented 1 year ago

@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 commented 1 year ago

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

ExperimentsInHonesty commented 1 year ago

@heyitsalexander I dont see that you made the logo change yet. See https://github.com/hackforla/VRMS/issues/1280#issuecomment-1435727213. 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 commented 1 year ago

Sounds good. Working on the logo

Get Outlook for iOShttps://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)

@heyitsalexanderhttps://github.com/heyitsalexander I dont see that you made the logo change yet. See hackforla/VRMS#1280 (comment)https://github.com/hackforla/VRMS/issues/1280#issuecomment-1435727213. I will want to review/revise the Lunch n' Learn deck VRMS - How to Add/Edit Meeting Times slideshttps://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 GitHubhttps://github.com/hackforla/VRMS/issues/1280#issuecomment-1445165772, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJLJ3Y357OAA376OQMDEDFDWZI7I3ANCNFSM6AAAAAAUL45B4Q. You are receiving this because you were mentioned.Message ID: @.***>

AmandaGlover-PM commented 1 year ago

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

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

From: @MattPereira (https://github.com/hackforla/VRMS/issues/1241#issuecomment-1447144043)

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

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 hackforla/VRMS#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 commented 1 year ago

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

Spiteless commented 1 year ago

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

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
- [X] API documentation: change this to integrating with other apps
- [X] 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 commented 1 year ago

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

Moving these items to Product Agenda:

[ ] review any issues that are in the new issue approval column for
- [ ] UX Writing
- [ ] [Product] - that are related to writing
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Zoe

JackHaeg commented 1 year ago

2023-07-10 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.) - All open issues have remained relatively static across labels since July 3 (with the exception of milestones improving)

Role Call (who is here - add team names)

Evan, Trillium, Josh, Jack, Stephanie, Julia (all VRMS team members).

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

VRMS check in feature not working for tonight's onboarding.

Recurring items:

New Items

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

[ ] BW: What is the role makeup of the dev team? (how many front end, back end, full stack, dev ops)
[ ] JH: Let's review hackforla/VRMS#1225 it has a closed PR with it and there are comments after that PR was closed.
[ ] BW: Issue assignment cleanup:
- [ ] Trillium
- [x] Micah
- [ ] Brad
- [ ] Evan
- [ ] Josh
- [x] Julia
- [x] Jack

Notes from meeting

Dev team used the meeting time to explore the VRMS check-in issue described here hackforla/VRMS#1411
Julia, Jack, Steph discussed existing open issue questions, design handoff, board cleanup.

Tasks

Devs to continue to work on VRMS check in.
Initiate regular testing of VRMS prior to onboard sessions on a weekly basis.

Items for next week's agenda

Revisit open issues, BW questions mentioned above, & design questions with developers during next team meeting.
Explore potential fix to VRMS issue & testing.

JackHaeg commented 12 months ago

2023-07-24 Meeting Agenda and Notes

Prework to prep for meeting

[ ] Review the QA
[ ] Perform Label Audit and add summary here ("milestone" labels improved, working on additional improvements to "size" and "feature" labels)

Role Call (who is here - add team names)

Trillium, Rohan, Steph, Julia, Jack, Josh, Bonnie

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

Recurring items:

New Items

[x] JH: Update on latest bug fix: hackforla/VRMS#1411
[ ] JH: Devs to discuss if time permits: hackforla/VRMS#1324
[x] BW: What is the role makeup of the dev team? (how many front end, back end, full stack, dev ops)
[x] JH: Ask Josh / Evan to write issues based on mock up needs for Julia
[ ] JH: Request Evan comment & move all issues that are fixed by his recent PR to Final QA.
[x] Issue assignment cleanup:
- [ ] Trillium
- [ ] Micah
- [ ] Brad
- [ ] Evan
- [ ] Josh
- [ ] Julia
- [ ] Jack

Notes from meeting

New PM joined the team, Rohan Vaidya.
Onboarded Rohan
Reviewed issues with Dev lead
According to Trillium, need new backend and full stack devs if possible

Tasks

Items for next week's agenda

Continue backlog grooming,
Review check-in fix

jbubar commented 11 months ago

I would love to discuss this pr next meeting https://github.com/hackforla/VRMS/pull/1401

JackHaeg commented 11 months ago

2023-07-31 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)

Josh, Bonnie, Evan, Jack, Trillium, Steph

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

Recurring items:

New Items

JH: Discuss hackforla/VRMS#1425
JB: Discuss hackforla/VRMS#1401
JH: What should we do with: hackforla/VRMS#1376
JB: Explore meeting time organization with Devs, Lead Dev to review all PRs before Monday meeting

Issue assignment cleanup:

[ ] Trillium
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Josh
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Discussed how devs organize time during meetings.
Reviewed PM tasks with Steph

Tasks

Items for next week's agenda

JackHaeg commented 11 months ago

2023-08-07 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] Trillium
[x] Josh
[ ] Micah
[x] Brad
[x] Evan
[x] Julia
[x] Jack
[x] Steph
[x] Rohan
[x] Bonnie
[x] Andrew Lin (potential new PM who sat in on meeting)

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

Recurring items:

New Items

JH/JG: Discuss meeting times
JH: Discuss feature label (added "login" feature label) and check in on: hackforla/VRMS#1458
JH: Can we check in on this: hackforla/VRMS#1387
JH: Can we discuss hackforla/VRMS#1177 with Bonnie if she is in attendance?
JH/Brad: Is this still an active issue? hackforla/VRMS#1424
JH/Bonnie: To discuss hackforla/VRMS#1086
Discuss hackforla/VRMS#1425
JB: Discuss hackforla/VRMS#1401
JH: What should we do with: hackforla/VRMS#1376
JB: Explore meeting time organization with Devs, Lead Dev to review all PRs before Monday meeting

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Discussed 1 PR per ticket requirement,
Devs discussed security issue, exploring next steps.
Potential to move meeting to Tuesdays at 6pm, Pacific depending on a vote
Worked on adding milestones, board clean up.
Explored division of work between PMs while Jack is away for the next 2 weeks.

Tasks

Items for next week's agenda

JackHaeg commented 11 months ago

2023-08-14 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] Trillium
[x] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

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

JH: Discuss hackforla/VRMS#1376 (Please reword this to explain that it is the check in time that has the wrong start and end time. The original meeting time is fine.
Discuss security issue...
Error message on the edit meeting screen saying "Event name cannot contain 'meeting' or 'mtg' or the project name"

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

vaidyarohan commented 11 months ago

2023-08-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)

[x] Trillium
[x] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[x] Julia
[ ] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

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

Discuss the progress in the security issue https://github.com/hackforla/VRMS/issues/1469#issue-1852285268 (environment secrets page)
Unable to change meeting name. (Close the issue?) https://github.com/hackforla/VRMS/issues/1466#issue-1850809443

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

Steph112792 commented 10 months ago

8/28/2023 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)

[x] Trillium
[x] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[x] Julia
[ ] Jack
[x] Steph
[ ] Rohan

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

Recurring items:

New Items

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

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

Update WIKI
-Organize and Maintain Kanban board so that it is CLEAR
Julioa has ideas that she will share next week.

JackHaeg commented 10 months ago

2023-09-07 PLANNING Meeting Agenda and Notes

Role Call (who is here - add team names)

[x] Trillium
[ ] Josh
[x] Julia
[x] Jack
[ ] Steph
[ ] Rohan

Issues to discuss:

Provided Karen with video overview on how to add/remove PMs from a project, also added new PM and provided support for Lucky Parking
Discuss hackforla/VRMS#1504 - issue mentioned by Bonnie in VRMS Slack (see image):
Discuss Start time selection, duration as mentioned by Bonnie. See new issue here: hackforla/VRMS#1508

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 10 months ago

2023-09-11 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] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[x] Evan
[x] Julia
[x] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

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

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 10 months ago

2023-09-18 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] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[x] Evan
[x] Stephen
[x] Julia
[x] Jack
[ ] Steph
[x] Rohan

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

Recurring items:

New Items

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

Issue assignment cleanup:

[x] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[x] Evan
[ ] Stephen
[x] Julia
[x] Jack
[ ] Steph
[x] Rohan

Notes from meeting

Discussed User Access levels with Bonnie (in increasing level of permissions):
- Prospective member
- Member of the organization but not member of team
- Team member
- Jr. Practice lead (jr. Design lead, would get jr of whatever the practice is).
- PM (multiple product managers all get leader / admin access)
- Brigade Admin
- VRMS admin
- Admin of the whole product
Reviewed and added issues to prioritized backlog
Updates on bug fix ongoing
Reviewed design issues
Assigned PM issues

Tasks

Items for next week's agenda

Must Ask Questions for Bonnie on next call

Trillium: Upgrade dependencies?
- Perspective on changing build systems so that we can use modern versions of React
- Application can currently be built and deployed using Vite using current GitHub actions
- Jobs?

Steph112792 commented 9 months ago

2023-09-25 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] Trillium
[ ] Josh
[ ] Micah
[x] Brad
[x] Evan
[ ] Stephen
[ ] Julia
[x] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

[x] Discuss Trillium's points below with Bonnie:
- Perspective on changing build systems so that we can use modern versions of React
- Application can currently be built and deployed using Vite using current GitHub actions
- Jobs?
[x] Agree on Slack channels to keep / delete / archive below:

Slack Channels	Responsible	Status	Public or private	Last Message Date
vrms-ops	vrms	Dormant	public	2020-11-10
vrms-ui	vrms	Dormant	public	2021-01-16
vrms-test	vrms	Dormant	public	2021-06-11
vrms-devs	vrms	Dormant	public	2021-07-08
vrms-tech	vrms	Active	private	2023-08-07
vrms	vrms	Active	public	2023-09-11
vrms-design	vrms	Dormant	public	2023-02-02

Maybe change VRMS-tech to VRMS-security to keep one of these channels as private (for discussing security issues, private info, etc.) Discuss with Trillium

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Stephen
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

Trillium - How to change AWS secrets? Not sure if we can change our secrets, or if we need to put them into some environment elsewhere. Usually, AWS will have a place. Probably some secrets for VRMS, one of them is JWT secret that we use to sign Javascript web tokens (email is signed by our secret). Need to change this secret to make it more secure.

JackHaeg commented 9 months ago

2023-10-02 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)

[x] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Stephen
[x] Julia
[ ] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

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

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Stephen
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 9 months ago

2023-10-09 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.)
- Milestones improved significantly last week and are almost completed. Next step is "features" and "size"

Role Call (who is here - add team names)

[x] Trillium
[ ] Josh
[ ] Micah
[x] Brad
[x] Evan
[ ] Stephen
[x] Julia
[x] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

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

Discuss recruiting new devs with Trillium / Bonnie
Check in with Trillium about AWS secrets - did he reach out to the Ops CoP for more info? Perhaps Josh can provide additional input?
Is this still an issue - moved from Prioritized backlog to Questions/Review? https://github.com/hackforla/VRMS/issues/1424
Discuss with Julia https://github.com/hackforla/VRMS/issues/1151

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Stephen
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 9 months ago

2023-10-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] Trillium
[x] Josh
[ ] Micah
[x] Brad
[ ] Evan
[ ] Stephen
[x] Julia
[x] Jack
[x] Steph
[x] Rohan

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

Recurring items:

New Items

Bonnie: Review issue mentioned by Bonnie (part of a larger check in bug that is being addressed in other issues, should we delete this issue?): https://github.com/hackforla/VRMS/issues/1530
Trillium / Josh: Missing milestone review for issues: https://github.com/hackforla/VRMS/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone
Josh & Trillium: Review https://github.com/hackforla/VRMS/issues?q=is%3Aopen+is%3Aissue+-project%3Ahackforla%2Fvrms%2F12+
Josh/Trillium Is this still an issue? Moved from Prioritized backlog to Questions/Review? https://github.com/hackforla/VRMS/issues/1424
Bonnie: New issues created re: stakeholder feedback:
- Project Status definitions: https://github.com/hackforla/VRMS/issues/1532
- UAL from project details: https://github.com/hackforla/VRMS/issues/1534
- Cadence definitions: https://github.com/hackforla/VRMS/issues/1533
Bonnie: Mentioned that feature labels are confused. Discuss how to clean these up

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Stephen
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

Notes from meeting

Tasks

[ ] Josh will review old issues over the next week: https://github.com/hackforla/VRMS/issues?q=is:open+is:issue+-project:hackforla/vrms/12+
[x] Josh / Trillium reviewed & merged one of the PR's. Many of the remaining PR's are dependabot PR's, which will be resolved with a coming dependency update by Trillium.
[x] We will plan to close this issue as it is related to the larger check-in bug and duplicates the same behavior: https://github.com/hackforla/VRMS/issues/1530
[x] Jack - Added available back end and front end roles for VRMS here, as we are actively recruiting additional developers: https://github.com/hackforla/engineering/projects/2

Items for next week's agenda

JackHaeg commented 8 months ago

2023-10-30 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here: All issues are complete, with the exception of the size label (see here: https://github.com/hackforla/VRMS/issues?q=is%3Aopen+is%3Aissue+label%3A%22size%3A+missing%22)

Role Call (who is here - add team names)

[x] Trillium
[x] Josh
[ ] Micah
[x] Brad
[ ] Evan
[ ] Stephen
[x] Julia
[x] Jack
[x] Steph
[x] Rohan
[x] Nayan

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

Recurring items:

New Items:

[x] Check in with Josh on reviewing old open issues - happy to create an issue to track progress: https://github.com/hackforla/VRMS/issues?q=is:open+is:issue+-project:hackforla/vrms/12+
[x] Discuss check in bug progress with Trillium / Josh: hackforla/VRMS#1411 and hackforla/VRMS#1376
[x] Trillium - check in on PRs, split up between devs: https://github.com/hackforla/VRMS/pulls
[x] Trillium / Josh - can we add size labels to these last few remaining issues? https://github.com/hackforla/VRMS/issues?q=is%3Aopen+is%3Aissue+label%3A%22size%3A+missing%22
[x] Julia - discuss cadence issue and screens with Bonnie: https://github.com/hackforla/VRMS/issues/1533
[x] Julia - discuss open "in progress" issues, move accordingly.
[ ] Bonnie - discuss feature labels: https://docs.google.com/spreadsheets/d/14fd47047A42vycujTc03MeahFZyHHqM2ke-B3VaqH4w/edit#gid=0 and https://github.com/hackforla/VRMS/issues/1537

Issue assignment cleanup:

[x] Trillium
[x] Josh
[ ] Micah
[x] Brad
[ ] Evan
[ ] Stephen
[x] Julia
[x] Jack
[x] Steph
[x] Rohan
[x] Nayan

Notes from meeting

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

Tasks

Items for next week's agenda

JackHaeg commented 8 months ago

2023-11-13 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[x] Trillium
[x] Josh
[x] Nayan
[ ] Micah
[x] Brad
[ ] Evan
[ ] Stephen
[x] Julia
[ ] Jack
[x] Steph
[x] Rohan

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

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

New Items

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

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Nayan
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan
[ ] Micah
[ ] Stephen

Notes from meeting

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

Tasks

Items for next week's agenda

JackHaeg commented 8 months ago

2023-11-20 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

[ ] Trillium
[ ] Josh
[ ] Nayan
[ ] Micah
[ ] Brad
[ ] Evan
[ ] Stephen
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan

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

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

Recurring items:

New Items

[x] Julia: Present any new, relevant screens & clarify additional specs with Bonnie (recommend clarifying specs with Bonnie in a Breakout room to make best use of time)
- hackforla/VRMS#1545
- hackforla/VRMS#1546
[ ] Trillium: check in on bug issue progress, explore next steps with team: https://github.com/hackforla/VRMS/issues/1411
[ ] Trillium - check in on any relevant PRs, split up between devs: https://github.com/hackforla/VRMS/pulls
[ ] Trillium / Josh - assign prioritized issues amongst devs.
[ ] Bonnie / Josh - Issues Josh requested review from Bonnie to see if still relevant:
- https://github.com/hackforla/VRMS/issues/146#issuecomment-1797602578
- https://github.com/hackforla/VRMS/issues/1045#issuecomment-1797332218
[ ] Josh / Bonnie - Should we move this issue from icebox and add the info to the wiki, given that the task described is continuous and keeping such information on the wiki for future team members could be helpful? https://github.com/hackforla/VRMS/issues/1132
[x] Julia - should we work on this together? Maybe scope out some flows together to discuss how this would work along with Bonnie? https://github.com/hackforla/VRMS/issues/1397
[x] Julia - should we close this issue? https://github.com/hackforla/VRMS/issues/10
[ ] Bonnie - a while back, we discussed this Google Drive Migration issue. I believe you mentioned having an email template / some additional info (happy to discuss at next planning call). https://github.com/hackforla/VRMS/issues/1177

Issue assignment cleanup:

[x] Trillium
[x] Josh
[ ] Nayan
[ ] Brad
[ ] Evan
[x] Julia
[ ] Jack
[ ] Steph
[x] Rohan
[ ] Micah
[ ] Stephen

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 7 months ago

2023-11-27 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 labelled appropriately.

Role Call (who is here - add team names)

[x] Trillium
[x] Josh
[ ] Nayan
[ ] Micah
[ ] Brad
[x] Evan
[ ] Stephen
[ ] Julia
[ ] Jack
[ ] Steph
[x] Rohan

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

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

Recurring items:

New Items

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

Issues that were not checked off from the last call:

[ ] Bonnie / Josh - Issues Josh requested review from Bonnie to see if still relevant:
- https://github.com/hackforla/VRMS/issues/146#issuecomment-1797602578
- https://github.com/hackforla/VRMS/issues/1045#issuecomment-1797332218
[ ] Bonnie - a while back, we discussed this Google Drive Migration issue. I believe you mentioned having an email template / some additional info (happy to discuss at next planning call). https://github.com/hackforla/VRMS/issues/1177

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Nayan
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan
[ ] Micah
[ ] Stephen

Notes from meeting

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

Tasks

Items for next week's agenda

JackHaeg commented 6 months ago

2024-01-22 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] Trillium
[x] Josh
[x] Nayan
[ ] Brad
[x] Evan
[ ] Stephen
[x] Julia
[x] Jack
[ ] Steph
[x] Rohan

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

Recurring items:

New Items

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

Issue assignment cleanup:

[x] Trillium
[x] Josh
[x] Nayan
[ ] Brad
[ ] Evan
[x] Julia
[x] Jack
[ ] Steph
[x] Rohan
[ ] Stephen

Notes from meeting:

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

Tasks

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

Items for next week's agenda

JackHaeg commented 5 months ago

2024-01-29 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] Trillium
[ ] Josh
[x] Nayan
[x] Evan
[x] Daniel
[ ] Brad
[ ] Stephen
[x] Julia
[x] Jack
[x] Rohan

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

Recurring items:

New Items

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Nayan
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan
[ ] Stephen

Notes from meeting

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

Tasks

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

Items for next week's agenda

JackHaeg commented 5 months ago

2024-02-05 Meeting Agenda and Notes

Prework to prep for meeting

[ ] 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] Trillium
[x] Josh
[ ] Nayan
[ ] Brad
[ ] Evan
[ ] Stephen
[x] Julia
[x] Jack
[ ] Steph
[ ] Rohan
[x] Daniel Kim

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

Recurring items:

New Items

[x] Discuss (see comments) hackforla/VRMS#1566
[x] Check in on progress of: hackforla/VRMS#1538
[x] Remind team of these PRs: hackforla/VRMS#1497
[x] Check in on progress of: hackforla/VRMS#1411

Issue assignment cleanup:

[ ] Trillium
[ ] Josh
[ ] Nayan
[ ] Brad
[ ] Evan
[ ] Julia
[ ] Jack
[ ] Steph
[ ] Rohan
[ ] Stephen

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 5 months ago

2024-02-11 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

[x] Check in with new team members.
[x] Discuss Check in bug hackforla/VRMS#1411.
- Is this implemented on PROD?
  
  Currently, it looks like check ins are not matching up

The issue will be reopened based on the ongoing bug, see notes below
[x] Why do we have "Google Drive ID" included as a field on both dev & prod? Created a new issue to comment out this field as well, but perhaps it should be deleted altogether:
- hackforla/VRMS#1584
- This was addressed during the call and will be commented out.
[x] Should "Google Drive URL" be a required field? Looks like there are currently projects stored on VRMS that do not have a Google Drive URL available. Created a new issue to remove the validation requirement
- hackforla/VRMS#1585
- Not a required field, validation will be removed
[x] Before deploying Dev to Prod, it would be great if we could address the following:
- hackforla/VRMS#1576
- hackforla/VRMS#1574
- These are more cosmetic, as long as edits ARE saving on dev and the following issues are complete, we could deploy hackforla/VRMS#1584 & hackforla/VRMS#1585
- Then we can also close: hackforla/VRMS#1566
- Team agreed with this approach

Issue assignment cleanup:

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

Notes from meeting

Discussed ongoing issues with check-in bug, which is displaying events scheduled for the following day (Tuesday), with the only exception being the "Onboarding" event. Given that this is still occurring, the hackforla/VRMS#1411 has been re-opened.
Onboarded new team member, Jo who will set up environment over next week
Trillium & Daniel worked to fix hackforla/VRMS#1584 & hackforla/VRMS#1585 during the call
- PRs will be reviewed & merged accordingly once merge conflicts are refined
Josh has an interview and is leaving early, will (GOOD LUCK!!!)

Tasks

Items for next week's agenda

JackHaeg commented 4 months ago

[2024-02-26] 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] Trillium
[x] Josh
[x] Nayan
[ ] Brad
[x] Evan
[ ] Stephen
[x] Julia
[x] Jack
[ ] Steph
[ ] Rohan
[ ] Daniel
[x] Jo
[x] Vincent

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

Recurring items:

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

New Items

Trillium / group:

[x] Discuss updates on https://github.com/hackforla/VRMS/issues/1411
- [x] Any blockers? Next steps?
- [x] Saw new Issues: https://github.com/hackforla/VRMS/issues/1591 & https://github.com/hackforla/VRMS/issues/1593
  - labeled these together
  - There's a PR associated with hackforla/VRMS#1593. Should help solve the issue.
  - Moved to In Progress
  - Should we just make hackforla/VRMS#1593 a checkbox in hackforla/VRMS#1591?
    - Not needed - as first issue has been closed.
[x] https://github.com/hackforla/VRMS/issues/1576
- [x] Jo - saw that you self-assigned this issue. If you are planning on working on it. If so, let’s put it in progress. Also mention changes to the issue (added steps, including checking off an issue, then moving over ).
  - Jo confirmed and worked with Trillium to finalize issues
- [x] Note that https://github.com/hackforla/VRMS/issues/1574 has been placed in the icebox given the dependency mentioned by Trillium.
[x] Ask Trillium about the status of these PRs… can we assign to review? https://github.com/hackforla/VRMS/issues/1497
- Trillium will take a look at these this week
[x] Ask Team if this still needs to be complete? Looks like we are good to go. Julia about this one: https://github.com/hackforla/VRMS/issues/1318
- Yes - still needs to be worked on and updated with MUI. Check In screen(s) also needs to be updated with MUI - plan to create new design and development issues related to these edits.
[x] Trillium - do you mind reviewing the QA at some point this week?
- Yes - we will meet on Wednesday to discuss this and other concerns
[x] Do we have sufficient engineers on the team, or should we continue to keep our open role post up for backend engineers?
- Given that engineers are in and out, we will keep the role open for the backend engineer
[x] New members to work on setting up the environment this week.

Ask Josh / Julia:

[x] Julia is currently tagged here…. what more info do we need form Bonnie to close? https://github.com/hackforla/VRMS/issues/1533
[x] Review designs, provide feedback based on findings.
- [x] Discussed initial project details screen designs
[ ] Josh - https://github.com/hackforla/VRMS/issues/1538

Issue assignment cleanup:

[x] Jack
[x] Trillium
[x] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[x] Nayan
[ ] Evan
[x] Daniel
[x] Jo
[ ] [Vincent] - Need to collect github handle

Notes from meeting

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

Tasks

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

Items for next week's agenda

JackHaeg commented 4 months ago

2024-03-04 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
[x] Trillium
[x] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[x] Daniel
[ ] Jo
[ ] Vincent

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

Recurring items:

New Items

[x] Check in on new issues:
- [x] hackforla/VRMS#1606
- [x] hackforla/VRMS#1603
[x] Discuss updated issues:
- [x] hackforla/VRMS#1601
- (button was added by mistake on old Figma designs - Nayan to maybe take this forward)?
- [x] hackforla/VRMS#1598 (linked to Jo's issue)
[x] Discuss issues in progress
[x] Note:
- [x] Trillium - should we move this issue back to the icebox or list it as "draft" for now until it can get broken down into smaller issues by Dev: hackforla/VRMS#1243
- [x] hackforla/VRMS#1511 - I see Brad is still attached to this issue (in prioritized backlog) - I haven't seen him make any contributions recently - should we remove him?
- YES - removed Brad for now
- [x] hackforla/VRMS#1497 Let's post an update
- [ ] Please provide weekly updates on issues prior to calls:
  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.
- [ ] For any future front-end changes, please include a screenshot of the UI once the change has been implemented, as a comment on the GitHub issue.
- [ ] Issues to be assigned from Prioritized backlog (not New Issue approval)

-- Split up between Dev / PM & Design

[x] Trillium -
- [x] review PRs, explore in progress issues, assign issues to devs who do not have an issue.
[x] Jack & Julia
- [x] discuss new designs, start issue for Devs: https://www.figma.com/file/pIxFTL62Nx2XyQdZy1fR6f/VRMS-v.4?type=design&node-id=2844%3A4776&mode=design&t=0WEsD6AI4zk13SU6-1
- [x] Discuss setting up meeting with Trillium to explore requirements for design system.
- Set up meeting for Thursday at 10am PST

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] [Vincent] - Need to collect github handle

Notes from meeting

Tasks

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

Items for next week's agenda

JackHaeg commented 4 months ago

2024-03-11 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 appropriately labeled.

Role Call (who is here - add team names)

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

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

Trillium unable to join until 7:40pm

Recurring items:

New Items

[x] hackforla/VRMS#1576 - Jo discuss replication of issue
[x] hackforla/VRMS#1243 - Julia, discuss explore if additional specs required
- [x] Julia - discuss design tickets, also if hackforla/VRMS#1405 is still required given the above ticket
[ ] Touch base with Trillium on following up with DevOps on the two issues mentioned during previous All teams call (#1497, & hackforla/VRMS#1603)
[ ] Trillium - new draft issues:
- [ ] Is hackforla/VRMS#1544 sufficient to address the github secret problem? Add to prioritized backlog? Or should we create a separate ticket that is essentially, "if each of these github secrets is exposed, this is the process we should use to re-secure them"?
- [x] Create draft MUI component issue together to: review code, find where existing components that have yet to be updated are located > update with MUI across the application.
- [ ] If time allows, discuss how production is delivered, deployment working, .

Issue assignment cleanup:

[x] Jack
[ ] Trillium
[x] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[x] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[ ] [Vincent] - Need to collect github handle

Notes from meeting

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

Tasks

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

Items for next week's agenda

JackHaeg commented 4 months ago

2024-03-18 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
[ ] Trillium
[x] Julia
[ ] Josh
[ ] Bonnie
[ ] Rohan
[ ] Brad
[x] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[ ] Vincent

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

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

Recurring items:

[x] Discuss expected UX with Jo hackforla/VRMS#1576
[x] Discuss MUI / designs further with Julia
[ ] Discuss next steps on privacy policy with Rohan

New Items

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] [Vincent] - Need to collect github handle

Notes from meeting

Tasks

[ ] Jack to meet with Trillium to catch up on issues and planning

Items for next week's agenda

JackHaeg commented 3 months ago

2024-03-25 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit and add summary here - All open 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
[ ] Evan
[x] Daniel
[ ] Jo

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

Recurring items:

New Items

Trillium / devs:

[x] Run through issues with Trillium and team if not already complete:
- [x] Review & merge Nayan and Jo’s PRs:
- [ ] Jo’s PR (#1616) and original issue (#1576)
- [ ] Nayan’s PR(#1612) and original issue (#1551)
  - [x] Also check in on Evan's other PR that is associated (#1475) - understand that this PR needs to be on hold until the larger batch of PRs is completed here correct?
- [x] Finish 2 final action items on Jo’s original issue(#1576), assign to new issue: hackforla/VRMS#1574 (and remove dependency labels)
- [x] Review MUI epic issue, break down action items into smaller individual dev issues (happy to help on creating issues if needed)
- [ ] Assign Nayan first action item/issues from MUI Epic issue: hackforla/VRMS#1611
- [x] Discuss progress on check in bug hackforla/VRMS#1411 (currently, available check in times are 1 hour off due to the Daylight savings time change)
- [x] Explore next steps on design given MUI

Issues from previous All Team to discuss with Trillium

[x] Touch base with Trillium on following up with DevOps on the two issues mentioned during previous All teams call (#1497, & hackforla/VRMS#1603)
[x] Is hackforla/VRMS#1544 sufficient to address the github secret problem? Add to prioritized backlog? Or should we create a separate ticket that is essentially, "if each of these github secrets are exposed, this is the process we should use to re-secure them"? If needed, then create together.

Design / PMs

[x] Review Julia's new flow, discuss next steps on design work with MUI.
[ ] Check in with Rohan on hackforla/VRMS#506

Issue assignment cleanup:

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

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 3 months ago

2024-04-01 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
[ ] Julia
[x] Josh
[x] Bonnie
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[x] Jo
[x] Chandler (new dev)

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

Recurring items:

New Items

[x] New devs / introductions
[x] Onboard new devs
[x] Check in Bug - next steps after updates. Appears that even though Onboarding times/checkins are correct, they are not available for check in. Mark progress/updates in comments.
[x] Update Trillium on hackforla/VRMS#1469 - where to access Github secrets (see comments)
[x] Trillium - next DevOps CoP meeting will be on April 10th (no DevOps meeting this week). Please attend if possible to answer "Issues from previous All Team to discuss with Trillium" from previous note
[x] Check in on hackforla/VRMS#1456 - looks like hackforla/VRMS#1464 is marked as complete, however has not been closed as of yet (should we wait to close until all of the associated PRs are merged?). Let's get these assigned as needed.
- [x] Looks like hackforla/VRMS#1551 is also complete. Mark as complete on epic and close or keep open until merged?
- Per Trillium - we want to keep these open for now and allow the PRs to close them
[ ] Collaborate on hackforla/VRMS#1611 and develop/assign issue: hackforla/VRMS#1617
[x] Answer any questions on hackforla/VRMS#1619 with Brad / Josh
[x] Discuss in progress issues, answer questions, assign new issues as needed.

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] [Chandler] - Need to collect github handle

Notes from meeting

Tasks

Items for next week's agenda

JackHaeg commented 3 months ago

2024-04-08 Meeting Agenda and Notes

Prework to prep for meeting

[x] Review the QA
[x] Perform Label Audit

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

[x] Check In Bug hackforla/VRMS#1411 - discuss progress and next steps...(e.g., have all events been "updated"?)
- [x] This week's Onboarding Event was not available for check in this week and the event itself was also not available for Manual Check in on the Onboarding project screen. This is a new issue that we have not seen in the past.
[x] Create new Bug issue for ". . . OR CREATE A NEW PROFILE" - define and assign?
[x] Jo - Clarification on save state for hackforla/VRMS#1576
- [x] Check in on original PR approval: hackforla/VRMS#1616
[x] Trillium Reminder - DevOps meeting is this week (April 10th), to discuss (see All Teams Call from 3/25/2024):
- hackforla/VRMS#1497
- hackforla/VRMS#1603
- hackforla/VRMS#1544
[x] Julia - question: Does the website team have assets we can reuse? (both in Figma and front end components)
[x] Josh - check in on next steps
[x] Brad - answer any questions on current issue: hackforla/VRMS#1619
[x] Work on VRMS onboarding issue together (collect detailed next steps for devs)

Separate into rooms, assign new issues, review PRs

[x] Julia - discuss hackforla/VRMS#1151, begin working on creating issue for devs and refining requirements.

Issue assignment cleanup:

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

Notes from meeting

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

Tasks

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

Items for next week's agenda

JackHaeg commented 3 months ago

2024-04-15 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
[x] Julia
[x] Josh
[ ] Bonnie
[ ] Rohan
[ ] Brad
[ ] Nayan
[x] Evan
[ ] Daniel
[ ] Jo
[ ] Chandler

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

Recurring items:

New Items

[x] Intros with any new members (follow VRMS onboarding issue below)
[x] hackforla/VRMS#1624
- Any additional steps for Devs to follow?
- Thinking of making this an issue template instead of an issue to make issue duplication a little easier.
[x] Trillium - saw that you attended the DevOps meeting last Wednesday - did that address the 3 linked issues mentioned previously?
- hackforla/VRMS#1497
- hackforla/VRMS#1603
- hackforla/VRMS#1544
[x] Trillium / Nayan: hackforla/VRMS#1617 Let's discuss if these smaller issues make sense, or if additional information needs to be added. Also, do we plan to complete all of these in a single PR, or will each part of the file tree be a singular PR?
- individual PRs per file
[x] Trillium - hackforla/VRMS#1616 I know last week we mentioned merging this PR, however it looks like it's still open. Can we merge?
[x] Trillium - let's create a new issue together for the check in bug based on latest comments here:
- [ ] Also, create a bug issue for ". . . OR CREATE A NEW PROFILE".
- Jack / Trillium will meet this week to create these issues together
[ ] Jo - any issues with loading save button logic? MUI components?
- Jo unavailable for tonight's call - will follow up next week
[x] Josh - do you think you will still be able to complete the issue cleanup?
[ ] Brad - any questions on hackforla/VRMS#1619 after using PM credentials to log in?
- Brad unavailable for tonight's call - will follow up next week
[x] Trillium - are we planning to leave all of Evan's issues open / in progress on this epic until they are completed: hackforla/VRMS#1456? - yes will leave open and allow PRs to close these issues
- [x] Looks like hackforla/VRMS#1551 is complete, and can be checked off in the epic at least.
- [x] What to assign next in this epic? (1480 will be assigned next)
[x] Trillium - Looks like hackforla/VRMS#1548 Is essentially complete, and just needs the PR to be approved.
- Yes, added to Prioritized Backlog for now, additional steps need to be taken to complete.

Breakout rooms:

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

Issue assignment cleanup:

[ ] Jack
[ ] Trillium
[ ] Julia
[ ] Josh
[ ] Rohan
[ ] Brad
[ ] Nayan
[ ] Evan
[ ] Daniel
[ ] Jo
[ ] [Chandler] - add github once added to team

Notes from meeting

Tasks

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

Items for next week's agenda

JackHaeg commented 2 months ago

2024-04-22 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
[ ] Josh
[ ] Bonnie
[ ] Rohan
[x] Brad
[x] Nayan
[x] Evan
[ ] Daniel
[ ] Jo
[x] Chandler

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

Recurring items:

New Items

[x] Brad - any questions on hackforla/VRMS#1619 after using PM credentials to log in?
- [x] (Trillium) Discuss files edited
[x] Changes to hackforla/VRMS#1624 - copy to template & assign to Chandler?
- [x] Assigned to Chandler
[ ] MUI edits - make additions as needed.
[x] hackforla/VRMS#1628 completed (Check In Buttons)
[x] hackforla/VRMS#1399 - review Action Items, add to prioritized backlog
[x] hackforla/VRMS#1630 - review action items, add to prioritized backlog
[x] Create issue to change button on "Create a New Profile" screen from "Check In" to "Save"
[x] Check in bug - Trillium to fiddle with service workers running and write / run tests.

Issue assignment cleanup:

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

Notes from meeting

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

Tasks

[x] Nayan & Trillium to meet to explore resolutions to Environment issue.
[ ] Trillium & Jack to meet to refine issues.

hackforla / VRMS

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

Overview

Old Team Meetings:

Jan 30th:

Bonnie jumped on and brought up the following:

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

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

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

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

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

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

2023-06-12 Meeting Agenda and Notes

Role Call (who is here):

Agenda Items:

Notes from meeting

Items for next week's agenda

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

Notes from meeting

Tasks

Items for next week's agenda

2023-07-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

2023-07-31 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