-
-
Notifications
You must be signed in to change notification settings - Fork 844
Closed
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issuefeature: agendarole: dev leadsTasks for technical leadsTasks for technical leadsrole: merge teamTasks for merge team membersTasks for merge team membersrole: productProduct ManagementProduct Managementsize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Milestone
Description
Overview
This issue tracks the agenda and notes for the Development/PM meeting
Action Items
- Add the Date of the next meeting below
- Link the Agenda/Notes from meeting
Resources/Instructions
Template
## [DATE IN YYYY-MM-DD FORMAT] Meeting Agenda
### Prework to prep for meeting
- [ ] Review the [QA]
- [ ] Review the [Questions column](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22). Make sure that all issues have a ready for label by [questions column, excluding all `ready for...`](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+-label%3A%22ready+for+org+rep%22+-label%3A%22ready+for+product%22+-label%3A%22ready+for+dev+lead%22+-label%3A%22ready+for+merge+team%22)
- [ ] [Ready for product](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+product%22)
- [ ] [Ready for Dev Lead](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+dev+lead%22)
- [ ] [ready for merge team](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+merge+team%22)
- [ ] [ready for org rep](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+org+rep%22)
- [ ] 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
- [ ] Check 2 week inactive label on the in progress column
- [ ] [Frontend 2 weeks inactive](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%222+weeks+inactive%22++label%3A%22role%3A+front+end%22)
- [ ] [Backend 2 weeks inactive](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%222+weeks+inactive%22+++label%3A%22role%3A+back+end%2Fdevops%22)
- [ ] Check 2 week inactive PRs
- [ ] Check all open pre-work developers checklists anywhere on the board AND any closed pre-work developers checklist in QA
- [ ] If it's in New Issue Approval, see if the prework is `ready for milestone` meaning it is assigned to the person who opened the prework, has a role label, and is on the Project Board.
- [ ] [Front End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22feature%3A+onboarding%2Fcontributing.md%22+label%3A%22role%3A+front+end%22#column-15490305)
- [ ] [Back End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22feature%3A+onboarding%2Fcontributing.md%22++label%3A%22role%3A+back+end%2Fdevops%22#column-15490305)
- [ ] Can we improve the prework template based on something we see as a pattern?
- [ ] Cleanup any anomalies in the [dashboard ](https://lookerstudio.google.com/reporting/f42df1c1-99df-4fa1-b719-7e135168bfa3)
- [ ] Product reviews
- [ ] [`ready for product` for dev issues](https://github.com/hackforla/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22ready+for+product%22+-label%3A%22role%3A+design%22+-label%3A%22role%3A+legal%22+-label%3A%22role%3A+writing%22+-label%3A%22role%3A+product%22)
- [ ] [`ready for prioritization`](https://github.com/hackforla/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22Ready+for+Prioritization%22)
### Recurring items:
- [ ] review any issues that are in the new issue approval column for
- [ ] [Front End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22#column-15235217)
- [ ] [Back End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22#column-15235217)
- [ ] Accountability and Support Check.
- [ ] Review assignments for each PM or Lead
- [ ] [Bonnie](https://github.com/hackforla/website/issues/assigned/ExperimentsInHonesty)
- [ ] [Danielle](https://github.com/hackforla/website/issues/assigned/daras-cu)
- [ ] [Will](https://github.com/hackforla/website/issues/assigned/t-will-gillis)
### FYIs (nothing needs to be done, just keeping each other informed)
### 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
Prior and upcoming meetings
All meetings from 2022 to 2025-01-20 are located here #2607
2025-01-27
2025-02-03
2025-02-10
2025-02-24
2025-03-03
2025-03-10
2025-03-17
2025-03-31
2025-04-07
2025-04-14
2025-04-21
2025-04-28
2025-05-05
2025-05-12
2025-05-19
2025-06-02
2025-06-09
2025-06-16
2025-06-23
2025-06-30
2025-08-04
2025-08-11
2025-08-18
2025-08-25
2025-09-08
2025-09-15
2025-09-22
2025-09-29
2025-10-06
2025-10-13
2025-10-20
2025-10-27
2025-11-03
2025-11-10
2025-11-17
2025-11-24
Metadata
Metadata
Assignees
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issuefeature: agendarole: dev leadsTasks for technical leadsTasks for technical leadsrole: merge teamTasks for merge team membersTasks for merge team membersrole: productProduct ManagementProduct Managementsize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Type
Projects
Status
Done