website icon indicating copy to clipboard operation
website copied to clipboard
verified publisher icon hackforla

HfLA: Dev/PM Agenda and Notes - 2025

Open ExperimentsInHonesty opened this issue 11 months ago • 33 comments

Overview

This issue tracks the agenda and notes for the Development/PM meeting

Action Items

  • [ ] Add the Date of the next meeting below
  • [ ] Link the Agenda/Notes from meeting

Resources/Instructions

Template

## [DATE IN YYYY-MM-DD FORMAT] Meeting Agenda

### Prework to prep for meeting
- [ ] Review the [QA]
- [ ] Review the [Questions column](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22).  Make sure that all issues have a ready for label by [questions column, excluding all `ready for...`](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+-label%3A%22ready+for+org+rep%22+-label%3A%22ready+for+product%22+-label%3A%22ready+for+dev+lead%22+-label%3A%22ready+for+merge+team%22)
   - [ ] [Ready for product](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+product%22)
   - [ ] [Ready for Dev Lead](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+dev+lead%22)
   - [ ] [ready for merge team](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+merge+team%22)
   - [ ] [ready for org rep](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=-label%3A%22away+on+hold%22+status%3A%22Questions+%2F+In+Review%22+label%3A%22ready+for+org+rep%22)
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
   - [ ] Check to see how new team members are doing 
      - [ ] Check 2 week inactive label on the in progress column 
         - [ ] [Frontend 2 weeks inactive](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%222+weeks+inactive%22++label%3A%22role%3A+front+end%22)
         - [ ] [Backend 2 weeks inactive](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%222+weeks+inactive%22+++label%3A%22role%3A+back+end%2Fdevops%22)
- [ ] Check 2 week inactive PRs
- [ ] Check all open pre-work developers checklists anywhere on the board AND any closed pre-work developers checklist in QA
   - [ ] If it's in New Issue Approval, see if the prework is `ready for milestone` meaning it is assigned to the person who opened the prework, has a role label, and is on the Project Board. 
      - [ ] [Front End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22feature%3A+onboarding%2Fcontributing.md%22+label%3A%22role%3A+front+end%22#column-15490305)
      - [ ] [Back End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22feature%3A+onboarding%2Fcontributing.md%22++label%3A%22role%3A+back+end%2Fdevops%22#column-15490305)
- [ ] Can we improve the prework template based on something we see as a pattern?  
- [ ] Cleanup any anomalies in the [dashboard ](https://lookerstudio.google.com/reporting/f42df1c1-99df-4fa1-b719-7e135168bfa3)
- [ ] Product reviews 
   - [ ] [`ready for product` for dev issues](https://github.com/hackforla/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22ready+for+product%22+-label%3A%22role%3A+design%22+-label%3A%22role%3A+legal%22+-label%3A%22role%3A+writing%22+-label%3A%22role%3A+product%22)
   - [ ] [`ready for prioritization`](https://github.com/hackforla/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22Ready+for+Prioritization%22)

### Recurring items: 
 - [ ] review any issues that are in the new issue approval column for 
    - [ ] [Front End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22#column-15235217)
    - [ ] [Back End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22#column-15235217)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each PM or Lead
       - [ ] [Bonnie](https://github.com/hackforla/website/issues/assigned/ExperimentsInHonesty)
       - [ ] [Danielle](https://github.com/hackforla/website/issues/assigned/daras-cu)
       - [ ] [Will](https://github.com/hackforla/website/issues/assigned/t-will-gillis)

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

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


### Notes from meeting

### Tasks

### Items for next week's agenda

Prior and upcoming meetings

All meetings from 2022 to 2025-01-20 are located here https://github.com/hackforla/website/issues/2607 2025-01-27 2025-02-03 2025-02-10 2025-02-24 2025-03-03 2025-03-10 2025-03-17 2025-03-31 2025-04-07 2025-04-14 2025-04-21 2025-04-28 2025-05-05 2025-05-12 2025-05-19 2025-06-02 2025-06-09 2025-06-16 2025-06-23

ExperimentsInHonesty avatar Jan 28 '25 01:01 ExperimentsInHonesty

2025-01-27 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] WG: Skills Issue problem see this Slack post

Notes from the meeting

Tasks

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

Items for next week's agenda

ExperimentsInHonesty avatar Jan 28 '25 01:01 ExperimentsInHonesty

Review Inactive Team Members: #7869

Inactive members with open issues:

  • GilbertQ: #2688
  • Thinking-Panda: #6319

t-will-gillis avatar Feb 01 '25 19:02 t-will-gillis

For next time:

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

t-will-gillis avatar Feb 01 '25 19:02 t-will-gillis

2025-02-03 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] JC to WG: Did you want to place a bug report with GitHub about the problems encountered in the Skills Issue (Ex #7847)?

  • [x] WG: Should we (or should I) create a new label Needs Reprioritization or similar?

    • This will make it easier to ID a previously-prioritized issue that the bot puts in "New issue approval" because a dev self-assigns (too many GFIs, etc.)

  • [x] WG: Propose to create a new label Ladder Redo (or something better!) so that devs who have been absent for a while can "restart the issue ladder", i.e. do 2 GFI's, do 1 Small again. Right now, they are being blocked by the automation since they did these issues in the past.

Notes from meeting

  • JC to WG: Did you want to place a bug report with GitHub about the problems encountered in the Skills Issue (Ex #7847)?
    • Discussed with Bonnie and Will and decided that the problem with the Skills Issue formatting, checkboxes, etc are because of an update by GitHub that is causing problems for all issues. So, for now, we will wait to see if GitHub fixes the problems and not do a bug report right now.
  • From the meeting, create label Status: Unassigned by Bot for issues that were previously prioritized but moved back to "New Issue Approval" by the bot.
  • We will not create a label for those wanting to redo the ladder, and we also don't want devs to repeat the ladder (except for a very good reason, which we can address when and if this is needed)
  • Also discussed that devs that are both Front end and Back end should work GFIs and Small issues as usual, and should then preferably work on a single Medium issue that is both Front + Back end, and only if this is not an option they can work on 1 Front Med + 1 Back Med.

Tasks

Items for next week's agenda

  • [ ] JC & WG: Discuss "Updates to Project Profile" Epics: should these be closed after the issues are made?
  • [ ] JC & WG: See #7305 "Create sub-issue"
    • [ ] JC: If the field "Sub-Issues Progress" is selected to be visible, you can see the progress bar for the epic on the board. See here for epic 7305.
  • [ ] JC & WG: Check coverage for
    • https://docs.google.com/spreadsheets/d/1phPsEd_RVjQlHI4hsPJVEqqi4Ua-4WI7lhXNggtuc24/edit?skip_itp2_check=true&pli=1&gid=63654157#gid=63654157
  • [ ] JC: How long does it take Slack posts in the Admin channel to respond to questions about employment verification letters?

JessicaLucindaCheng avatar Feb 03 '25 23:02 JessicaLucindaCheng

2025-02-10 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] JC & WG: Discuss "Updates to Project Profile" Epics: should these be closed after the issues are made?
  • [x] JC & WG: See #7305 "Create sub-issue"
    • [x] JC: If the field "Sub-Issues Progress" is selected to be visible, you can see the progress bar for the epic on the board. See here for epic 7305.
  • [x] JC & WG: Check coverage for
    • https://docs.google.com/spreadsheets/d/1phPsEd_RVjQlHI4hsPJVEqqi4Ua-4WI7lhXNggtuc24/edit?skip_itp2_check=true&pli=1&gid=63654157#gid=63654157
  • [x] JC: How long does it take Slack posts in the Admin channel to respond to questions about employment verification letters?

Notes from meeting

  • JC & WG: Discuss "Updates to Project Profile" Epics: should these be closed after the issues are made?
    • Answer from Bonnie: No, the "Updates to Project Profile" Epics will be closed after the issues have been prioritized.
  • JC: How long does it take Slack posts in the Admin channel to respond to questions about employment verification letters?
    • Answer from Bonnie: Usually daily.

Tasks

Items for next week's agenda

JessicaLucindaCheng avatar Feb 11 '25 00:02 JessicaLucindaCheng

2025-02-24 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] Info: Danielle onboarding as Developer Co-lead
  • [x] WG: Info only: Dependabot Security No. 1 & 2
    • I closed both as "Revoked" - the URL including the exposed API key returns "400: API key not valid..."
      Details

Notes from meeting

Tasks

Items for next week's agenda

JessicaLucindaCheng avatar Feb 18 '25 01:02 JessicaLucindaCheng

Review Inactive Team Members: #7958

Inactive members with open issues:

  • GilbertQ: #2688
  • duojet2ez: #6548

HackforLABot avatar Mar 01 '25 11:03 HackforLABot

DRAFT notes for next meeting:

  • From the Bot notice: Member 'duojet2ez' I manually removed
    • Related issue #6548 - I ice-boxed this, think it should be closed as not planned. Several members have tried resolving already. I think this is a minor problem that is not worth fixing in the way we are asking.
  • Member 'sj-pers' - sent msg on Slack: no Skills Issue or other activity? Was added to team in February 4th apparently.
  • Member 'varyad` - #3785. They are asking to be reactivated after bot removal, I messaged that they need to attend another onboarding.
  • Member recently assigned themselves the old Dev Pre-work template (not Skills Issue) #7949. Should we remove this template or are we still using?
  • Random- should #6689 be closed?

So these don't get buried, these are Draft issues assigned to inactive members:

  • #7668, #7636
  • #6904 ditto
  • #5654 ditto

t-will-gillis avatar Mar 01 '25 22:03 t-will-gillis

2025-03-03 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] WG: From the Bot notice: Member 'duojet2ez' I manually removed
    • [x] Related issue #6548 - I ice-boxed this, think it should be closed as not planned. Several members have tried resolving already. I think this is a minor problem that is not worth fixing in the way we are asking.
  • [x] WG: Member 'sj-pers' - sent msg on Slack: no Skills Issue or other activity? Was added to team in February 4th apparently.
  • [x] WG: Member 'varyad` - #3785. They are asking to be reactivated after bot removal, I messaged that they need to attend another onboarding.
  • [x] WG: Member recently assigned themselves the old Dev Pre-work template (not Skills Issue) #7949. Should we remove this template or are we still using?
  • [x] WG: Random- should #6689 be closed?
  • [x] WG: So these don't get buried, these are Draft issues assigned to inactive members:
    • [x] #7668, #7636
    • [x] #6904 ditto
    • [x] #5654 ditto

Notes from meeting

  • WG said https://github.com/hackforla/website/issues/6548 - I ice-boxed this, think it should be closed as not planned. Several members have tried resolving already. I think this is a minor problem that is not worth fixing in the way we are asking.
    • BW says: if we don't do the issue, then how are we going to deal with the code ql notifications?
  • WG said: Member 'sj-pers' - sent msg on Slack: no Skills Issue or other activity? Was added to team in February 4th apparently.
    • BW: they filled out the form on for the website team, but didn't do the rest, so remove them from all website assets except read team.
  • WG: Member 'varyad` - https://github.com/hackforla/website/issues/3785. They are asking to be reactivated after bot removal, I messaged that they need to attend another onboarding.
    • BW says: I wrote to them to ask they why they wanted to reopen issue since they have not ever contributed a good first issue.
  • WG: Random- should https://github.com/hackforla/website/issues/6689 be closed?
    • JC: Yes, it can be closed. BW closed it.

Tasks

  • [x] JC will delete the old prework template.
    • Completed. See https://github.com/hackforla/website/pull/7965.

Items for next week's agenda

  • [ ] Check on this person next week https://github.com/hackforla/website/issues/3785#issuecomment-2695932030

JessicaLucindaCheng avatar Mar 03 '25 23:03 JessicaLucindaCheng

For discussion at next meeting:

mugdhchauhan avatar Mar 10 '25 19:03 mugdhchauhan

2025-03-10 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

JessicaLucindaCheng avatar Mar 10 '25 23:03 JessicaLucindaCheng

For next meeting:

  • WG:
  • MC: To demo results from #3228.
    • WC: IN_PROGRESS_COLUMN_ID is obsolete- can be deleted

t-will-gillis avatar Mar 15 '25 01:03 t-will-gillis

2025-03-17 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • DA: Spoke with Danielle Andrews, she has already joined another team so will not be joining the merge team.

New Items

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

  • [x] MC: To demo results from #3228.
    • [x] WG: IN_PROGRESS_COLUMN_ID is obsolete- can be deleted
  • [x] DA: Wrapping up #2385, access to Google Drive with Wins form and spreadsheet
    • [x] #7707 David has not been active, can we assign a merge team member or dev ready for large issue a Wins issue for them to test updated instructions? (Maybe #5472)
  • [x] WG: There are some open issues with inactive members:
    • #1674
    • #6319
    • #6919
    • #7540
    • #7565
    • #7636

Notes from meeting

Tasks

Items for next week's agenda

JessicaLucindaCheng avatar Mar 17 '25 22:03 JessicaLucindaCheng

2025-03-31 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] WG: Slack 'hfla-site-merge': Remove "Kirsten Cardon", Remove "Niki Prasadh"
  • [x] WG: Skills Issues, Table of Contents section 14.1: "Issue Making - Level 1 (Medium)" not Level 2?

Notes from meeting

  • What to do with Update Project Profile ERs:
    • For each requested change, check that an issue has been created for it.
    • Make sure all the issues created from the Update Project Profile ERs are added to the ER as a sub-issue.
    • Once all the issues for the requested changes have been made, the ER can be closed with the note to the author to check the sub-issues
    • Once the ER is closed, for each sub-issue author, add them back as assignees to the ER so they get credit.

Tasks

  • [x] JC: Put the "Update Project Profile ERs" notes from this meeting into a issue and make it into a template at the top similar to agendas.
    • Completed: https://github.com/hackforla/website/issues/8054
  • [ ] JC: Review and prioritize
    • [ ] Update project profiles
      • [ ] Issues
      • [ ] ERs
      • [ ] Update template for creating these issues as needed but leave the initiating ER linking the Resources section
    • [ ] Add github-handle issues
  • [ ] WG: Review and prioritize
    • [ ] VSCode issues

Items for next week's agenda

  • [ ] WG to DA & BW: Skills Issue - Developer
    • [ ] Discuss reducing the number of PR reviews needed per complexity level (gfi, small, etc).
    • [ ] Discuss change or remove 14.1 Issue making medium level 1.

JessicaLucindaCheng avatar Mar 18 '25 01:03 JessicaLucindaCheng

Review Inactive Team Members: #8034

Inactive members with open issues:

  • roslynwythe: #5005

HackforLABot avatar Apr 01 '25 11:04 HackforLABot

For next:

  • [ ] WG: #7927 This user is not on any HfLA team.
  • [ ] WG: Wins form changes- google-apps-scripts/wins-form-responses/Code.js references Column IDs, needs revision

t-will-gillis avatar Apr 01 '25 16:04 t-will-gillis

2025-04-07 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] FYI: JC is not attending 2025-04-14 meeting.

New Items

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

  • [x] WG: Wins form changes- google-apps-scripts/wins-form-responses/Code.js references Column IDs, needs revision
  • [x] WG to DA & BW: Skills Issue - Developer
    • [x] Discuss reducing the number of PR reviews needed per complexity level (gfi, small, etc).
    • [x] Discuss change or remove 14.1 Issue making medium level 1.

Notes from meeting

  • WG: Wins form changes- google-apps-scripts/wins-form-responses/Code.js references Column IDs, needs revision
    • DA says the only Column ID being used is "In Review" column IDs.
    • Solution:
      • WG: Write an ER to create a GHA to move issues with the label new-win-submission to the "Questions/In Review" column.
      • DA: Write an ER to edit google-apps-scripts/wins-form-responses/Code.js and the actual Google Apps Script to remove Columns IDs from the code and comments. The resultant issue from this ER will have https://github.com/hackforla/website/issues/7707 in its Dependency section.
  • WG & DA to BW: Skills Issue - Developer
    • Discuss reducing the number of PR reviews needed per complexity level (gfi, small, etc) because there aren't that many PRs being created and reviewing enough PRs is becoming a blocker for some junior developers.
      • Currently 5 GFI PR reviews but suggest 3-4 pr reviews
      • Currently 3 small PR reviews but suggest 2 pr reviews
      • Currently 3 medium PR reviews but suggest 2 pr reviews
    • Discuss change or remove 14.1 Issue making medium level 1.
      • DA: Since this 14.1 is optional and only needed if there are no medium issues, we can leave this.
      • DA suggests possibly remove 16 since we usually don't have that level 2 GFI ERs.

Tasks

From 2025-03-31

  • [ ] JC: Review and prioritize
    • [ ] Update project profiles
      • [ ] Update template for creating these issues as needed but leave the initiating ER linking the Resources section
        • [ ] Update template in https://github.com/hackforla/website/issues/7478#issuecomment-2357066233
        • [ ] Update issue template Project Profile leader updates - Add
        • [ ] Update issue template Project Profile leader updates - Remove
      • [ ] Issues
      • [ ] ERs
    • [ ] Add github-handle issues
  • [x] WG: Review and prioritize
    • [x] VSCode issues

From this agenda

  • [ ] WG: Write an ER to create a GHA to move issues with the label "new-win-submission" to the "Questions/In Review" column.
    • [ ] WG: See #8055
  • [ ] DA: Write an ER to edit google-apps-scripts/wins-form-responses/Code.js and the actual Google Apps Script to remove Columns IDs from the code and comments. The issue created from this ER will have https://github.com/hackforla/website/issues/7707 in its Dependency section. (WG to DA: the ER I wrote #8055 overlaps here, but we can talk about it)

Items for next week's agenda

  • [ ] JC to DA & WG: https://github.com/hackforla/website/issues/6598#issuecomment-2707979265 and https://github.com/hackforla/website/issues/6598#issuecomment-2752517418: Did someone get back to her?
  • [ ] WG to BW: #7927 This user is not on any HfLA team.
  • [ ] WG & DA to BW: Skills Issue - Developer
    • [ ] Discuss reducing the number of PR reviews needed per complexity levels gfi, small, and medium because there aren't that many PRs being created and reviewing enough PRs is becoming a blocker for some junior developers.
      • [ ] Currently 5 GFI PR reviews. Suggest changing to 3-4 pr reviews.
      • [ ] Currently 3 small PR reviews. Suggest changing to 2 pr reviews.
      • [ ] Currently 3 medium PR reviews. Suggest changing to 2 pr reviews.
    • [ ] WG: Discuss change or remove 14.1 Issue making medium level 1.
      • [ ] DA: Since this 14.1 is optional and only needed if there are no medium issues, we can leave this.
      • [ ] DA suggests possibly removing 16 since we usually don't have level 2 GFI ERs.

JessicaLucindaCheng avatar Apr 07 '25 22:04 JessicaLucindaCheng

2025-04-14 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] JC to DA & WG: https://github.com/hackforla/website/issues/6598#issuecomment-2707979265 and https://github.com/hackforla/website/issues/6598#issuecomment-2752517418: Did someone get back to her?
  • [x] WG to BW: #7927 This user is not on any HfLA team.
  • [x] WG & DA to BW: Skills Issue - Developer
    • [ ] Discuss reducing the number of PR reviews needed per complexity levels gfi, small, and medium because there aren't that many PRs being created and reviewing enough PRs is becoming a blocker for some junior developers.
      • [ ] Currently 5 GFI PR reviews. Suggest changing to 3-4 pr reviews.
      • [ ] Currently 3 small PR reviews. Suggest changing to 2 pr reviews.
      • [ ] Currently 3 medium PR reviews. Suggest changing to 2 pr reviews.
    • [ ] DA: Suggests possibly removing 16 since we usually don't have level 2 GFI ERs.

Notes from meeting

Tasks

From 2025-03-31

  • [ ] JC: Review and prioritize
    • [ ] Update project profiles
      • [x] Update template for creating these issues as needed but leave the initiating ER linking the Resources section
        • [x] Update template in https://github.com/hackforla/website/issues/7478#issuecomment-2357066233
        • [x] Update issue template Project Profile leader updates - Add
        • [x] Update issue template Project Profile leader updates - Remove
      • [ ] Issues
      • [ ] ERs
    • [x] Add github-handle issues

From 2025-04-07

  • [x] WG: Write an ER to create a GHA to move issues with the label "new-win-submission" to the "Questions/In Review" column.
    • [x] WG: See #8055
  • [x] DA: Write an ER to edit google-apps-scripts/wins-form-responses/Code.js and the actual Google Apps Script to remove Columns IDs from the code and comments. The issue created from this ER will have https://github.com/hackforla/website/issues/7707 in its Dependency section. (WG to DA: the ER I wrote #8055 overlaps here, but we can talk about it)

Tasks from today's meeting

Items for next week's agenda

JessicaLucindaCheng avatar Apr 14 '25 20:04 JessicaLucindaCheng

For next meeting:

  • WG: Info: This member kelwilson #8068 was not on website or website-write teams, but was added to the HfLA org and indicates they attended onboarding. --> I added them to the teams.

t-will-gillis avatar Apr 20 '25 18:04 t-will-gillis

2025-04-21 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] JC: I will not be attending the April 28th and May 5th Dev/PM meetings.

New Items

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

Notes from meeting

I sent the following message to Kelly in the #hfla-site Slack channel after I turned the form on. Please let admin know to turn off the website onboarding form, after Kelly uses it

Bonnie 2025-04-29 5:17 PM Kelly Besong I see that you attended onboarding but didn't finish the process. Please pick up from where you left off and work on the steps in this deck HfLA website engineer onboarding

Tasks

  • [ ] JC: Review and prioritize link to filtered project board
    • [ ] Update project profiles
      • [x] Remove the initiating ER linking in the Resources section
        • [x] Update template in https://github.com/hackforla/website/issues/7478#issuecomment-2357066233
        • [x] Update issue template Project Profile leader updates - Add
        • [x] Update issue template Project Profile leader updates - Remove
      • [ ] All open issues in all columns (start backwards) - only have New Issue Approval left
      • [ ] All open ERs in all columns (start backwards) - only have New Issue Approval left

Items for next week's agenda

  • [ ] JC: Check their response to this Slack message to Kelly Besong and make sure the form has been closed
  • [ ] DA to WG: Re #8055 GraphQL functions do work from Google Apps Script, but the current personal access token for Elizabeth Honest Bot will need more permissions

JessicaLucindaCheng avatar Apr 21 '25 21:04 JessicaLucindaCheng

2025-04-28 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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: Check their response to this Slack message to Kelly Besong and make sure the form has been closed
  • [x] DA to WG: Re #8055 GraphQL functions do work from Google Apps Script, but the current personal access token for Elizabeth Honest Bot will need more permissions

Notes from meeting

Tasks

Items for next week's agenda

JessicaLucindaCheng avatar Apr 22 '25 00:04 JessicaLucindaCheng

Review Inactive Team Members: #8105

Inactive members with open issues:

  • roslynwythe: #5005
  • dcotelessa: #6649
  • FamousHero: #7152

HackforLABot avatar May 01 '25 11:05 HackforLABot

Items for next agenda:

  • DA to BW: Turning Wins form into generic automation-current GitHub token storage in Google Doc vs Properties Service
  • DA to BW: Google-Form-to-GitHub repo already seems to be set up for new automation
  • DA to WG: GraphQL mutations work in Google Apps Script, elizabethhonest token will need project, public_repo, write:org permissions

daras-cu avatar May 05 '25 03:05 daras-cu

2025-05-05 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] DA to WG: GraphQL mutations work in Google Apps Script, elizabethhonest token will need project, public_repo, write:org permissions
  • [x] JC to WG: https://github.com/hackforla/website/issues/7760 - Noticed the HackforLABot is removing the "Draft" on issues in the New Issue Approval column.
  • [x] JC: Can we leave the issue writing for "Update Project Profile" ERs/Epics to junior developers at least for a time period?

Notes from meeting

  • DA to WG: GraphQL mutations work in Google Apps Script, elizabethhonest token will need project, public_repo, write:org permissions

    • DA says we should wait for the issue resulting from this ER https://github.com/hackforla/website/issues/8055 to be implemented and completed. Then the permissions for the elizabethhonest token can be updated.

  • JC: Can we leave the issue writing for "Update Project Profile" ERs/Epics to junior developers at least for a time period?

    • JC, WG, and DA spoke agreed yes and leave it for about 3 months, unless we are low on GFIs or other reasons for a lead or merge team member to write them.

Tasks

Items for next week's agenda

  • [ ] JC to BW: Check their response to this Slack message to Kelly Besong and make sure the form has been closed
  • [ ] DA to BW: Turning Wins form into generic automation-current GitHub token storage in Google Doc vs Properties Service
  • [ ] DA to BW: Google-Form-to-GitHub repo already seems to be set up for new automation
  • [ ] JC: Will there be a Dev/PM meeting on Memorial Day (May 26th)?
  • [ ] DA/WG to BW: Skills issues to review #7699 and #7745
  • [ ] JC: Since GitHub still hasn't fixed the nested checkbox problem, can we add a checkbox with instructions on how to edit the Skills Issue to check off items?

JessicaLucindaCheng avatar May 05 '25 23:05 JessicaLucindaCheng

For 5/12/25:

  • WG to BW: Daniel Franco no longer on merge team, needs to be removed from:

t-will-gillis avatar May 12 '25 02:05 t-will-gillis

2025-05-12 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] WG to BW: Daniel Franco no longer on merge team, needs to be removed from:
    • [x] Slack hfla-site-merge, remove "Daniel"
    • [x] Remove from 1Password
    • [x] Google Drive HfLA website Admin Remove "[email protected]" (I did not see a way to do it myself )
      • JC: I removed Daniel from the Admin drive.
      • [x] JC to WG: You need to be at the top level of the Drive and then you should be able to delete.
  • [x] DA to BW: Turning Wins form into generic automation-current GitHub token storage in Google Doc vs Properties Service
  • [x] DA to BW: Google-Form-to-GitHub repo already seems to be set up for new automation
  • [x] DA/WG to BW: Skills issues to review #7699 and #7745
  • [x] JC to BW: Check their response to this Slack message to Kelly Besong and make sure the form has been closed
    • [x] JC sent a message to see if Kelly completed the steps. --> Kelly completed the steps
  • [x] JC: Will there be a Dev/PM meeting on Memorial Day (May 26th)?

Notes from meeting

  • BW will not be attending the Sunday (May 25th) meeting and Dev/PM meeting on Monday (May 26th).

Tasks

  • [x] JC: Cancel Dev/PM meeting on Memorial Day (May 26th).
  • [ ] JC: https://github.com/hackforla/website/issues/3328 - after this issue an issue should be created to link each page to the Program Area pages with one line of code

Items for next week's agenda

  • [ ] JC: Since GitHub still hasn't fixed the nested checkbox problem, can we add a checkbox with instructions on how to edit the Skills Issue to check off items?
  • [ ] JC: Discuss website contents
  • [ ] JC: https://github.com/hackforla/website/issues/3328 - each page links to Program Area pages

JessicaLucindaCheng avatar May 12 '25 23:05 JessicaLucindaCheng

Issues that are needed before we make the GHAs available to other teams

  • #7769
  • #7562
  • #7423
  • #7421
  • #7417
  • #6649

ExperimentsInHonesty avatar May 13 '25 00:05 ExperimentsInHonesty

2025-05-19 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] BW: Issues that are needed before we make the GHAs available to other teams

    • #7769
    • #7562
    • #7423
    • #7421
    • #7417
    • #6649

  • [ ] WG: Here are some additional GHA-related issues/ ERs:

    • #8035
    • #8024
    • #7994
    • #7942
    • #6291
    • #4820
    • One more, however I strongly believe the following issue should not be worked on and should be closed. The short argument is that Merge Team needs to be looking at each PR individually and should not be relying on Project Board sorting to decide whether a PR should- or should not- be merged. The longer argument is on the issue itself.
      • #3112
      • #3227: This is for the Wiki and should be worked on.

  • [x] DA: #8147 (time sensitive)

Notes from meeting

Tasks

Items for next week's agenda

  • [ ] JC: Since GitHub still hasn't fixed the nested checkbox problem, can we add a checkbox with instructions on how to edit the Skills Issue to check off items?
  • [ ] JC: Discuss website contents
  • [ ] JC: https://github.com/hackforla/website/issues/3328 - each page links to Program Area pages

JessicaLucindaCheng avatar May 19 '25 19:05 JessicaLucindaCheng

Review Inactive Team Members: #8166

Inactive members with open issues:

  • roslynwythe: #5005
  • Cloid: #4388
  • jsnhn: #7642

HackforLABot avatar Jun 01 '25 11:06 HackforLABot

2025-06-02 Meeting Agenda

Prework to prep for meeting

Recurring items:

  • [ ] review any issues that are in the new issue approval column for
  • [ ] Accountability and Support Check.

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

  • [x] WG: Here are some additional GHA-related issues/ ERs:
    • #8035
    • #8024
    • #7994
    • #7942
    • #6291
    • #4820
    • One more, however I strongly believe the following issue should not be worked on and should be closed. The short argument is that Merge Team needs to be looking at each PR individually and should not be relying on Project Board sorting to decide whether a PR should- or should not- be merged. The longer argument is on the issue itself.
      • #3112
      • #3227: This is for the Wiki and should be worked on.
  • [x] DA: Unassign #5472 and offer to Donovan?
  • [x] JC: Is it okay to use "Listed in" GitHub feature for dependencies instead of adding a link in Resources section saying, "Issue A is dependent on the completion of this issue."? Example: https://github.com/hackforla/website/issues/7425
    • Notes:
      • Needs to be in the main issue body. If it is in a later comment, it doesn't list it.
      • Format: - [ ] hackforla/website/issues/7640 or - [ ] #7640
  • [x] JC: Strange user activity
  • [x] JC: Discuss website contents
  • [x] JC: https://github.com/hackforla/website/issues/3328
    • [x] Should this issue be completed on feature-homepage-launch branch or another branch?
    • [x] Dependencies
      • [x] https://github.com/hackforla/website/issues/7425

Notes from meeting

Tasks

Items for next week's agenda

  • [ ] JC: Since GitHub still hasn't fixed the nested checkbox problem, can we add a checkbox with instructions on how to edit the Skills Issue to check off items?

JessicaLucindaCheng avatar Jun 02 '25 20:06 JessicaLucindaCheng