HfLA: Dev/PM Agenda and Notes - 2025

[ExperimentsInHonesty]

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)
       - [ ] [Roslyn](https://github.com/hackforla/website/issues/assigned/roslynwythe)
       - [ ] [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-2025-01-20 are located here #2607
2025-01-27

[ExperimentsInHonesty]

2025-01-27 Meeting Agenda

Prework to prep for meeting

• Review the [QA]
• Review the Questions column. Make sure that all issues have a ready for label by questions column, excluding all ready for...
  • Ready for product
  • Ready for Dev Lead
  • ready for merge team
  • ready for org rep
• 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
      • Backend 2 weeks inactive
• 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
    • Back End
• Can we improve the prework template based on something we see as a pattern?
• Cleanup any anomalies in the dashboard
• Product reviews
  • ready for product for dev issues
  • ready for prioritization

Recurring items:

• review any issues that are in the new issue approval column for
  • Front End
  • Back End
• Accountability and Support Check.
  • Review assignments for each PM or Lead
    • Bonnie
    • Roslyn
    • Will

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

• WG: Skills Issue problem see this Slack post

Notes from the meeting

Tasks

• Dev Lead or Merge Team member: Place a bug report with GitHub about the problems encountered in the Skills Issue

Items for next week's agenda

[t-will-gillis]

Review Inactive Team Members: #7869

Inactive members with open issues:

• GilbertQ: Onboard & Offboard: Product #2688
• Thinking-Panda: ER: Improve testing instructions to "How to Review Pull Requests" page #6319

[t-will-gillis]

For next time:

• Should we (or should I) create a new label Needs Reprioritization or similar?
  • This will make it easier to ID a previously-prioritized issue that the bot puts in "New issue approval" because a dev self-assigns (too many GFIs, etc.)