Skip to content

HfLA: Dev/PM Agenda and Notes - 2025 #7859

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
2 tasks
ExperimentsInHonesty opened this issue Jan 28, 2025 · 22 comments
Open
2 tasks

HfLA: Dev/PM Agenda and Notes - 2025 #7859

ExperimentsInHonesty opened this issue Jan 28, 2025 · 22 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue feature: agenda role: dev leads Tasks for technical leads role: merge team Tasks for merge team members role: product Product Management size: 0.5pt Can be done in 3 hours or less
Milestone
08. Team workflow

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 28, 2025 •
edited by JessicaLucindaCheng
Loading

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 #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
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: Missing Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Jan 28, 2025
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jan 28, 2025 •
edited by JessicaLucindaCheng
Loading

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

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

Closed
2 tasks
@JessicaLucindaCheng JessicaLucindaCheng added feature: agenda role: product Product Management role: dev leads Tasks for technical leads role: merge team Tasks for merge team members Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing Complexity: Missing size: missing labels Jan 28, 2025
@t-will-gillis
Copy link
Member

Review Inactive Team Members: #7869

Inactive members with open issues:

@t-will-gillis

This comment has been minimized.

Sign in to view
@JessicaLucindaCheng JessicaLucindaCheng added this to the 08. Team workflow milestone Feb 3, 2025
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Feb 3, 2025 •
edited
Loading

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

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

  • 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.)

  • 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 Skills Issue: Developer: TEST #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

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Feb 11, 2025 •
edited
Loading

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

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 JessicaLucindaCheng moved this from New Issue Approval to Agendas in P: HfLA Website: Project Board Feb 11, 2025
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Feb 18, 2025 •
edited by ExperimentsInHonesty
Loading

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

  • Info: Danielle onboarding as Developer Co-lead
  • 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

@HackforLABot
Copy link
Contributor

Review Inactive Team Members: #7958

Inactive members with open issues:

@t-will-gillis

This comment has been minimized.

Sign in to view
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Mar 3, 2025 •
edited
Loading

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

Notes from meeting

  • WG said Update codeql.yml to exclude YAML front-matter and Liquid code #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` - Pre-work Checklist: Developer: Varun Yadav #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 ER: Unexpected Website Deployment in Forked Repo #6689 be closed?
    • JC: Yes, it can be closed. BW closed it.

Tasks

Items for next week's agenda

@mugdhchauhan
Copy link
Member

For discussion at next meeting:

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Mar 10, 2025 •
edited by ExperimentsInHonesty
Loading

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

@t-will-gillis

This comment has been minimized.

Sign in to view
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Mar 17, 2025 •
edited by t-will-gillis
Loading

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

Notes from meeting

Tasks

Items for next week's agenda

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Mar 18, 2025 •
edited
Loading

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

  • WG: Slack 'hfla-site-merge': Remove "Kirsten Cardon", Remove "Niki Prasadh"
  • 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

  • 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.
  • 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.

@HackforLABot
Copy link
Contributor

Review Inactive Team Members: #8034

Inactive members with open issues:

@t-will-gillis

This comment has been minimized.

Sign in to view
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 7, 2025 •
edited
Loading

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)

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

New Items

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

  • WG: Wins form changes- google-apps-scripts/wins-form-responses/Code.js references Column IDs, needs revision
  • 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.

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 Update documentation for wins_data #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

From this agenda

Items for next week's agenda

  • JC to DA & WG: Pre-work Checklist: Developer: Danielle Andrews #6598 (comment) and Pre-work Checklist: Developer: Danielle Andrews #6598 (comment): Did someone get back to her?
  • WG to BW: Skills Issue: Developer: Kartik Nesari #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 JessicaLucindaCheng mentioned this issue Apr 7, 2025
Closed
16 tasks
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 14, 2025 •
edited
Loading

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

Notes from meeting

Tasks

From 2025-03-31

From 2025-04-07

Tasks from today's meeting

Items for next week's agenda

@t-will-gillis

This comment has been minimized.

Sign in to view
@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Apr 21, 2025 •
edited
Loading

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)

  • 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

Items for next week's agenda

@JessicaLucindaCheng
Copy link
Member

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

Notes from meeting

Tasks

Items for next week's agenda

@HackforLABot
Copy link
Contributor

Review Inactive Team Members: #8105

Inactive members with open issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue feature: agenda role: dev leads Tasks for technical leads role: merge team Tasks for merge team members role: product Product Management size: 0.5pt Can be done in 3 hours or less
Projects
P: HfLA Website: Project Board
Status: Agendas
Milestone
08. Team workflow
Development

No branches or pull requests
5 participants
@JessicaLucindaCheng @ExperimentsInHonesty @t-will-gillis @mugdhchauhan @HackforLABot