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

[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: Enhance wins sheets to support selection for homepage randomizer #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, Research and recommend best practice for using quotes around text in .md files #7565 (comment)
• BW to RW: Where are we add with the daniel ridge bot Daniel Ridge Bot issue template for updates requested needs to be improved 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: Enhance wins sheets to support selection for homepage randomizer #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: Counting Activities in a PR as Activity Credit in Its Linked Issue #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

[ExperimentsInHonesty]

2024-10-14 and Continued on 2024-10-21 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)

• JC: Reminder I will not be attending the the meeting today and Monday, October 21. I will still be working on issues and can be reached on Slack. Thanks.

New Items

add issue numbers to be discussed and any notes that will be helpful

• BW: Check to see if he responded, Research and recommend best practice for using quotes around text in .md files #7565 (comment)
• BW to RW: Where are we add with the daniel ridge bot Daniel Ridge Bot issue template for updates requested needs to be improved 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: 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: Enhance wins sheets to support selection for homepage randomizer #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: 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: Discuss the buddy sheet with dev leads
• BW to RW: can you review this and see if we can close this issue. it still needs to be added to https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki
• BW to RW: its been 3 weeks on this issue Remove api-actionnetwork.js script from default markdown layout template #7091
• 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 that 'fixed' these issues: Update codeql.yml to automatically create new CodeQL issues #6503
    • CodeQL considered these fixed and closed the alerts but it is unclear why. It might be (?) because this hasn't been a problem for the major browsers since 2021 or earlier.
    • We could reopen the issues and do the changes anyway
• 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 to WG: Refactor GHA sort-closed-issues.js to use label-directory.json #7530 (comment)
  • WG response: I updated with your notes
• BW: let's review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• JC to BW: ER: Headers Are Different Heights From the Top Navigation Bar in Mobile Views #7510 (comment)
• JC to BW: ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 (comment)
• BW to JC: Please review this draft ER: Unexpected Website Deployment in Forked Repo #6689 (comment)
  • JC answer: Reviewed it and moved it to the Done column. ER: Unexpected Website Deployment in Forked Repo #6689 (comment)

Notes from meeting

Tasks

carried forward from previous meeting 2024-09-23

• 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

carried forward from previous meeting 2024-10-07

• update the offboard issues to match Onboard & Offboard: Tech Leads and Merge team #2689
  • WG comments:
    • Done: Onboard & Offboard: Tech Leads and Merge team #2689
    • edited to reflect the automatic actions by "Schedule Monthly" workflow
    • Note that changes to the meeting invites, Figma access, 1Password, etc. would still need to be done manually
    • Done: Onboard & Offboard: Junior Developers #3175
    • No changes: Onboard & Offboard: Product #2688 and Onboard & Offboard: Tech Leads and Merge team #2689

New tasks from this meeting

• BW: Add important information about content on site to the wiki #1068 -to update issue with wiki stuff and move to prioritized backlog

Items for next week's agenda

For 2024-10-28 agenda

• JC to BW: See blockers in ER: Build a tool to verify activities of HfLA members #4186 (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?
• JC: Discuss November and December HfLA days off.

[JessicaLucindaCheng]

2024-10-28 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: Discuss November and December HfLA days off.
• BW: 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: Rollout Plan: Refactor code with img HTML tags to end without a slash #4362 (comment)
• BW: Brandoncyu is showing as inactive on the roster, but they have an
  • open prework Skills Issue: Developer: Brandon Yu #7331
    • WG:
      • Hi @ExperimentsInHonesty - they were listed as "Onboarded" on the Roster because they did not provide their GitHub Handle. I added their handle and now they are showing as "Active".
      • However, even though this person appears OK, "Schedule Monthly" needs an edit so that Skills Issues are closed- I am adding this to Maintenance and adjustments to "Schedule Monthly" workflow #7614
• RW: Updates to CONTRIBUTING.md to reflect changes in the Project Board and Skills Issue #7236
• RW: working on only one wins issue at a time
• BW to RW: Update Google Apps Script to generate wins data feed only on Change #4154 (comment)
• BW to RW: can you review this and see if we can close this issue. it still needs to be added to https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki
• BW to RW: Add new fields to WINS Display Review and _wins-data.json #5472 (comment)
• BW to RW: ER: additions to the "Hack for LA's GitHub Actions" wiki guide #2033
• BW to RW: Update Project Profile Card review issue template #7596
• BW to WG: Why is this person still showing up as active
  • Limeload's issues - no issues since late may
  • roster row 108
  • Pre-work Checklist: Developer: Shraddha Rao #6349 - essence sent her the skills update to the prework because it said she was active on the roster
  • it's possible she could benefit from having her prework reopened because she never got a medium issue??
  • WG Comments:
    • "Sch. Monthly" bot saw some activity after July 1 so Limeload was included on the Oct 1 "notify" list (instead of Sept 1), now scheduled for removal Nov 1.
    • I opened Maintenance and adjustments to "Schedule Monthly" workflow #7614 to adjust 'one month' detection after our July and December breaks.
• 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"
• BW: let's review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• JC: See blockers in How to delete a branch from the Website repo #6416 (comment)
• JC to BW: ER: Headers Are Different Heights From the Top Navigation Bar in Mobile Views #7510 (comment)
• JC to BW: ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 (comment)
• JC to BW: See blockers in ER: Build a tool to verify activities of HfLA members #4186 (comment)
• 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

Notes from meeting

Tasks

Carried forward from 2024-09-23 meeting

• 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

Carried forward from 2024-10-14 and 2024-10-21 meeting

• BW: Add important information about content on site to the wiki #1068 -to update issue with wiki stuff and move to prioritized backlog

New tasks from this meeting

Tasks for Product

• Refactor filter on Project's page to be reusable
  • We want to refactor the filter on the My projects page so that we can reuse it later on other pages (including toolkit). It should use a file that delineates the filters that should display.
• Create a new issue Rollout Plan: Refactor code with img HTML tags to end without a slash #4362 (comment)
• clean up the issue for updating projects level 1 issue making (not github handle issues) with

  Choose `Submit new issue` button
  

Items for next week's agenda

• JC to BW: See blockers in ER: Build a tool to verify activities of HfLA members #4186 (comment)
• JC and BW to WG: ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 (comment)

[ExperimentsInHonesty]

Add to next agenda

• BW to RW: Update wins.js so the Wins page uses icon-github.svg #6911 we tried a bunch of things... but we can't get it to work. Can you make it work, or do we need to move the svgs out of the includes folder and into the assets.
• DA to RW, BW: Google Apps Script: Add unique IDs as object keys for each wins entry #2385 (comment) - I believe this is ready to demo, but want to make sure the way I am generating IDs will not cause issues

[HackforLABot]

Review Inactive Team Members: #7684

Inactive members with open issues:

• MarcosG119: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266

[JessicaLucindaCheng]

2024-11-04 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

• RW: Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
• RW: Add new fields to WINS Display Review and _wins-data.json #5472
• RW: Update wins.js so the Wins page uses icon-github.svg #6911
• RW: ER: additions to the "Hack for LA's GitHub Actions" wiki guide #2033
• JC and BW to WG: ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 (comment)
• BW: let's review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• JC to BW: See blockers in ER: Build a tool to verify activities of HfLA members #4186 (comment)
• JC: Make "Learn more" Link Visible on Redesigned Homepage #7689 (comment)
• 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

Notes from meeting

Tasks

Carried forward from 2024-09-23 meeting

• 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

Carried forward from 2024-10-14 and 2024-10-21 meeting

• BW: Add important information about content on site to the wiki #1068 -to update issue with wiki stuff and move to prioritized backlog

Carried forward from 2024-10-28 meeting

Tasks for Product

• Refactor filter on Project's page to be reusable
  • We want to refactor the filter on the My projects page so that we can reuse it later on other pages (including toolkit). It should use a file that delineates the filters that should display.
• Create a new issue Rollout Plan: Refactor code with img HTML tags to end without a slash #4362 (comment)

New tasks from this agenda

• JC: Update ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 to implement counting activity on pr in its related issue. Then, after the pr activity is counted as activity in the issue, have to update and 2 weeks inactive labels be turned on for all issues.

Items for next week's agenda

• JC: Discuss managing the Tasks section of agendas/meeting notes. To prevent that section from getting too long,
  • Can we review it each month during the meeting on the first or second week (when there isn't an onboarding)? This can include
    • Seeing if the task is completed
    • Figuring out what to do next with uncompleted tasks (i.e. have someone write an ER or issue for it, leave it as a task, etc), especially for older tasks

[JessicaLucindaCheng]

2024-11-18 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

• BW to RW: She updated the draft pr she already had in Update wins.js so the Wins page uses icon-github.svg #6911 (comment)
• BW to RW: Add new fields to WINS Display Review and _wins-data.json #5472
• BW: epic: Refactor img tags in CONTRIBUTING.md to end without a slash #6453 (comment)
• WG Refactoring so that Template .md files use labelId values instead of labelName:
  • Upon issue creation, if a 'label' is not recognized it is ignored- so can't use labelIds directly in the 'labels' or other field
  • What would work: we could use a new template label placeholder label as a trigger, then substitute in labelIds we want- these would be contained by a comment in the template body so that the automation can see the information.
  • Example shown here
  • The proposed .md solution does not work with .ymls...
• WG: Info only: The "Update Label" automation shows three new labels created by two new devs: front end, back end/devOps, and role: front end/back end. I deleted the labels and put notes on the two devs' Skills Issues
• JC to WG: ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 (comment)
• BW: let's review these issues that say ready for dev lead, are not assigned to anyone and are not in the icebox
• JC: Discuss managing the Tasks section of agendas/meeting notes. To prevent that section from getting too long,
  • Can we review it each month during the meeting on the first or second week (when there isn't an onboarding)? This can include
    • Seeing if the task is completed
    • Figuring out what to do next with uncompleted tasks (i.e. have someone write an ER or issue for it, leave it as a task, etc), especially for older tasks
• BW to JC: where are the instructions for the issues that need wiki additions? ER: Improve testing instructions to "How to Review Pull Requests" page #6319
  • JC: Answer: https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki
• JC to BW: See blockers in ER: Build a tool to verify activities of HfLA members #4186 (comment)
• JC: Make "Learn more" Link Visible on Redesigned Homepage #7689 (comment)
• 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

Notes from meeting

Tasks

Carried forward from 2024-09-23 meeting

• 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

Carried forward from 2024-10-14 and 2024-10-21 meeting

• BW: Add important information about content on site to the wiki #1068 -to update issue with wiki stuff and move to prioritized backlog

Carried forward from 2024-10-28 meeting

Tasks for Product

• Refactor filter on Project's page to be reusable
  • We want to refactor the filter on the My projects page so that we can reuse it later on other pages (including toolkit). It should use a file that delineates the filters that should display.
• Create a new issue Rollout Plan: Refactor code with img HTML tags to end without a slash #4362 (comment)

Carried forward from 2024-11-04 meeting

• JC: Update ER: Counting Activities in a PR as Activity Credit in Its Linked Issue #4536 to implement counting activity on pr in its related issue. Then, after the pr activity is counted as activity in the issue, have to update and 2 weeks inactive labels be turned on for all issues.

New tasks from this agenda

Items for next week's agenda

[JessicaLucindaCheng]

2024-11-25 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

• BW to WG these issues wont let someone stay assigned
  • EPIC: Create issues to Update Project Profile: Expunge Assist #7321 (comment)
  • EPIC: Create Issues to update Project Profile: Home Unite Us #7362
• 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: where are the instructions for the issues that need wiki additions? ER: Improve testing instructions to "How to Review Pull Requests" page #6319
  • JC: Answer: https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki
• BW to JC: review the issues JC is assigned to and see how we can reduce her assignments
• BW to JC: is this spreadsheet resolved? Can we write depreciated on it? HfLA-Website: Task List Dev leads
  • Add comment either way to this issue Epic: Skills/Productivity Dashboard  #7539

Notes from meeting

Tasks

Carried forward from 2024-09-23 meeting

• 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

Carried forward from 2024-10-14 and 2024-10-21 meeting

• BW: Add important information about content on site to the wiki #1068 -to update issue with wiki stuff and move to prioritized backlog

Items for meeting's agenda

[HackforLABot]

Review Inactive Team Members: #7790