HfLA: 2026 Dev/PM Agenda and Notes

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)

### 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

Resources

Previous Agendas

HfLA: Dev/PM Agenda and Notes - 2025 #7859
All meetings from 2022 to 2025-01-20 are located here HfLA: Dev/PM Agenda and Notes #2607

Prior and upcoming meetings

2026-10-19 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...
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 …

2026-10-12 Meeting Agenda

Prework to prep for meeting

Recurring items:

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

JC's

Move this to an ER: HfLA: 2026 Dev/PM Agenda and Notes #8442 (comment) - The contents of the comment has been placed in ER: Refactor Value Info and Program Area & Project Pages #8840.
Add this to sdg-info repo: HfLA: 2026 Dev/PM Agenda and Notes #8442 (comment)
Make a note in the wiki page for wiki-repo to update the "Value" section in https://github.com/hackforla/website/wiki/project.md-file-template

Items for next week's agenda

(Will need update after this week) DA to BW: updated Wins development guide with "Why we built the Wins page" and "Issue Writing Guidelines" sections (updated following ChatGPT suggestions)

Edit by JC: The contents of this comment below has been placed in ER: Refactor Value Info and Program Area & Project Pages #8840.
We need a new large issue (if one does not already exist) for refactoring:

_layouts/project.html so that it no longer uses the old code in the project files, but instead uses how they will be refactored. Currently this is what the code looks like

website/_layouts/project.html

Lines 100 to 123 in 68d18a3

    
           <!--Project Value Card--> 
        
           {% if page.problem %} 
        
           <div id='project-value-card' class='page-card card-primary page-card-lg page-card--project-description-page'> 
        
               <h2 class='project-page-card-title title6'>Value</h2> 
        
               <div class='project-page-value-description'> 
        
                   <div class='sdg-grid-item'> 
        
                       <p><strong>Problem</strong></p> 
        
                       <p>{{ page.problem }}</p> 
        
                       <p><strong>Solution</strong></p> 
        
                       <p>{{ page.solution }}</p> 
        
                       <p><strong>Impact</strong></p> 
        
                       <p>{{ page.impact }}</p> 
        
                   </div> 
        
                   {%- assign background_color = page.sdg-color-variable |  replace_first: "$", "background-" -%} 
        
                   <div class='sdg-description-card {{ background_color }}'> 
        
                       <h2 class='sdg-card-title title7'>Sustainable Development Goal</h2> 
        
                       <div class='sdg-description-wrapper'> 
        
                           <img class='sdg-img' src='{{ page.sdg-image-src }}'> 
        
                           <div class='sdg-description-grid-item'>{{ page.sdg }}</div> 
        
                       </div> 
        
                   </div> 
        
               </div> 
        
           </div> 
        
           {% endif %}

program area cards that appear on the program area pages https://github.com/hackforla/website/blob/gh-pages/_includes/program-area-pages-cards.html
project files that have a problem section with the following layout

# program area card data
problem: The city produces a data set from all the 311 tickets placed. This data is useful if you are a data scientist, but for citizens without this training it has little value.
solution: We partnered with the Los Angeles Department of Neighborhood Empowerment and LA Neighborhood Councils to co-create and iterate analysis and tools (see 311-Data.org) to provide neighborhoods with actionable information at the local level through real time visualizations and comparison tools.
impact: Neighborhood Councils are able to use visualizations to demonstrate and discuss the city service levels with constituents and determine where to send mailings to target information to those parts of their community not availing themselves of specific city services.
sdg: '<strong>16.8:</strong> Broaden and strengthen the awareness and participation of City and local communities, especially those traditionally underserved and marginalized, in the institutions of local and global governance.'
sdg-image-src: /assets/images/sdg/sdg16.svg
sdg-image-alt: '16: peace, justice and strong institutions'
sdg-color-variable: $color-sdg16

and replace them with the new layout from https://github.com/hackforla/website/wiki/project.md-file-template

# Value (used on program area page cards, project pages, eventually SDG pages)
# What problem this project addresses
problem: 
# How this project provides a solution to the problem
solution:
# The impact of this project 
impact: 
# Sustainable Development Goals (SDGs)
sdgs:
    # The Sustainable Development Goal (SDG) this project falls under (e.g. 9)
  - goal-number: 1
    # The Sustainable Development Goal (SDG) target (e.g. "b")
    target:
      - "2"
      - "5.3"
      - "a"
      - "b.1"
  - goal-number:
    target:
  - goal-number:
    target:

List of projects that have the old format

engage https://github.com/hackforla/website/blob/gh-pages/_projects/engage.md
311 data https://github.com/hackforla/website/blob/gh-pages/_projects/311-data.md
lucky parking https://github.com/hackforla/website/blob/gh-pages/_projects/lucky-parking.md
open community survey https://github.com/hackforla/website/blob/gh-pages/_projects/open-community-survey.md
access the data https://github.com/hackforla/website/blob/gh-pages/_projects/access-the-data.md

From the https://github.com/hackforla/sdg-info/blob/main/README.md

Currently it says

# How to contribute 

This repository is managed by the website team.  

- See our getting started page on how to join Hack for LA https://www.hackforla.org/getting-started.
- Join the website team
- If you want to be assigned to an existing issue
  - In the proceess of working your way up the ladder of issues, pick up a ticket with the label [`p-feature: SDGs` on prioritized backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22p-feature%3A+sdgs%22#column-7198257)
- If you have noticed something that need to be made into an issue
  - Make sure the issue does not exist yet by reviewing all our open issues with the label [`p-feature: SDGs`](https://github.com/hackforla/website/labels/p-feature%3A%20SDGs)
  - [Create an Emergent Request Issue](https://github.com/hackforla/website/issues/new?assignees=&labels=Complexity%3A+Missing%2C+ER%2C+Feature+Missing%2C+role+missing%2C+size%3A+0.25pt&projects=&template=emergent-request.md&title=ER%3A+%5Breplace+with+info+%5D+)

It should say

# How to contribute 

If you notice something that could be improved and want to submit a PR or just bring it to our attention, please do the following

- Make sure the improvment does not already exist in an issue by reviewing all our open issues on this repo https://github.com/hackforla/sdg-info/issues
- If an issue does not already exist.  Please create an issue using [the 1 - Hack for LA Issue Template ](https://github.com/hackforla/sdg-info/issues/new?template=1---hack-for-la-issue-template.md)
- If you are a member of Hack for LA
   - if this issue is related to a project you are working on at Hack for LA, you will want to add the issue link to your project board
   - message in the Admin Slack channel with a link to the issue to let us know that you have placed the issue so we can prioritize it or comment on it.  Once it receives approval you can submit a PR against it.  Do not submit a PR against it, unless it receives approval to proceed.
- If you are not a member of Hack for LA
   - message us on the Hack for LA LinkedIn https://www.linkedin.com/company/hack-for-la, with a link to your issue.  Make sure you are following us, so we can write back.

## Q & A  
- Q: Why might it not receive approval?  
- A: The repo is beig used by the Hack for LA website team, to deliver images of the SDGs and text details about them (Goals, Targets, and Indicators), to webpages.  Before we can approve the change, we will need to verify that it won't break anything on that repo.

2026-10-19 Meeting Agenda

Prework to prep for meeting

Recurring items:

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

zkess: Can we move forward on updating the TDM Calculator project description? Update Project Profile: TDM Calculator (Update Project's Description) #8821
DA to BW: Updating Wins scripts to use the new project board requires adding 'project' scope to elizabethhonest bot token - came up in issue Update wins data to be posted to new project board #8701
DA to BW: do we use Project .status-Rebooting
- BW: Where are you seeing it?
  - DA: There's a color set for it in a few Sass files for the Projects pages. No projects currently have that status though.
HackforLABot: Review Inactive Team Members
JC: ER: Refactor Value Info and Program Area & Project Pages #8840 - For labeling, are we labeling for the person who is going to write the issue from the ER or for the resultant issue, specifically for role and size labels?

Notes from meeting

ER: [Toolkit Page]: Fix "undefined" message shown when filter selects no guide or resource cards #8819 took out of ready to prioritize, and wrote author a note
On ERs
- size labels is how long it took to write the ER, and how long it takes to write the issue.
- role label is what role it will take to solve the issue that the er is about.
  - if the person writing the ER does not know who should solve it, they leave it role: missing and merge team can decide
We need to close inactive team members skills issue when they reach terminal inactivity.
BW asked MH to look at automation on the roster for the cutoff of when a member becomes in active, and add documentation to the merge team responsibilities to indicate that is when a team members skills issue should be unassigned and closed so that new merge team members going forward will know that is part of the responsibility on the merge team task assignment spreadsheet.

Tasks

Please let author of 8819 know about the request
We need to close inactive team members skills issue when they reach terminal inactivity.

Items for next week's agenda

(Will need update after this week) DA to BW: updated Wins development guide with "Why we built the Wins page" and "Issue Writing Guidelines" sections (updated following ChatGPT suggestions)

Navigation Menu

Repository navigation

HfLA: 2026 Dev/PM Agenda and Notes #8442

Overview

Action Items

Resources/Instructions

Template

Resources

Previous Agendas

Prior and upcoming meetings

2026-10-19 Meeting Agenda

Prework to prep for meeting

88 remaining items

2026-10-12 Meeting Agenda

Prework to prep for meeting

Recurring items:

FYIs (nothing needs to be done, just keeping each other informed)

New Items

Notes from meeting

Tasks

JC's

Items for next week's agenda

2026-10-19 Meeting Agenda

Prework to prep for meeting

Recurring items:

FYIs (nothing needs to be done, just keeping each other informed)

New Items

Notes from meeting

Tasks

Items for next week's agenda

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	<!--Project Value Card-->
	{% if page.problem %}
	<div id='project-value-card' class='page-card card-primary page-card-lg page-card--project-description-page'>
	<h2 class='project-page-card-title title6'>Value</h2>
	<div class='project-page-value-description'>
	<div class='sdg-grid-item'>
	<p><strong>Problem</strong></p>
	<p>{{ page.problem }}</p>
	<p><strong>Solution</strong></p>
	<p>{{ page.solution }}</p>
	<p><strong>Impact</strong></p>
	<p>{{ page.impact }}</p>
	</div>
	{%- assign background_color = page.sdg-color-variable \| replace_first: "$", "background-" -%}
	<div class='sdg-description-card {{ background_color }}'>
	<h2 class='sdg-card-title title7'>Sustainable Development Goal</h2>
	<div class='sdg-description-wrapper'>
	<img class='sdg-img' src='{{ page.sdg-image-src }}'>
	<div class='sdg-description-grid-item'>{{ page.sdg }}</div>
	</div>
	</div>
	</div>
	</div>
	{% endif %}

HfLA: 2026 Dev/PM Agenda and Notes #8442

Description

Overview

Action Items

Resources/Instructions

Template

Resources

Previous Agendas

Prior and upcoming meetings

2026-10-19 Meeting Agenda

Prework to prep for meeting

Activity

88 remaining items

JessicaLucindaCheng commented on Oct 12, 2026

2026-10-12 Meeting Agenda

Prework to prep for meeting

Recurring items:

FYIs (nothing needs to be done, just keeping each other informed)

New Items

Notes from meeting

Tasks

JC's

Items for next week's agenda

ExperimentsInHonesty commented on Oct 12, 2026

ExperimentsInHonesty commented on Oct 12, 2026

ExperimentsInHonesty commented on Oct 12, 2026

zkess commented on Oct 15, 2026

daras-cu commented on Oct 16, 2026

JessicaLucindaCheng commented on Oct 19, 2026

2026-10-19 Meeting Agenda

Prework to prep for meeting

Recurring items:

FYIs (nothing needs to be done, just keeping each other informed)

New Items

Notes from meeting

Tasks

Items for next week's agenda

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions