HfLA: Dev/PM Agenda and Notes

[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](https://github.com/hackforla/website/projects/7#column-15490305)
- [ ] 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

2021-12-18
2022-01-02
2022-01-07
Note: The 2022-01-07 meeting agenda is in a comment before the 2022-01-02 meeting agenda.
2022-01-15
2022-01-22
2022-01-27
2022-01-29
2022-02-05
2022-02-12
2022-02-19
2022-02-26
2022-03-05
2022-03-12
2022-03-19
2022-03-26
2022-04-02
2022-04-16
2022-04-30
2022-05-07
2022-05-12
2022-05-28
2022-06-04

[ExperimentsInHonesty]

next meeting
I want to move the surveys in this folder but I don't want them to break. Lets test out the wins form
https://drive.google.com/drive/folders/1f3ReNv-uQ408JqQ4jwyufx78-E1yoNws?usp=sharing

[roslynwythe]

2024-07-08 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

• (Time sensitive, recurring agenda item) If there are any updates, discuss Epic: Project migration from classic to beta #3265.
• RW: ER: Find all the places that GitHub should be GitHub and fix #6161
• BW: Review this spreadsheet HfLA: Skills Dashboard

Notes from meeting

Tasks

Items for next week's agenda

Discuss the new onboarding project views https://github.com/orgs/hackforla/projects/86/views/15

[JessicaLucindaCheng]

2024-07-15 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

• (Time sensitive, recurring agenda item) If there are any updates, discuss Epic: Project migration from classic to beta #3265.
• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• BW: Discuss the new onboarding project views https://github.com/orgs/hackforla/projects/86/views/15
• JC: Wiki: Project Profile Issue Template #5630

Notes from meeting

Tasks

Items for next week's agenda

• BW: Continue to review this spreadsheet HfLA: Skills Dashboard
• BW: Discuss the new onboarding project views https://github.com/orgs/hackforla/projects/86/views/15

[JessicaLucindaCheng]

2024-07-22 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

• (Time sensitive, recurring agenda item) If there are any updates, discuss Epic: Project migration from classic to beta #3265.
  • WG: I submitted a PR to modularize three functions - one a query that finds an issue's GraphQL id, one that changes an issue's status, and the last one that is a reference that lists GraphQL ids for all status fields. Credit to moaz-dev1. Using these three modules, all of the previous functionality involving columns can be restored.
  • Post PBB migration: Refactor "Issue Trigger"  #7075 creates the modules and becomes a dependency for the remaining issues. The other issues (Post PBB migration: Refactor "Schedule Friday" workflow #7078 and Post PBB migration: Refactor "Move Closed Issues" workflow #7079) are in the "Ice Box" and are ready to be worked on after releasing the dependency. Closing Post PBB migration: Refactor "Pull Request Trigger" workflow #7076 as not needed.
• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• BW: Discuss the new onboarding project views https://github.com/orgs/hackforla/projects/86/views/15

Notes from meeting

Tasks

Items for next week's agenda

[JessicaLucindaCheng]

2024-07-29 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

• (Time sensitive, recurring agenda item) If there are any updates, discuss Epic: Project migration from classic to beta #3265.
  • WG: I submitted a PR to modularize three functions - one a query that finds an issue's GraphQL id, one that changes an issue's status, and the last one that is a reference that lists GraphQL ids for all status fields. Credit to moaz-dev1. Using these three modules, all of the previous functionality involving columns can be restored.
• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• RW: Research and Provide a Demo of Unit Testing for GHAs #7151

Notes from meeting

• We need more small and medium dev issues

Tasks

Items for next week's agenda

• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• BW: Check to see if David Responded Create Issues to add new variable github-handle for members in design-systems.md #6828
• WG: Create JSON file and related functionality for replacing hard-coded labels #6442 - add to meeting in 2 weeks

[JessicaLucindaCheng]

2024-08-05 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

• BW: Update Pre-work checklist template #4944
• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• BW: Check to see if David Responded Create Issues to add new variable github-handle for members in design-systems.md #6828
• BW to RW: Run VS Code Spell Checker on _includes/calendar.html #7144 (comment)

Notes from meeting

Tasks

Items for next week's agenda

• WG: Create JSON file and related functionality for replacing hard-coded labels #6442

[roslynwythe]

2024-08-12 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

Items from last week that may need attention

• BW: Update Pre-work checklist template #4944
• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• BW: Check to see if David Responded Create Issues to add new variable github-handle for members in design-systems.md #6828
• BW to RW: Run VS Code Spell Checker on _includes/calendar.html #7144 (comment)
• WG: Create JSON file and related functionality for replacing hard-coded labels #6442
• JC: We have separate ready for dev lead and ready for merge team labels but a role: dev leads label that covers both merge team members and tech leads. Should a separate role: merge team label be created?
  • Answer from BW: Yes

Notes from meeting

Tasks

Items for next week's agenda

• RW: Research and Provide a Demo of Unit Testing for GHAs #7151
  • should we create a new role for "qa" or "test"

[danielridgebot]

• RW: merged Updated Daniel Ridge workflows danielridgebot/check-ghpages-versions#23 but workflows still did not run so made some changes in a separate branch and now need to merge this PR: update Daniel Ridge PAT and release version files danielridgebot/check-ghpages-versions#24

[t-will-gillis]

2024-08-19 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

Items from last week that may need attention

• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• RW: Research and Provide a Demo of Unit Testing for GHAs #7151
• RW: merged Updated Daniel Ridge workflows danielridgebot/check-ghpages-versions#23 but workflows still did not run so I made some changes in a separate branch and now need to merge this PR: update Daniel Ridge PAT and release version files danielridgebot/check-ghpages-versions#24
  • When that is complete we can merge Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
• RW: GHPAGES-DOCKER needs to be updated - ruby gem ops#142
• WG: Update codeql.yml to exclude YAML front-matter and Liquid code #6548
• WG: Quick question about the key: value pairings for the label directory Create JSON file and related functionality for replacing hard-coded labels #6442. My thinking has been that the 'key' value should be similar to the actual label value: eg.:
  • 'key' is "2WeeksInactive" for the label 2 weeks inactive; key is "complexitySmall" for label Complexity: Small , etc.
  • Is this OK or do we want a completely abstracted key for each label? For example "label23": 2 weeks inactive, "label35": Complexity: Small, "label36": Complexity: Large, etc.

Notes from meeting

Tasks

Items for next week's agenda

[roslynwythe]

hackforla/ghpages-docker#3 (comment)

[roslynwythe]

2024-08-26 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

Items from last week that may need attention

• BW: (Continue to?) Review this spreadsheet HfLA: Skills Dashboard
• RW: Review message to merge team re: skills issues and 2 weeks inactive
• RW: local testing of new dockerhub image #7358
• WG: Update codeql.yml to exclude YAML front-matter and Liquid code #6548
• WG: Quick question about the key: value pairings for the label directory Create JSON file and related functionality for replacing hard-coded labels #6442. My thinking has been that the 'key' value should be similar to the actual label value: eg.:
  • 'key' is "2WeeksInactive" for the label 2 weeks inactive; key is "complexitySmall" for label Complexity: Small , etc.
  • Is this OK or do we want a completely abstracted key for each label? For example "label23": 2 weeks inactive, "label35": Complexity: Small, "label36": Complexity: Large, etc.
  • Update: PR for label directory submitted and ready for review

Notes from meeting

Tasks

Items for next week's agenda

[HackforLABot]

Review Inactive Team Members: #7374

Inactive members with open issues:

• MarcosG119: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
• Jung-GunSong: Add new fields to WINS Display Review and _wins-data.json #5472

[roslynwythe]

2024-09-02 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

New Items

• RW: Inconsistent Image Locations #1900
• RW: Add id value to yml collection #4146

Notes from meeting

Tasks

Items for next week's agenda

[JessicaLucindaCheng]

2024-09-09 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

New Items

• RW: about merge team
  • Nayan and Mario have resigned, offboard is in progress Onboard & Offboard: Tech Leads and Merge team #2689
  • John V : Skills Issue: Developer: John V. #7219 (comment)
  • Danielle : Skills Issue: Developer: Danielle Aras #6948 (comment)
• RW will not be able to lead Tuesday meetings
• Docker: delay in merging Dockerfile Update Dockerfile with ruby:3.3.4-alpine3.20 ghpages-docker#3
  • discussion - how will devs pull down the new image? Keep local Docker images up to date #3488
• ER: Unexpected Website Deployment in Forked Repo #6689
• JC: How do epics work now? Is it the following?
  1. An epic is written with action items to write child issues.
  2. Once an epic is prioritized, a developer assigns themselves to it and writes the child issues.
  3. Once Merge Team members have approved the epic and child issues, the epic is unassigned from the assignee and put in the Ice Box with a Dependency label. However, the developer gets credit because we will check the issues the developer authored.
  4. Once all the child issues are completed, the epic is closed without an assignee.
• JC to BW: Create each program area page automatically using a layout #3328 (comment)
• JC: Create each program area page automatically using a layout #3328 (comment)

Notes from meeting

Tasks

Items for next week's agenda

[JessicaLucindaCheng]

2024-09-16 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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: If someone active on the team needs time off but has a closed, old version of the pre-work, where should I tell them to put their time off statement? For reference, below are the procedures for taking time off from the team copied from the Skills Issue.

  <details><summary>If you need to take some time off from the team</summary>
    Copy and customize this response, and leave it in a comment on this issue
        ```
        I need to take some time off from the team.  I believe I will be back on [Replace with DATE YOU WILL BE BACK]
        ```
        - If you have put work in, please make sure its well documented.
           - Add the label `away on hold`
           - Move this issue to the questions column
        - if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.  
  </details>

• BW if no answer on this by the time we meet, let's unassign them and close as unplanned ER: Unexpected Website Deployment in Forked Repo #6689
• BW to RW: Research and Provide a Demo of Unit Test Implementation for HfLA Repo #2249 (comment) sure. What is the status of these?
  • Research and Provide a Demo of Unit Testing for GHAs #7151
  • Research and Provide a Demo of Unit Testing for front-end JavaScript code #7152
• BW to RW and WG: Update PR template with instructions regarding CodeQL annotations #5196
• BW to RW: what is the size level of CodeQL Alerts that are Closed as unplanned? I added a size label 0.25.
• BW to RW: Are these issues ready? RW: Yes they are ready
  • Create Issues to add new variable github-handle for members in not-today.md #7161
  • Create Issues to add new variable github-handle for members in new-schools-today.md #7159
• BW to RW: do you have questions about this, or do you want someone else to rewrite it? RW: please see my comment/question Remove api-actionnetwork.js script from default markdown layout templates #7091
• BW: what are the next steps for these issues
  • Create wiki page "How to manage spell check warnings" #6519
  • Considering using Prettier and research on setup via CL and Plugin #4059
• BW to RW: so can we close this? RW: Yes, closed Creating issues: Review GHAs in wiki pages #3229 (comment)
• BW: let's do the cleanup on these issues together during this meeting
  • ER: New Wiki Content for large issues #2033 (comment)
  • Google Apps Script: Migrate Wins Data - Stop generation of AF file #2147 (comment)
• BW to JC: is this question still outstanding? Create each program area page automatically using a layout #3328 (comment)
  • JC: Answer: No, it has been answered. I have updated the comment with the answer.
• BW to WG: Let's review this issue and see if we need to add a draft label or what is the next steps Epic: Refactoring GHA - JavaScript files to use common key: value JSON #6454
  • WG: Comment Just merged the Dependency Create JSON file and related functionality to support replacement of hard-coded issue labels #5205, and now starting with creating the issues from this Epic
• BW to JC: I would like to be able to put these Project profile change issues in the ER ready for making into issues column and add a template to a resource link, but I don't know how. Can we walk through it together?
• BW to JC: Are you going to make the new ER ER: Filters on project page #4530 (comment)?
  • JC: Answer: No. Since I am not assigned to it and it had a ready for merge team label, I thought someone on the Merge Team would do it.
• BW: Let's figure out next steps on this issue: Create a wiki page about best practices for maintaining GitHub secrets #3290
• BW: This issue needs a cleanup. Lots of its checkboxes are checked and there are a couple of comments VS Code Spell Checker Extension: GHA Messaging #4469
• BW to JC: checking on your progress on this issue Instructions for Viewing the Website through a Forked Repo's GitHub Pages #6219
  • JC: Answer: Issue update: Instructions for Viewing the Website through a Forked Repo's GitHub Pages #6219 (comment). See question under Blockers.
• BW: does this look good to you? Section 2.7e of CONTRIBUTING.md has code that will not work in terminal #7378
• BW to RW: Elliot has not answered you. I slacked him ER: Create documentation for reviewing CodeQL PRs #6904 (comment)

Items for next week's agenda

• JC to BW: Update Pre-work checklist template #4944 (comment)
• JC: Review Epic: Change _program-area Files From -card.yml to .md #7424 and its child issues:
  • JC: Write Issues to Change _program-area Files From -card.yml to .md #7383
  • JC: Approve of template Template for #7383: Change a _program-areas File From -card.yml to .md for [Insert the current name of the file].yml #7404
    • JC: Issue from template Change a _program-areas File From -card.yml to .md for citizen-engagement-card.yml #7425

[JessicaLucindaCheng]

2024-09-23 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • [ ] Bonnie
    • [ ] Roslyn

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

New Items

• BW: If no answer on this by the time we meet, let's unassign them and close as unplanned ER: Unexpected Website Deployment in Forked Repo #6689
• BW to RW: Research and Provide a Demo of Unit Test Implementation for HfLA Repo #2249 (comment) sure. What is the status of these?
  • Research and Provide a Demo of Unit Testing for GHAs #7151
• BW: Let's figure out next steps on this issue: Create a wiki page about best practices for maintaining GitHub secrets #3290
• BW: This issue needs a cleanup. Lots of its checkboxes are checked and there are a couple of comments VS Code Spell Checker Extension: GHA Messaging #4469
• BW to JC: checking on your progress on this issue Instructions for Viewing the Website through a Forked Repo's GitHub Pages #6219
  • JC: Answer: Issue update: Instructions for Viewing the Website through a Forked Repo's GitHub Pages #6219 (comment). See question under Blockers.
• BW: I onboarded Essence who is going to take over as the product owner / project manager, and will continue the important work of organizing our board and prioritizing work/issues
• BW: I made an issue with Essence and Rabia Create new issue templates for adding/removing single volunteers on a project page with instructions #7478 so that I could get all the project update requests, turned into Epics, so that other people could make issues out of them.
• BW: We have made some issues for projects to give us their accomplishments for the accomplishment page. We have created a new project board to track that Admin: Project Team Tasks, Accomplishment tab which will roll up to homepage launch #2481
• JC to BW: Update Pre-work checklist template #4944 (comment)
• BW to RW: what is the next step with this issue Keep local Docker images up to date #3488
  • Please see my recent comments
• RW: DO NOT MERGE: docker-compose.yml has been updated to pull the test image from dockerhub #7359

Notes from meeting

• posted in Slack for more reviewers for RWs pr DO NOT MERGE: docker-compose.yml has been updated to pull the test image from dockerhub #7359
• Lots of people caught in the assigning themselves to an issue when they have already done issues of that size. Possibly because they were author... which means we need to ask them to put draft label on first.

Tasks

Moved to this comment #2607 (comment)

Items for next week's agenda

• Introductions
• BW: If he is not interested in writing the DR, close as unplanned, if he is, leave open and make sure he is assigned, and it's in progress. ER: Unexpected Website Deployment in Forked Repo #6689
• BW to WG: Research and Provide a Demo of Unit Testing for GHAs #7151 (comment)
  • WG response: Issues are written for the dependency Epic: Refactoring GHA - JavaScript files to use common key: value JSON #6454. tbc
• JC: How do we want to move the SDG files?
• BW to JC: review the issues JC is assigned to and see how we can reduce her assignments
• BW to RW and WG: This issue was created via an automation. Its labeled as small, and ready for dev lead. Is that what we want? Resolve CodeQL Alert #55 - Generated by GHA #6826
  • WG response: Some questions/comments:
    • Is the code in the directory google-apps-script actually live? There is identical code from Google Apps Script- the Google Drive "Wins-form (Responses)"- that is triggered whereas I don't see anything that would trigger the repo code.
    • If the repo code is only a copy, is there a reason to include it in the repo as if it were functioning code?
    • Regardless, the alert fix is easy- I would vote to resolve it immediately instead of passing it to a dev
• BW: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
• BW to RW: I thought we had decided what to do on this issue, but I don't see any notes, so let's review again Google Apps Script: Add unique IDs as object keys for each wins entry #2385
• BW to RW: reviewing what the update to this issue is Keep local Docker images up to date #3488 (comment)
• RW to BW: Google Apps Script: Add automation for Homepage Summary spreadsheet #2505 (comment)
• BW: lets review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• BW to WG: These issues have a comment - is it possible to link it to the specific [dependabot PR](https://github.com/hackforla/website/pulls?
  • Resolve CodeQL alert 21 and 23 "Potentially unsafe external link" #6230 (comment)
  • Resolve CodeQL alert 5 and 7 "Potentially unsafe external link" #6226 (comment))?
    • update guidance to KG Skills Issue: qa engineer: Klavdia Goldshteyn #7232
  • WG response: I added the closest PR Update codeql.yml to automatically create new CodeQL issues #6503 that 'fixed' these issues (and one add'l Resolve CodeQL alert 22 and 24 "Potentially unsafe external link"  #6231), but I am unclear why CodeQL considered these alerts fixed after the PR. Also added note to Skills Issue: qa engineer: Klavdia Goldshteyn #7232
• BW to RW: we are closing these as no longer planned, but it does not track the time you spent on it, let's discuss/devise labels.

[JessicaLucindaCheng]

2024-09-30 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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
    • Bonnie
    • Roslyn

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

• JC: I will not be attending the meeting on October 21st.

New Items

• Introductions
• BW: If he is not interested in writing the DR, close as unplanned, if he is, leave open and make sure he is assigned, and it's in progress. ER: Unexpected Website Deployment in Forked Repo #6689
• BW to WG: Research and Provide a Demo of Unit Testing for GHAs #7151 (comment)
  • WG response: Issues are written for the dependency Epic: Refactoring GHA - JavaScript files to use common key: value JSON #6454. tbc
• BW to WG: These issues have a comment - is it possible to link it to the specific [dependabot PR](https://github.com/hackforla/website/pulls?
  • Resolve CodeQL alert 21 and 23 "Potentially unsafe external link" #6230 (comment)
  • Resolve CodeQL alert 5 and 7 "Potentially unsafe external link" #6226 (comment))?
    • update guidance to KG Skills Issue: qa engineer: Klavdia Goldshteyn #7232
  • WG response: I added the closest PR Update codeql.yml to automatically create new CodeQL issues #6503 that 'fixed' these issues (and one add'l Resolve CodeQL alert 22 and 24 "Potentially unsafe external link"  #6231), but I am unclear why CodeQL considered these alerts fixed after the PR. Also added note to Skills Issue: qa engineer: Klavdia Goldshteyn #7232
• BW to RW and WG: This issue was created via an automation. Its labeled as small, and ready for dev lead. Is that what we want? Resolve CodeQL Alert #55 - Generated by GHA #6826
  • WG response: Updated after meeting 9/30:
    • (Code in the directory google-apps-script is tied to Google Apps Script- the Google Drive "Wins-form (Responses)")
    • WG to review 6826.
• BW to RW: we are closing these as no longer planned, but it does not track the time you spent on it, let's discuss/devise labels.
  • JC: I copied this item from the previous agenda but didn't see any links or issues for it.
• BW to RW: I thought we had decided what to do on this issue, but I don't see any notes, so let's review again Google Apps Script: Add unique IDs as object keys for each wins entry #2385
• BW to RW: reviewing what the update to this issue is Keep local Docker images up to date #3488 (comment)
• RW to BW: Google Apps Script: Add automation for Homepage Summary spreadsheet #2505 (comment)
• BW: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
• BW: let's review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• JC: ER: Headers Are Different Heights From the Top Navigation Bar in Mobile Views #7510 (comment)
• JC: Remove an Extra Period in README.md 100Automations/futureautomations#53
  • Since this project is on hold who should I ask to merge this in 100 Automations? Bonnie merged it.
  • Once the pr is merged, since I don't have access to the Google Apps Script for the Google Form, should I just fill out the form again? Ans from BW: Just fill it out again.
• BW to JC: review the issues JC is assigned to and see how we can reduce her assignments
• JC: How do we want to move the SDG files?

Notes from meeting

Tasks

Items for next week's agenda

• JC: Are we meeting on Monday, October 14 (Indigenous Peoples' Day, Columbus Day)?

[JessicaLucindaCheng]

2024-10-07 Meeting Agenda

Prework to prep for meeting

• Review the QA
• 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

• JC: Are we meeting on Monday, October 14 (Indigenous Peoples' Day, Columbus Day)?
• BW: ER: Skills Issue link to PRs that require review #7528 I changed the branch settings so that it requires two approvals. That should stop the problem of people clicking on good first issue PRs, Review Required and finding no results, even though there are issues that only have one approving review. That won't help with the problem of there not being that many good first issues to review, though. Should I lower the number of reviews for good first issues that they are required to do?
• BW: Check to see if he responded, ER: Create issues so that we correctly use quotes around text in .md files #7565 (comment)
• BW to RW: Where are we add with the daniel ridge bot Daniel Ridge Bot updates requested ops#52 GHPAGES-DOCKER needs to be updated - ruby gem ops#142
• BW to RW: is there an issue to attach to this dependency Add ESlint VS Code installation instructions #4264. There is another issue that is dependent on it Identify and fix inconsistent code indentation in a SCSS file #2695
• BW to RW: Create "List" view on Project and Toolkit pages #6143 is this dependency resolved "HTML and JS Refactoring so that project and toolkit pages share elements"
  • yes
  • no
• BW to RW: Create issue template "Resolve Spell Check warning" #6446 - I just put this back into the new issue approval from icebox
• BW to RW: reviewing what the update to this issue is Keep local Docker images up to date #3488 (comment)
• RW to BW: Google Apps Script: Add automation for Homepage Summary spreadsheet #2505 (comment)
• BW to RW: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266 - are we ready to give him some instructions
• BW to RW: Add important information about content on site to the wiki #1068 - what is the next steps for this issue. Tell me and I'll add a note.
• BW to RW: This issue Epic: Refactor website header to provide accessible navigation #4300 is a blocker for this issue Accessibility Audit #1347, which is in turn a blocker for this issue Research impact of techniques in the WCAG 1.4.4. Guideline for resizing text  #4227
• BW to RW: This issue Epic: Refactor website header to provide accessible navigation #4300 is a blocker for this issue Accessibility Audit #1347, which is in turn a blocker for this issue Research impact of techniques in the WCAG 1.4.4. Guideline for resizing text  #4227
• BW to WG and RW: These issues have a comment - is it possible to link it to the specific dependabot PR?
  • WG Updates:
    • Resolve CodeQL alert 5 and 7 "Potentially unsafe external link" #6226 (comment))
    • Resolve CodeQL alert 21 and 23 "Potentially unsafe external link" #6230 (comment)
    • Resolve CodeQL alert 22 and 24 "Potentially unsafe external link"  #6231 (comment)
    • update guidance to KG Skills Issue: qa engineer: Klavdia Goldshteyn #7232
  • WG response:
    • I added the closest PR Update codeql.yml to automatically create new CodeQL issues #6503 that 'fixed' these issues
    • Note that CodeQL considered these alerts fixed and closed after the PR
    • It isn't immed. obvious why CodeQL closed the alert, however since 2021 this isn't problem for the major browsers
    • We could reopen the issues and do the changes anyway
• WG: Do any Leads/ others need to be added to the "Safe List" for the Google Drive?
  If so they or I can add their emails to the Safe List.
  • Venkatasai 'manager' accounts were removed b/c of inactivity.
    • add to safe
    • not on safe list
  • Poorna Tushara Chada 'manager' account were removed b/c of inactivity.
    • add to safe
    • not on safe list
  • Yugma Moradia's 'manager' accounts were removed b/c of inactivity.
    • add to safe
    • not on safe list
  • 'shaikhsrabia' is still on Safe List- should they be off now?
    • keep on safe list
    • remove from safe list
  • WG comment: Added "[email protected]" to Safe List
• WG: FYI only: I changed the default "Offboard template": a.) changed note about Roster: it should not "Mark as inactive" and b). rewrote notes under "GitHub": the person should not be removed from 'website-write', but do remove 'Maintainer' status for all teams
• WG: Edits to Slack 'hfla-site-merge': Remove Freaky Wrld, Mario Antonini, (Vanessa?)
• WG: is this ready? GHA: Sort pull requests to correct column #3112
  • WG response: I updated the links for the new Project Board, but would like to discuss:
    • Some of the statuses seem like renames- do we need new statuses for these or reuse existing? Also, there are existing Workflows to cover a couple of these status situations already- can we continue using?
    • Do we need/ want these statuses still? What I am thinking about is that sometimes the PRs don't follow a simple review path: Example would be PR with two approvals, then a third requesting changes. (Also, admittedly I don't use the Project Board to look at PRs, I always go directly to the Pull Requests page. I feel like each PR needs to be looked at individually regardless.)
• BW to WG: is she still on the team, is she going to make the changes that WG specified, if not, what's next ER: update the pull request contributing guidelines #6990
  • WG response: she is inactive. I made the edits that I suggested to the ER- I believe it is ready to be made into an issue.
• WG: Discuss draft ER: Discussion of processes for removal of inactives from issues, website team #7552
• WG: Could we talk briefly about members who are on hiatus, the away on hold label, and what exceptions we want from the GHAs? Eg The label description mentions "members who will be gone two weeks or less"
• JC to WG: Create GHA to add comments to prework issues documenting issues events #4820 (comment) - Did you want to determine what is to be done with this issue and its pr? Or did you want a Merge Team member to try to figure it out?
• BW: let's review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• BW to JC: Instructions for Viewing the Website through a Forked Repo's GitHub Pages #6219 the blocker was addressed at a prior meeting. What's next? Ans: The issue has been closed as completed.
• JC to BW: ER: Headers Are Different Heights From the Top Navigation Bar in Mobile Views #7510 (comment)
• JC to BW: See blockers in ER: Build a tool to verify activities of HfLA members #4186 (comment)
• JC to BW: ER: Automate update comment and labeling for issues with an open linked pr #4536 (comment)
• BW to JC: review the issues JC is assigned to and see how we can reduce her assignments
• JC: How do we want to move the SDG files?

Notes from meeting

• BW: ER: Skills Issue link to PRs that require review #7528 I changed the branch settings so that it requires two approvals. That should stop the problem of people clicking on good first issue PRs, Review Required and finding no results, even though there are issues that only have one approving review. That won't help with the problem of there not being that many good first issues to review, though. Should I lower the number of reviews for good first issues that they are required to do?

• BW: We decided for now to keep the number of reviews for good first issue at 5, but to ask people to not do more than 5, unless you are a merge team member who is approving/merging

Tasks

carried forward from previous meeting 2024-09-23

• JC Instructions for Viewing the Website through a Forked Repo's GitHub Pages #6219 will finalize decision record draft, changing the wording to be in their copy of Google App script
• BW will make a new issue Create new issue templates for adding/removing single volunteers on a project page with instructions #7478 (comment)
• BW and EG will make issues for projects to give us their accomplishments for the accomplishment page. We have created a new project board to track that Admin: Project Team Tasks, Accomplishment tab which will roll up to homepage launch #2481
• BW to integrate JCs new text into the skills issue, FAQ: Update Pre-work checklist template #4944 (comment)
• BW to work with EG on creating new issues
  • a new issue (add dependency of GHA variable file being done to rename all the labels all lowercase.
• BW to review the following links with EG:
  • Ready for Product - design, legal, writing
  • Ready for Prioritization
  • Ready for Merge team
  • Ready for Dev Lead

New tasks from this agenda

Items for next week's agenda

Notes from meeting

Tasks

Items for next week's agenda

[HackforLABot]

Review Inactive Team Members: #7553

Inactive members with open issues:

• MarcosG119: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
• Jung-GunSong: Add new fields to WINS Display Review and _wins-data.json #5472

[ExperimentsInHonesty]

• we decided for now to keep the number of reviews for good first issue at 5, but to ask people to not do more than 5, unless you are a merge team member who is approving/merging

Task list

• update the offboard issues to match Onboard & Offboard: Tech Leads and Merge team #2689

WG: FYI only: I changed the default "#2689": a.) changed note about Roster: it should not "Mark as inactive" and b). rewrote notes under "GitHub": the person should not be removed from 'website-write', but do remove 'Maintainer' status for all teams