HfLA: 2026 DEV TEAM Meeting Agenda (Tuesday)

Start with the Weekly Agenda Markdown template in this issue and review the previous agenda linked as issue #2010. Replace every date placeholder, then complete the ice breaker, announcements, wins, and additional meeting topics; done means the Tuesday agenda is filled out and ready for the meeting.

Overview

This issue tracks the agenda for the HFLA website team and weekly roll call.

Weekly Action Items

• Copy and paste the template below in the Weekly Agenda Markdown section
• Replace "MONTH DD, YYYY" with the date
  • At the top of the agenda, where it says "Agenda for MONTH DD, YYYY"
  • At the bottom of the agenda, where it says, "Post-meeting notes MONTH DD, YYYY"
  • At the bottom of the agenda, where it says, "Click to see the meeting notes for MONTH DD, YYYY"
• Fill in the "Ice breaker for everyone" field
• Fill in the Announcements section
• Fill in the Wins section with wins since last meeting
• Add anything else to the agenda we need to go over during meeting

Weekly Agenda Markdown

### Agenda for MONTH DD, YYYY

Facilitator: TBD

#### Meeting start

- [ ] Sign in to [www.vrms.io](https://www.vrms.io)

#### Stand-up update (5-10 minutes)
Each member will give a quick update and popcorn to the next person

- **Returning members** (1-3 minutes)
1. If we have new members present, brief introduction about yourself.
2. What have you completed since last Tuesday?
3. What do you plan to complete before next Tuesday?
4. If you have a blocker, leave a short summary in the chat so we can help you resolve it later in the meeting
- **New members** (1-3 minutes)
1. Where are you from?
2. What are you looking to get out of volunteering with Hack for LA?
3. What is your experience with coding / open source contribution?

**Ice breaker for everyone**: 

#### Announcements (30 minutes)

- [ ] Will open the floor for any announcements
  - [ ] 
- [Pull requests (PRs)](https://github.com/hackforla/website/pulls) 
  - [ ] Go over open PRs to assign reviewers
    - [ ] [How to Review Pull Requests](https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests)
    - [ ] Remind all reviewers to add ETA and availability at the time of assignment
    - [ ] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
    - [ ] Assign junior developers to [On-call PR Review for 1st and 2nd Issue spreadsheets](https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0)
  - [ ] Check on any prs with "Changes requested" 
    - [ ] Show how to request a reviewer to re-review a pr after changes are made
- [ ] Go over Project Board for any questions
  - [ ] [Help wanted label](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+label%3A%22help+wanted%22)
  - [ ] [Questions/In Review column](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22)
- [ ] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

#### Breakout Rooms (Till end of meeting)
- [ ] Issue help / questions 
- [ ] PR help / questions
- [ ] Onboarding new members
  - [ ] Go over the new [pre-issue template](https://github.com/hackforla/website/issues/new/choose) with new developers. Also, go over the following documents if time permits: Demo on picking up a good first issue, [How to Review Pull Requests](https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests), [Being a Part of the HackForLa Team](https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA-Team). Follow the steps in #3175

Resources

Previous Agendas

• https://github.com/hackforla/website/issues/2010