HfLA: DEV TEAM Meeting Agenda Sunday 🧣

[Aveline-art]

Overview

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

Weekly Action Items

• Designate a note taker who will follow up on issue creation
• Make announcements
• Monthly Workflow Demos
  • 1st Sunday: No demo because all leads meeting
  • 2nd Sunday: Progress Report creation
  • 3rd Sunday: Pull Request review demo
  • 4th Sunday: Issue creation, including labels and issue approval process
• Do below agenda items
• Go through project
  • Dev team column
  • In-progress
    • Help wanted label
    • To Update ! label
  • Pull requests

Weekly Agenda Markdown

### Agenda for monthAsText dd, yyyy
Facilitator: TBD

**Welcome to the Sunday All Website Teams meeting. Thank you for joining us!**

## Announcements & Reminders
  - [ ] https://www.vrms.io/
  - [ ] Devs only team meeting on Tuesdays from 7-8pm PST
  - [ ] Office hours on Thursdays from 7-8pm PST 
  - [ ] No meetings for the first 7 days of every month
  - [ ] Open the floor for celebrating any announcements

## Meeting items 
### [Pull Requests](https://github.com/hackforla/website/pulls)
  - [ ] Go over open PRs to assign reviewers
    - [ ] Check on any PRs with `Changes requested`
    - [ ] Explain how to re-request a review after you make the requested changes
  - [ ] All developers are expected to review pull requests 
  - [ ] Encourage team members to review open PRs
    - [ ] [How to Review Pull Requests](https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests)
    - [ ] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
    - [ ] [On-call for Reviewing PRs](https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0)


### [Project Board](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=)
- [ ] Explain the project board and the flow of issues between status columns
- [ ] Explain how to use the various views: "@me", "dev: GFI", etc.
- [ ] Check the ["In Progress (actively working"](https://github.com/orgs/hackforla/projects/86/?filterQuery=status%3A%22In+progress+%28actively+working%29%22+label%3A%22Status%3A+Help+Wanted%22) status column for issues with `Status: Help Wanted` label 
- [ ] Check the ["Questions/In Review"](https://github.com/orgs/hackforla/projects/86/?filterQuery=status%3A%22Questions+%2F+In+Review%22) status column


### HFLA Journey Advice
- [ ] https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team



### To bring up with UI/UX


### To bring up with PM

Example Agenda

Agenda for November 9, 3012*

• Discuss when to have a meeting about making origami
• Get feedback on 3 different brands of folding paper
• Create issue about the origami ship project

*Note: Date is written out because of cultural differences in date formatting.

[t-will-gillis]

Agenda for June 9, 2024

Facilitator: Will

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Announcements & Reminders

• Devs only team meeting on Tuesdays from 7-8pm PST
• Office hours on Thursdays from 7-8pm PST
• No meetings for the first 7 days of every month
• Open the floor for celebrating any announcements

Meeting items

Pull Requests

• Go over open PRs to assign reviewers
• Check on any PRs with "Changes requested"
  • Explain how to re-request a review after you make the requested changes
• All developers are expected to review pull requests - goal is to review at least two PRs for every PR submitted.
• Encourage team members to review open PRs
  • How to Review Pull Requests
  • Remind PR reviewers to add their ETA and availability after requesting themselves for a review
  • On-call for Reviewing PRs

Project Board

• Explain the Project Board and the flow of issues between columns
• Check the "In Progress (actively working)" column for issues with Status: Help Wanted label.
• Check the "Questions/In Review" column

HFLA Journey Advice

• Being a Part of the Hack for LA Dev Team

To bring up with UI/UX

To bring up with PM

[t-will-gillis]

Agenda for June 23, 2024

Facilitator: Will

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Stand-up update

Each member will give a quick update and popcorn to the next person. New members, please give a brief intro about yourself.

• New members

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?

• Returning members

1. What have you completed in the last week?
2. What do you plan to complete before the next meeting?
3. If you have a blocker, leave a short summary in the chat so we can help you resolve it later in the meeting

Announcements & Reminders

• Devs only team meeting on Tuesdays from 7-8pm PST
• Office hours on Thursdays from 7-8pm PST
• No meetings for the first 7 days of every month
• Open the floor for celebrating any announcements

Meeting items

Pull Requests

• Go over open PRs to assign reviewers
• Check on any PRs with Changes requested
  • Explain how to re-request a review after you make the requested changes
• All developers are expected to review pull requests - goal is to review at least two PRs for every PR submitted.
• Encourage team members to review open PRs
  • How to Review Pull Requests
  • Remind PR reviewers to add their ETA and availability after requesting themselves for a review
  • On-call for Reviewing PRs

Project Board

• Explain the project board and the flow of issues between columns
• Check the "In Progress (actively working)" column for issues with Status: Help Wanted label.
• Check the "Questions/In Review" column

HFLA Journey Advice

• https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team

To bring up with UI/UX

To bring up with PM

[t-will-gillis]

Agenda for June 30, 2024

Facilitator: Will

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Stand-up update

Each member to give a quick update and popcorn to the next person. New members, please give a brief intro about yourself. You can raise your hand if you have not gone yet

• New members

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?

• Returning members

1. What have you completed in the last week?
2. What do you plan to complete before the next meeting?
3. If you have a blocker, leave a short summary in the chat so we can help you resolve it later in the meeting

Announcements & Reminders

• Devs only team meeting on Tuesdays from 7-8pm PST
• Office hours on Thursdays from 7-8pm PST
• No meetings for the first 7 days of every month
• No meetings in July

Meeting items

Pull Requests

• Go over open PRs to assign reviewers
• Check on any PRs with Changes requested
  • Explain how to re-request a review after you make the requested changes
• All developers are expected to review pull requests - goal is to review at least two PRs for every PR submitted.
• Encourage team members to review open PRs
  • How to Review Pull Requests
  • Remind PR reviewers to add their ETA and availability after requesting themselves for a review
  • On-call for Reviewing PRs

Project Board

• Link to new project board: https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=
• Explain the project board and the flow of issues between status columns
• Check the "In Progress (actively working)" status column for issues with Status: Help Wanted label.
• Check the "Questions/In Review" status column

HFLA Journey Advice

• https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team

To bring up with UI/UX

To bring up with PM