hackforla / hackforla/website

HfLA: DEV TEAM Meeting Agenda Sunday 🧣

Open
#2,027 215 comments 0 reactions 0 assignees View on GitHub
Complexity: Small Feature: Administrative feature: agenda role: back end/devOps role: front end role: merge team size: 0.25pt
Dominant language
JavaScript
Stars
363
Forks
872
Avg merge
2d 21h
Merged PRs (30d)
18

Description

### 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- see your Skills Issue
- [ ] 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: "dev: GFI", "IM: 1", 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
- [ ] [Being a Part of the Hack for LA Dev Team](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.

#### Previous All Team agendas
- https://github.com/hackforla/website/issues/1734

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.