HfLA: DEV TEAM Meeting Agenda Tuesday📝

hackforla / website

Hack for LA's website

https://www.hackforla.org

GNU General Public License v2.0

292 stars 707 forks source link

HfLA: DEV TEAM Meeting Agenda Tuesday📝 #2010

Open abuna1985 opened 2 years ago

abuna1985 commented 2 years ago

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
[x] 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/hackforla/website/projects/7?card_filter_query=label%3A%22status%3A+help+wanted%22)
  - [ ] [Questions/In Review column](https://github.com/hackforla/website/projects/7#column-8178690)
- [ ] 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

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 an issue about the origami ship project

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

Adastros commented 10 months ago

Agenda for July 25, 2023

Facilitator: Danny

Meeting start

[x] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

adrianang commented 9 months ago

Agenda for August 8, 2023

Facilitator: Adrian (@adrianang) / Richard (@kwangric)

Meeting start

[x] Sign in to 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)

[x] Will open the floor for any announcements
- [x] Reminder: This upcoming Thursday's (8/10) office hours are cancelled.
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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.
- [x] Reminder: This upcoming Thursday's (8/10) office hours are cancelled.

Breakout Rooms (Till end of meeting)

[x] Issue help / questions
[x] PR help / questions
[x] Onboarding new members
- [x] Go over the newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

blulady commented 9 months ago

Agenda for August 15, 2023

Facilitator: @blulady

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[ ] 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 newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

t-will-gillis commented 9 months ago

Agenda for August 22, 2023

Facilitator: Will @t-will-gillis

Meeting start

[x] ignore ~Sign in to vrms.io~

Stand-up update (5-10 minutes)

Each member will give a quick update and popcorn to the next person

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?
Returning members (1-3 minutes)
1. What have you completed since last Tuesday?
2. What do you plan to complete before next Tuesday?
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 (30 minutes)

[x] Will open the floor for any announcements
- [ ]
[x] Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Example of a good PR review https://github.com/hackforla/website/pull/5257
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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)

[x] Issue help / questions
[x] PR help / questions
[ ] Onboarding new members
- [ ] Go over the newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 9 months ago

Agenda for August 29, 2023

Facilitator: Roslyn Wythe

Meeting start

[x] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[ ] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 8 months ago

Agenda for Sept. 12, 2023

Facilitator: TBD

Meeting start

[x] Sign in to 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)
- [ ] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] 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
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[ ] 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 newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 8 months ago

Agenda for Sept. 19, 2023

Facilitator: Roslyn Wythe

Meeting start

[ ] Sign in to 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)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[ ] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

blulady commented 8 months ago

Agenda for September 26, 2023

Facilitator: @blulady

Meeting start

[x] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [ ] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] 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
- [x] Check on any prs with "Changes requested"
- [x] 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
- [ ] Questions/In Review column
[ ] 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 newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

blulady commented 7 months ago

Agenda for October 10, 2023

Facilitator: @blulady

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] 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
- [ ] Questions/In Review column
[x] 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)

[x] Issue help / questions
[x] PR help / questions
[ ] Onboarding new members
- [ ] Go over the newpre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

t-will-gillis commented 7 months ago

Agenda for October 17, 2023

Facilitator: @t-will-gillis

Meeting start

[ ] Sign in to www.vrms.io

Stand-up update (5-10 minutes)

[x] Each member will give a quick update and popcorn to the next person
[x] Raise your hand if you have not gone yet

New members (1-3 minutes)

Where are you from?
What are you looking to get out of volunteering with Hack for LA?
What is your experience with coding / open source contribution?

Returning members (1-3 minutes)

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

Announcements (30 minutes)

[ ] Will open the floor for any announcements
- [ ] Do you have anything you'd like to share? Interviews? Job offers? Relevant seminars upcoming?
[x] Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] Check on any PRs with "Changes requested"
- [x] How to Review Pull Requests
- [x] Example of good PR reviews
  - [x] Examples of what to check for:
  - correct branches,
  - correctly linked issue (reviewer should review and understand what the original issue was asking for),
  - concise summary of what changes are to be made and why,
  - before and after screenshots if the changes affect the display of the website (otherwise "No visual changes to website"),
  - confirmation via Docker when visual changes are made to the website, especially to check that no other, unintended/ unexpected changes have occurred due to the new code, and finally
  - code edits are only what needs to be changed -
  - [x] Reminder: all reviewers to add ETA and availability at the time of assignment
  - [x] Show how to request a reviewer to re-review a PR after changes are made
- [x] 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
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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)

[x] Issue help / questions
[x] PR help / questions
[ ] Onboarding new members
- [ ] Go over the new pre-issue template 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,
- Being a Part of the Hack for LA Team. Follow the steps in #3175

blulady commented 7 months ago

Agenda for October 24, 2023

Facilitator: @blulady

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [ ] 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
- [ ] 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
- [ ] Questions/In Review column
[ ] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 6 months ago

Agenda for November 14, 2023

Facilitator: Roslyn Wythe

Meeting start

[ ] Sign in to 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)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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)

[x] Issue help / questions
[ ] PR help / questions
[ ] Onboarding new members
- [ ] Go over the new pre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

blulady commented 6 months ago

Agenda for November 21, 2023

Facilitator: @blulady

Meeting start

[x] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] 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
- [ ] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

blulady commented 6 months ago

Agenda for November 28, 2023

Facilitator: @blulady

Meeting start

[ ] Sign in to 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)
- [x] Go over open PRs to assign reviewers
- [ ] 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
- [ ] 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
- [ ] Questions/In Review column
[ ] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

t-will-gillis commented 4 months ago

Agenda for January 9, 2024

Facilitator: Will

Meeting start

[ ] ~Sign in to www.vrms.io~

Stand-up update (5-10 minutes)

[ ] Each member will give a quick update and popcorn to the next person
[ ] Raise your hand if you have not gone yet

New members (1-3 minutes)

Where are you from?
What are you looking to get out of volunteering with Hack for LA?
What is your experience with coding / open source contribution?

Returning members (1-3 minutes)

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

Announcements (30 minutes)

[ ] Will open the floor for any announcements / anything that anyone would like to share
[ ] Pull requests (PRs)](https://github.com/hackforla/website/pulls)
- [x] Go over open PRs to assign reviewers
- [x] Check on any PRs with "Changes requested"
- [x] How to Review Pull Requests
- [x] Example of good PR reviews
- [x] Examples of what to check for:
  - correct branches,
  - correctly linked issue (reviewer should review and understand what the original issue was asking for),
  - concise summary of the changes being made, and the reason why the change are to be made and why,
  - before and after screenshots if the changes affect the display of the website (otherwise "No visual changes to website"),
  - confirmation via Docker when visual changes are made to the website, especially to check that no other, unintended/ unexpected changes have occurred due to the new code, and finally
  - code edits are only what needs to be changed
- [x] Reminder: all reviewers to add ETA and availability at the time of assignment
- [x] Show how to request a reviewer to re-review a PR after changes are made
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 with new developers.
- Demo on picking up a good first issue, , Being a Part of the HackForLa Team. Follow the steps in #3175

t-will-gillis commented 4 months ago

Agenda for January 16, 2024

Facilitator: Will

Meeting start

[ ] ~Sign in to www.vrms.io~

Stand-up update (5-10 minutes)

[x] Each member will give a quick update and popcorn to the next person
[x] Raise your hand if you have not gone yet

New members (1-3 minutes)

Where are you from?
What are you looking to get out of volunteering with Hack for LA?
What is your experience with coding / open source contribution?

Returning members (1-3 minutes)

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

Announcements (30 minutes)

[ ] Will open the floor for any announcements / anything that anyone would like to share
[x] Pull requests (PRs)](https://github.com/hackforla/website/pulls)
- [x] Go over open PRs to assign reviewers
- [x] Check on any PRs with "Changes requested"
- [x] How to Review Pull Requests
- [x] Example of good PR reviews
- [x] Examples of what to check for:
  - correct branches,
  - correctly linked issue (reviewer should review and understand what the original issue was asking for),
  - concise summary of the changes being made, and the reason why the change are to be made and why,
  - before and after screenshots if the changes affect the display of the website (otherwise "No visual changes to website"),
  - confirmation via Docker when visual changes are made to the website, especially to check that no other, unintended/ unexpected changes have occurred due to the new code, and finally
  - code edits are only what needs to be changed
- [x] Reminder: all reviewers to add ETA and availability at the time of assignment
- [x] Show how to request a reviewer to re-review a PR after changes are made
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 with new developers.
- Demo on picking up a good first issue, , Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 4 months ago

Agenda for Jan 23,2024

Facilitator: Roslyn Wythe

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [ ] Questions/In Review column
[ ] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 4 months ago

Agenda for January 30, 2024

Facilitator: Roslyn Wythe

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[ ] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 3 months ago

Agenda for February 13, 2024

Facilitator: Roslyn Wythe

Meeting start

[ ] Sign in to www.vrms.ioFeb

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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[ ] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

t-will-gillis commented 3 months ago

Agenda for February 20, 2024

Facilitator: Will

Meeting start

[ ] Sign in to www.vrms.io

Stand-up update (5-10 minutes)

Each member to give a quick update and popcorn to the next person
Raise your hand if you have not gone yet

New members (1-3 minutes)

Where are you from?
What are you looking to get out of volunteering with Hack for LA?
What is your experience with coding / open source contribution?

Returning members (1-3 minutes)

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

Announcements

[ ] Will open the floor for any announcements / anything that anyone would like to share
[x] Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] Check on any PRs with "Changes requested"
- [x] How to Review Pull Requests
- Examples of what to check for:
  - correct branches - into: hackforla:gh-pages from somebody:issue-worked-on-7890, NOT somebody:gh-pages
  - correctly linked issue (reviewer should review and understand what the original issue was asking for),
  - concise summary: what changes are being made, and the specific reason why the changes are being made (not "because the issue said to make the changes"),
  - before and after screenshots if the changes affect the display of the website (otherwise "No visual changes to website"),
  - confirmation via Docker when visual changes are made to the website, especially to check that no other, unintended/ unexpected changes have occurred due to the new code. When appropriate, checking responsive design on multiple browsers, and finally
  - code edits change only what needs to be changed to satisfy the original issue. If you see something else that looks wrong or you are unsure, please do ask: sometimes there is another issue and sometimes it is something we did not see.
- [x] Reminder: all reviewers to add ETA and availability at the time of assignment
- [x] Show how to request a reviewer to re-review a PR after changes are made
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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
[ ] Any other questions
[ ] Onboarding new members
[ ] Go over the new pre-issue template with new developers.

drakenguyen4000 commented 3 months ago

Agenda for February 27, 2024

Facilitator: Drake Nguyen

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

drakenguyen4000 commented 2 months ago

Agenda for March 12, 2024

Facilitator: Drake Nguyen

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

drakenguyen4000 commented 2 months ago

Agenda for March 19, 2024

Facilitator: Drake Nguyen

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [ ] Go over open PRs to assign reviewers
- [ ] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

drakenguyen4000 commented 2 months ago

Agenda for March 26, 2024

Facilitator: Drake Nguyen

Meeting start

[ ] Sign in to 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)
- [ ] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

drakenguyen4000 commented 1 month ago

Agenda for April 9, 2024

Facilitator: Drake Nguyen

Meeting start

[ ] Sign in to 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)
- [ ] Go over open PRs to assign reviewers
- [ ] 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
- [ ] 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
- [ ] Questions/In Review column
[ ] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

drakenguyen4000 commented 1 month ago

Agenda for April 16, 2024

Facilitator: Drake Nguyen

Meeting start

[ ] Sign in to 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)
- [ ] Go over open PRs to assign reviewers
- [ ] 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
- [ ] 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
- [ ] Questions/In Review column
[ ] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

Thinking-Panda commented 1 month ago

Agenda for April 23,2024

Facilitator: Nikileshwari Prasadh

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

Thinking-Panda commented 1 month ago

Agenda for April 30, 2024

Facilitator: Nikileshwari Prasadh

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [ ] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

roslynwythe commented 2 weeks ago

Agenda for May 14, 2024

Facilitator: Roslyn Wythe

Meeting start

[x] Sign in to 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)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [ ] Help wanted label
- [ ] Questions/In Review column
[ ] 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)

[x] Issue help / questions
[x] PR help / questions
[ ] Onboarding new members
- [ ] Go over the new pre-issue template 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, Being a Part of the HackForLa Team. Follow the steps in #3175

Thinking-Panda commented 1 week ago

Agenda for May 21, 2024

Facilitator: Nikileshwari Prasadh

Meeting start

[ ] Sign in to 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)

[x] Will open the floor for any announcements
- [ ]
Pull requests (PRs)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175

Thinking-Panda commented 4 days ago

Agenda for May 28,2024

Facilitator: Nikileshwari Prasadh

Meeting start

[ ] Sign in to 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)
- [x] Go over open PRs to assign reviewers
- [x] How to Review Pull Requests
- [x] Remind all reviewers to add ETA and availability at the time of assignment
- [x] All developers are expected to review pull requests. (Target: for every PR created, should review 2 PRs)
- [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
- [x] Check on any prs with "Changes requested"
- [x] Show how to request a reviewer to re-review a pr after changes are made
[x] Go over Project Board for any questions
- [x] Help wanted label
- [x] Questions/In Review column
[x] 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 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, Being a Part of the HackForLa Team. Follow the steps in #3175