Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

VRMS: ALL: Monday Meeting Agenda 📝 #1280

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

VRMS: ALL: Monday Meeting Agenda 📝 #1280

jbubar opened this issue Jan 31, 2023 · 73 comments
Assignees
Labels
feature: Agenda role: Product size: 0.5pt Can be done in 2-3 hours or less

Comments

@jbubar
Copy link
Member

jbubar commented Jan 31, 2023

Overview

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

Here is the old one:
#1051

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

## [DATE] Meeting Agenda and Notes

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

### Role Call (who is here - add team names)
- [x] Jack
- [ ] Bonnie
- [ ] Trillium
- [ ] Julia
- [ ] Josh
- [ ] Brad
- [ ] Evan
- [ ] Angela 
- [ ] Katiuska
- [ ] Nora 
- [ ] Nikhil
- [ ] Mudassir
- [ ] Sankshay
- [ ] Vorleak
- [ ] James
- [ ] Pluto

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


### Recurring items: 

### New Items 

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

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

### Notes from meeting

### Tasks

### Items for next week's agenda

Old Team Meetings:

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

@jbubar
Copy link
Member Author

jbubar commented Jan 31, 2023

Jan 30th:

Bonnie jumped on and brought up the following:

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

@heyitsalexander
Copy link
Member

heyitsalexander commented Jan 31, 2023

Template

## [DATE] Meeting Agenda and Notes

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

### Role Call (who is here)

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

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

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


### Notes from meeting

### Tasks

### Items for next week's agenda

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 4, 2023

2023-02-06 Meeting Agenda and Notes

Prework to prep for meeting

  • Judy's prototype work

Role Call (who is here)

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

  • Onboarding Event

Recurring items:

Notes from meeting

Tasks

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

Items for next week's agenda

@AmandaGlover-PM
Copy link
Member

2023-02-06 Meeting Agenda and Notes

Prework to prep for meeting

  • Judy's prototype work

Role Call (who is here)

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

  • Onboarding Event

Recurring items:

Notes from meeting

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

Tasks

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

Items for next week's agenda

@heyitsalexander
Copy link
Member

heyitsalexander commented Feb 9, 2023

2023-02-13 Meeting Agenda and Notes

Prework to prep for meeting

  • Judy's prototype reviewed and usability testing script

Role Call (who is here)

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

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

Recurring items:

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

Resources for meeting

Notes from meeting

Tasks

  • Ask for permission to record

  • Usability testing with Bonnie part 2

  • Post test survey

  • UX researcher responsbilities?

Items for next week's agenda

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

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

@ExperimentsInHonesty
Copy link
Member

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

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

create an account

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

Log In

  • I added text to this slide

Three Important Notes/Quirks:

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

Edit Meeting Time slide

  • I added text to the second bullet

@ExperimentsInHonesty
Copy link
Member

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

@heyitsalexander
Copy link
Member

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

@ExperimentsInHonesty
Copy link
Member

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

@heyitsalexander
Copy link
Member

heyitsalexander commented Feb 25, 2023 via email

@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Feb 28, 2023

2023-02-27 Meeting Agenda and Notes

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

Recurring items:

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

Notes from meeting

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

  • User Testing notes (Usability Testing 2 for VRMS)

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

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

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

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

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

  • Other comments:

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

Tasks

  • To be added during the meeting

Items for next week's agenda

  • Discuss updates to Github tickets between dev & design

@heyitsalexander
Copy link
Member

heyitsalexander commented Feb 28, 2023

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

From: @MattPereira (#1241 (comment))

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

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

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

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

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

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

@MattPereira MattPereira changed the title VRMS Agenda All Teams: Meeting Agenda Monday 📝 Mar 7, 2023
@MattPereira MattPereira changed the title All Teams: Meeting Agenda Monday 📝 ALL TEAMS: Monday Meeting Agenda 📝 Mar 13, 2023
@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Mar 14, 2023

2023-03-13 Meeting Agenda and Notes

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

Agenda items:

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

Notes from meeting

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

Tasks

  • Updated prioritized backlog
  • [ ]Backend updates

Items for next week's agenda

  • Updates on the above

@jbubar
Copy link
Member Author

jbubar commented May 23, 2023

Facilitator: Amanda
Time wizard: Trilluim
Scribe: Josh

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

Notes:

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

Getting designers

  • need design issues
  • need cards on open roles

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

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

@trillium
Copy link
Member

trillium commented May 23, 2023

Meeting minutes from timecop:

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

@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Jun 6, 2023

2023-06-05 Meeting Agenda and Notes

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

Agenda Items:

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

Notes from meeting

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

Items for next week's agenda

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

@AmandaGlover-PM
Copy link
Member

AmandaGlover-PM commented Jun 11, 2023

2023-06-12 Meeting Agenda and Notes

Role Call (who is here):

Agenda Items:

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

Notes from meeting

Items for next week's agenda

  • TBD

@JackHaeg
Copy link
Member

JackHaeg commented Jul 6, 2023

Moving these items to Product Agenda:

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

@JackHaeg
Copy link
Member

JackHaeg commented Jul 6, 2023

2023-07-10 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.) - 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

Notes from meeting

  • Dev team used the meeting time to explore the VRMS check-in issue described here Bug: Users Cannot Check In #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.

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

JackHaeg commented Apr 30, 2024

2024-04-29 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

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

Trillium - if time permits (otherwise will discuss async)

Issue assignment cleanup:

Notes from meeting

  • Julia unavailable due to scheduling conflict

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented May 7, 2024

2024-05-06 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items & Notes

Split up into breakout rooms

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

Issue assignment cleanup:

Notes from meeting

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

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented May 14, 2024

2024-05-13 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

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

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented May 21, 2024

2024-05-20 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

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

JackHaeg commented Jun 4, 2024

2024-06-03 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

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

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

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

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Jun 11, 2024

2024-06-10 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

Recurring items:

New Items

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

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

JackHaeg commented Jun 18, 2024

2024-06-17 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Trillium
  • Julia
  • Josh
  • Bonnie
  • Brad
  • Nayan
  • Evan
  • Jo
  • Chandler
  • Angela
  • Katiuska
  • Steph

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

  • (confirmed) HfLA will be taking a break for the month of July. Next Monday's call will be our last meeting until August. Anyone is welcome to continue working and continue communicating async over Slack if they would like.
  • Team updates on Daniel & Rohan, offboarding.
  • Will be conducting a review of GitHub Project teams.
  • New GitHub project board!

Recurring items:

New Items

BREAKOUT ROOMS

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Jun 25, 2024

2024-06-24 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • 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:

Breakout rooms (review Issue assignment cleanup below).

Issue assignment cleanup:

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg JackHaeg pinned this issue Jul 16, 2024
@JackHaeg
Copy link
Member

JackHaeg commented Aug 6, 2024

2024-08-05

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

  • Nora out of country / no internet for next 3 weeks - will be unable to respond to messages on PRs, okay to handoff work if necessary.
  • Next week, People Depot will attend our call to discuss VRMS needs for database fields and permissions architecture. Discuss next steps to prepare. (building VRMS on top of People Depot's backend)
  • Processes update:
    • Devs to use issue cleanup on Monday calls
    • Splitting up PRs amongst team members (2 approved reviews before merging). Aim to improve turnaround time to feedback / merged work.
    • Reminder - Weekly update in issue comments:
1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
 - remember to add links to the top of the issue if they are going to be needed again.

Recurring items:

New Items

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Aug 13, 2024

2024-08-12 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

  • 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.
    • Trillium to discuss a list of requirements
  • Potential intro/onboarding of new dev Mudassir Hussain
  • Open Role posts - any requests? Last week's recruitment was packed.
  • Note on Issue drafts:
  • 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

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: Finalize Project Status Designs #1678

###Issue assignment cleanup:
PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Aug 27, 2024

2024-08-26 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

  • No Monday meeting next week - due to Labor Day
  • 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

  • Onboarding new dev Mudassir Hussain.

Trillium:

Julia

###Issue assignment cleanup:
PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Sep 5, 2024

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
Copy link
Member

JackHaeg commented Sep 10, 2024

2024-09-09 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Steph
  • Bonnie
  • Trillium
  • Julia
  • Josh
  • Brad
  • Nayan
  • Evan
  • Daniel
  • Chandler
  • Angela - ON BREAK until September
  • Katiuska
  • Nora
  • Nikhil
  • 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:

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

PR Review:

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

Nora’s PR:

Evan/Trillium:

  • feat: Validate Google drive, but not sure how to use custom error msg #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.
    • 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.
    • 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.
      • 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
  • Need to discuss Validation requirements.

Trillium:

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

Julia:

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

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Sep 17, 2024

2024-09-16 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

  • Trillium out sick today, Julia unable to join.

Recurring items:

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

New Items:

Nikhil & Team

  • Discuss latest PR: 1486 - The ability to set a User as Admin on Edit Users Page #1746
    • Ensure that "But not the admin that promoted you" requirement is not included in this PR (both from front end & back end)
    • Explore potentially holding off on merging until Create ability for Admins to promote and demote Admins #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 ([email protected]) 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).
      • Discuss front end and back end implementation of these changes.
      • Request Josh to promote [email protected] to admin as a first step. - DONE
      • New issue created here tracking Super Admin User: Implement Super Admin User Feature #1747
  • Discuss updates to the User Permission Epic Epic - User Permission Search #1737. Nikhil working on backend perspective.
  • Evan - discuss PR mentioned last week - feat: Validate Google drive, but not sure how to use custom error msg #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
  • PR assignment / review with Brad / Josh.

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Sep 24, 2024

2024-09-23 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Steph
  • Bonnie
  • Trillium
  • Julia
  • Josh
  • Brad
  • Evan
  • Daniel
  • Chandler
  • Angela - ON BREAK until September
  • Katiuska
  • Nora
  • Nikhil
  • Mudassir

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

Recurring items:

New Items

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Oct 1, 2024

2024-09-30 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Bonnie
  • Trillium
  • Julia
  • Josh
  • Brad
  • Evan
  • Chandler
  • Angela
  • Katiuska
  • Nora - unavailable for 9/30 & 10/7 meetings
  • Nikhil
  • 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:

Josh & Trillium

Trillium & Evan

Chandler

Nikhil

  • Updates on Super Admin User issue?

Angela

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

Brad

Team:

  • PR cleanup / assignment.

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@ExperimentsInHonesty
Copy link
Member

@JackHaeg
Copy link
Member

JackHaeg commented Oct 7, 2024

2024-10-07 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Bonnie
  • Trillium
  • Julia
  • Josh
  • Brad
  • Evan
  • Chandler
  • Angela
  • Katiuska
  • Nora - unavailable for 9/30 & 10/7 meetings
  • 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

Nikhil / Mudassir

Nikhil

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

Trillium

Angela

Julia

Full Team

  • Review & assign PRs.

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

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

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Oct 15, 2024

2024-10-14 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

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

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

  • New devs joining the team / introductions.
  • Onboarding

Recurring items:

New Items

Julia

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

  • Onboard new team members
  • Allocate good first issues for new members

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Oct 22, 2024

2024-10-21 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • 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

Sankshay:

Trillium:

Angela:

Full team:

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

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Oct 29, 2024

2024-10-28 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Bonnie
  • Trillium
  • Julia
  • Josh
  • Brad
  • Evan
  • Angela
  • Katiuska
  • Nora
  • Nikhil
  • Mudassir
  • Sankshay
  • Vorleak
  • James
  • Pluto

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

  • VRMS project board was closed near the end of last week, reopened
  • Great work on reviewing PRs - let’s keep this up!
    • Trillium - Will we have the ability to merge some PRs this week? Last merge: 3w
    • When can we rebuild PROD again?

Recurring items:

New Items

Trillium:

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Nov 5, 2024

2024-11-04 Meeting Agenda and Notes

Prework to prep for meeting

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

Role Call (who is here - add team names)

  • Jack
  • Bonnie
  • Trillium
  • Julia
  • Josh
  • Brad
  • Evan
  • Angela
  • Katiuska
  • Nora
  • Nikhil
  • Mudassir
  • Sankshay
  • Vorleak
  • James
  • Pluto

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

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

Recurring items:

New Items

Trillium

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

Vorleak

Team

  • Vrms client terraform migration incubator#29
    • BACKGROUND: Sitting since November of last year. Was being worked on by Chelsey, but failed its plan. Need someone to take it over from our team to get VRMS Dev & Prod instances onto incubator for and kill other instances that are costing HfLA
    • TIMELINE: By March 2025
    • REQUEST:
      • Incubator team is happy if we want to start from scratch, work through it and fix it with them, etc. The team currently has an experienced AWS engineer that could assist with this.
      • VRMS team member would need to attend the DevOps CoP Wednesday meeting (next meeting will happen on November 13th at 6pm Pacific).
      • VRMS team member needs to have some experience with AWS, terraform.
    • Questions for team:
      • Is anyone interested in picking this up?
        • If Yes:
          • Name of VRMS member taking on issue: Angela
          • Can you attend the next DevOps CoP meeting on November 13th at 6pm Pacific
          • Angela already has DevOps CoP meeting invite and will attend.
          • Trillium to get this member up to speed
          • Recommend checking at any issues that Home Unite Us has worked on (on the incubator or Ops repos). Just come to the DevOps call and a member from HUU will tell you where to look.
  • Close Issue?
    • Yes
    • No - leave open for now, and Angela will review.

Time permitting - split up into breakout rooms

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

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

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

Tasks

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

Items for next week's agenda

@JackHaeg
Copy link
Member

JackHaeg commented Nov 19, 2024

[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
  • Angela
  • Katiuska
  • Nora
  • Nikhil
  • Mudassir
  • Sankshay
  • Vorleak
  • James
  • Pluto

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

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

Recurring items:

New Items

Trillium:

Vorleak / Trillium:

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

Nikhil:

Nora:

Angela:

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

Evan:

Breakout Rooms:

Julia:

Issue assignment cleanup:

PMs / Designers

Developers

Notes from meeting

Tasks

Items for next week's agenda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: Agenda role: Product size: 0.5pt Can be done in 2-3 hours or less
Projects
Status: Agendas & Resources
Development

No branches or pull requests

8 participants