Skip to content
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.

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

HfLA: PM Weekly Meeting Agenda #2212

Open
2 tasks
sheltoG opened this issue Aug 31, 2021 · 62 comments
Open
2 tasks

HfLA: PM Weekly Meeting Agenda #2212

sheltoG opened this issue Aug 31, 2021 · 62 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Administrative Administrative chores etc. feature: agenda role: product Product Management size: 0.25pt Can be done in 0.5 to 1.5 hours
Milestone

Comments

@sheltoG
Copy link

sheltoG commented Aug 31, 2021

Overview

This issue tracks the agenda for the PM team weekly meeting.

Action Items

  • Copy agenda template to a new comment below
  • Add the date of the agenda with comment link to the list
## 2024-MM-DD Agenda and notes for PM meetings

### Prework
- [ ] #2698
- [ ] Check the[ icebox column](https://github.com/hackforla/website/projects/7?card_filter_query=label%3Adependency#column-7198227) to make sure that none of the issues with Dependencies have been cleared
  - [ ] click on issue title
  - [ ] review dependency in the side panel to see if issue is closed
  - [ ] if open, do nothing
  - [ ] if closed
     - [ ] move it to the new issue approval column
     - [ ] remove dependency label
     - [ ] Strike through or check off the dependency

### Recurring items 
- [ ] review any issues that are in the new issue approval column for Dev team 
    - [ ] Front End
       - [ ] [All Issues on board](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22#column-15235217)
       - [ ] [All Issues on board with Ready for Milestones](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22+label%3A%22ready+for+milestone%22#column-15235217)
    - [ ] Back End
       - [ ] [All Issues on board](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22#column-15235217)
       - [ ] [All Issues on board with Ready for Milestones](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22+label%3A%22ready+for+milestone%22#column-15235217)
- [ ] review any issues that are in the new issue approval column for UI/UX team 
    - [ ] Design
       - [ ] [All Issues on board](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+design%22#column-7198227)
       - [ ] [All Issues on board with Ready for Milestones](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+design%22+label%3A%22ready+for+milestone%22#column-7198227)
    - [ ] Research
      - [ ] [All Issues on board](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+user+research%22#column-7198227)
      - [ ] [All Issues on board with Ready for Milestones](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+user+research%22+label%3A%22ready+for+milestone%22#column-7198227)
- [ ] review QA column for dev team 
   - [QA] (https://github.com/hackforla/website/projects/7#column-15490305)
- [ ] review QA column for UI/UX team 
   - [QA] (https://github.com/hackforla/website/projects/7#column-15490305)
- [ ] Prep for Dev team meetings on Saturdays 
- [ ] Prep for UI/UX meetings on Tuesdays 
- [ ] Accountability check 
   - [ ] [Providence](https://github.com/issues?q=is%3Aopen+is%3Aissue+assignee%3AProvidence-o+archived%3Afalse+user%3Ahackforla)


### New Items
- [ ]
- [ ] Carry items that did not get addressed down into items for next week's agenda

### FYIs
- 

### Notes from Meeting
-

### Tasks
- [ ]

### Items for next week's agenda
- [ ] 

Resources

Past Agendas

@sheltoG sheltoG added Feature: Administrative Administrative chores etc. role: product Product Management Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Aug 31, 2021
@sheltoG sheltoG added this to the z. Ongoing milestone Aug 31, 2021
@github-actions
Copy link

Hi @sheltoG.

Good job adding the required labels to this issue.

Just a friendly reminder to also move the issue into the "New Issue Approval" column under the Project Board. For more info on that, check Github's documentation here.
Thanks!

Additional Resources:
Wiki: How to add status labels to issues (WIP. Link will be updated when the wiki is done)
Wiki: How to create issues (WIP. Link will be updated when the wiki is done)

@sheltoG
Copy link
Author

sheltoG commented Aug 31, 2021

Template:
Meeting: 08/31/21

Participants: @ExperimentsInHonesty @kevngaleu @sheltoG @sobe-an

Things to discuss:

  1. Transition of @sobe-an from Hfla project
  2. Review business objectives to inform growth and analytics strategy
  3. For the revised project page come up with ideas of what we want site visitors to understand when they visit the page. Write copy for Projects Page Header #1051
    (
    Things discussed:

Actions to take:

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 5, 2021

2021/09/08
Make a template together
#1996

#918 product needs to come up with the list of labels they want included in the guide and then we can meet with design to identify how the current figma needs to change.

  • Write copy for Projects Page Header #1051 PM team will identify and give UX team clarity on what the most important elements we want to mention on the header of our Projects page.
    • Questions to answer: what do we want people to think about when they think about our projects? How do we want to frame our projects for them?”

#1076 Sobechukwu provided her draft - next steps putting on letterhead and final edits

Issues being worked on
#1730 - Shelton - will update

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 8, 2021

next weeks agenda

#1076 Sobechukwu provided her draft - next steps putting on letterhead and final edits

#918 product needs to come up with the list of labels they want included in the guide and then we can meet with design to identify how the current figma needs to change. - bonnie is going to finish analyzing existing labels and then show them to the rest of the product team before design.

#1968 Kayode is going to listen to interview and do a first draft of text

Collaborative work
#2040 review the product roadmap and identify if we have all the issues necessary to complete the milestone

#2037 Kevin will review the projects against the slide deck and review the sdgs

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 15, 2021

Bonnie to make sure dean has access to edit privacy policy
Connect Shelton with Dean re privacy policy
Get Shelton draft from TDM calculator of consent message

#1968 Kayode is going to listen to interview and do a first draft of text - Add link here to your draft
#2037 Kevin will review the projects against the slide deck and review the sdgs

Make the following issues for milestone 3/satisfactory

  • Projects Page: Change Location dropdown on Project Page to Programs Areas
    • We need look into if there is a figma
    • Do all project.md files have a program area assigned
      • Yes
      • No
  • Projects Page: Check to see if all links on the project cards resolve
    • and make issues for the project card that do not so that we can reach out to each project
  • Join Us Page: Check links for forms, they seems to be operating weirdly (truncated first page)
  • Getting-Started page: Update the FAQ answer to "How many hours are you expected to commit to Hack for LA each week?" See slidedeck for onboarding
  • Communities of Practice: Make sure they are all listed and up to date.
  • Check mobile responsiveness on all issues pages in this milestone

Make issues for excellent level

  • Identify what projects are not project page

  • Discuss at next meeting if we need a milestone for Navigation elements working properly across the site

    • Adjust footer position #2125 This issue is no strictly in onboarding milestone, but needed to be prioritized, should it get its own milestone?

Make prework template

Label issue

CoP template update

@ExperimentsInHonesty
Copy link
Member

@kevngaleu
Copy link
Member

Meeting: 10/06/2021

Participants: @ExperimentsInHonesty @KayodeAlabi @kevngaleu

Things discussed:
Review of current issues of Kayode #1968 and Kevin #2037

@kevngaleu
Copy link
Member

kevngaleu commented Oct 13, 2021

Meeting: 10/13/2021

Participants:

Things to discuss:

  • Google Analytics presentation by Shelton
  • Review of ongoing PM issues

Things discussed:

Actions to take:

@ExperimentsInHonesty ExperimentsInHonesty changed the title PM Weekly Meeting Agenda HfLA: PM Weekly Meeting Agenda Jan 6, 2022
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 16, 2022

Next meeting agenda

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 18, 2022

Template for future meetings

## 2022-MM-DD Agenda and notes for PM meetings

### Prework
- [ ] #2698
- [ ] Check the[ icebox column](https://github.com/hackforla/website/projects/7#column-7198227) to make sure that none of the issues with Dependencies have been cleared
  - [ ] click on issue title
  - [ ] review dependency in the side pannel to see if issue is closed
  - [ ] if open, do nothing
  - [ ] if closed
     - [ ] move it to the new issue approval column
     - [ ] remove dependency label
     - [ ] strikethrough dependency

### New Items
- [ ]
- [ ] Carry items that did not get addressed down into items for next weeks agenda

### FYIs
- 

### Notes from Meeting
-

### Tasks
- [ ]

### Items for next weeks agenda
- [ ] 

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 18, 2022

2022-01-18 Agenda and notes for PM meetings

Prework

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

  • Created template for future meetings
  • reviewed how to do the audit
  • reviewed how to release items from icebox
  • What should be in a dependency
  • We want to make releasing the dependencies be on the person closing the issue so we will add to a future meeting, adding a note to future issues that says
- [ ] When this issue is completed and merged or other completion metric please move Issue #____ to the new issue approval column.

Tasks

  • Add an item to the dev/pm agenda about why there are a bunch of issues that got added to the new issue approval column (i.e., they were not on the board at all).

Items for next week's agenda

  • review some issues from the label audit to see if we can't fix them

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 18, 2022

2022-01-22 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side panel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strike through dependency

New Items

  • review some issues from the label audit to see if we can't fix them
  • Carry items that did not get addressed down into items for next week's agenda

FYIs

Notes from Meeting

Tasks

  • [ ]

Items for next weeks agenda

  • [ ]

@Providence-o
Copy link
Contributor

Providence-o commented Jan 25, 2022

2022-01-25 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

New Items

FYIs

  • Issue 2015 in the icebox column has no dependency label and no dependency has been described in the issue. Move to New issue approval column anyway?

Notes from Meeting

Tasks

  • add to agenda of UI/UX and Dev
    • People are still doing prework issues and not adding them to the board (dev lately). Please, when you have the new people create their own prework issue, stay with them (them screensharing) until they have submitted it, added it to the board and assigned themselves. We have added checkboxes to the template that ask them to do it.
    • we need to have a label for issues that should be not be counted when we are looking at the achieved velocity (number of points on issues successfully completed). What has been happening is that the labels have just been being removed. See example issue DRAFT: Identify and fix inconsistent code indentation in a SCSS file #2628. This will make it hard to see trends in issues that have been created as duplicates or other reasons for closing and not working on. Thoughts?
  • Add to UI/UX agenda

Items for next week's agenda

@Providence-o
Copy link
Contributor

Providence-o commented Jan 27, 2022

2022-01-29 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

New Items

FYIs

Notes from Meeting

Tasks

  • Providence to work with team leads (UX and Dev) to confirm that all calendar invites for team meetings are not sent from their personal email (i.e. they are not the owner)

Items for next week's agenda

  • Mark team members who are inactive as 'inactive' on the roster & perform offboarding Onboard & Offboard: Product #2688
  • Change owner of Sunday all team meeting (on calendar) to [email protected] so that Bonnie doesn't need to start the meeting.
  • We have added the new zoom link for the Sunday website meeting to the Zoom google sheet but we have not uodated the link yet (as we were locked out of the zoom account)
  • we need to update the PM only meeting so that [email protected] is the organiser
  • resolve zoom login issue- Bonnie is licked out of the zoom 1 email account

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 31, 2022

Add to next agenda

FYI

  • Left Jessica Cheng a message on slack

Jessica (she/her) when you come back, Please make an issue and then do the issue to remove Tomas from our project page and add yourself https://www.hackforla.org/projects/website ... Also, can we add Providence at the same time. Her info should be on the roster. (edited)

Tasks

@Providence-o
Copy link
Contributor

Providence-o commented Feb 1, 2022

2022-02-01 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

New Items

FYIs

  • Left Jessica Cheng a message on slack

Jessica (she/her) when you come back, Please make an issue and then do the issue to remove Tomas from our project page and add yourself https://www.hackforla.org/projects/website ... Also, can we add Providence at the same time. Her info should be on the roster. (edited)

  • Providence to work with team leads (UX and Dev) to confirm that all calendar invites for team meetings are not sent from their personal email (i.e. they are not the owner) - waiting for confirmation

Notes from Meeting

Tasks

  • We need to add to the onboarding and offboarding
  • Add rest of agenda to the resources section of the template above.
  • Clean up the roster using the updated filter from the 'Category dropdown tab' and then create filters for each role and send filtered view for each role to the team leads to identify their inactive members. After this is done, we can perform offboarding for inactive team members Onboard & Offboard: Product #2688
  • Let Simone know that Tammy has been added to the 1password and she needs to :
    -Have them log in to the email account for UX research
    -Have them add themselves to the forwarding list
    -Add a filter so that all new messages that come into the email address get forwarded to them.
  • Create a new issue for updating the wiki page Introduction to the project
  • Create a new issue for updating the Joining the HFLA website team

Items for next week's agenda

@ExperimentsInHonesty
Copy link
Member

@Providence-o I have updated the roster with the roles and highlighted the ones where we don't know what to put

@ExperimentsInHonesty
Copy link
Member

Add to next agenda

  • discussing this the problem with the Metrics Dashboard page. Start the discussion by visiting about page and then move on to the links it connects to.

@Providence-o
Copy link
Contributor

Providence-o commented Feb 2, 2022

2022-02-05 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

New Items

FYIs

  • Providence to work with team leads (UX and Dev) to confirm that all calendar invites for team meetings are not sent from their personal email (i.e. they are not the owner) - Dev & UX confirmed

Notes from Meeting

  • Add to the Dev agenda
    • to create an issue to for development to make the footer appear on the dashboard page https://www.hackforla.org/dashboard/
    • discussing this the problem with the Metrics Dashboard page. Start the discussion by visiting about page and then move on to the links it connects to.
    • We need to update the size guidelines in section 2.2 How Hack for LA organizes issues on the CONTRIBUTING.md

Tasks

Items for next week's agenda

  • Create the following labels for developers that don't complete their pre-work issues; achievement: cgfi, achievement: cgsi, achievement Progress update, achievement: review level 1, achievement: review level 2
  • High Priority: clean up 'New Issue Approval' column for issues with role: product and role: missing labels

@Providence-o
Copy link
Contributor

Providence-o commented Feb 6, 2022

2022-02-08 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • Create the following labels for developers that don't complete their pre-work issues; achievement: cgfi, achievement: cgsi, achievement Progress update, achievement: review level 1, achievement: review level 2
  • High Priority: clean up 'New Issue Approval' column for issues with role: product and role: missing labels

FYIs

Notes from Meeting

  • This is the link to add team members to github
  • Bonnie sent this message in the slack channel to everyone who created a pre-work issue last night from the onboarding

Welcome to the HackforLA website team. We have messaged you on the github issue you created. You can find your issue by going to https://github.com/issues

  • Research has 3 issues in NIA column and 0 with ready for milestone label
  • Design has 2 issues in NIA Column and 0 with ready for milestone label

Tasks

  • [ ]

Items for next weeks agenda

  • [ ]

@ExperimentsInHonesty
Copy link
Member

- [ ] Research
  - [ ] [All Issues on board](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+user+research%22#column-7198227)
  - [ ] [All Issues on board with Ready for Milestones](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+user+research%22+label%3A%22ready+for+milestone%22#column-7198227)

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 9, 2022

FYI

  • Add "size: not counted" label to issues that closed because they are duplicate, or we are not going to work on them.
  • Add the size not counted label to the audit links

@Providence-o
Copy link
Contributor

Providence-o commented Feb 12, 2022

2022-02-12 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

#1515 was moved from icebox to new issue approval column

Recurring items

New Items

FYIs

  • Add "size: not counted" label to issues that closed because they are duplicate, or we are not going to work on them.
  • Add the size not counted label to the audit links

Notes from Meeting

Tasks

  • Create new issue to update meeting times via VRMS which will update the times on the hfla website

Items for next weeks agenda

-Note

  • We are not using the 'not counted' label. We need to update design on the two new ignore labels

@Providence-o
Copy link
Contributor

Providence-o commented Feb 13, 2022

2022-02-19 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

FYIs

Notes from Meeting

Tasks

  • Create issue to write to hacktoberfest organizers with request that they add instructions for new people to read the contributing file first.
  • Add to PM template to review QA section for devs and design at these meetings

Items for next weeks agenda

@ExperimentsInHonesty
Copy link
Member

@Providence-o please respond to Ivy. She has messaged you a couple of times in the slack
image

@7kram
Copy link
Member

7kram commented Oct 3, 2022

Add to next agenda meeting:

Look at the issues with no assignees in the in-progress column
Link to progress board

@ExperimentsInHonesty
Copy link
Member

2022-MM-DD Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

Tasks

  • [ ]

Items for next weeks agenda

  • [ ]

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Mar 10, 2023

for our next agenda,

@wanyuguan
Copy link
Member

wanyuguan commented May 28, 2023

2023-05-28 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

Tasks

  • [ ]

Items for next weeks agenda

  • [ ]

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 4, 2023

Item for next agenda

@ExperimentsInHonesty ExperimentsInHonesty added size: 0.25pt Can be done in 0.5 to 1.5 hours and removed size: missing labels Jul 16, 2023
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jul 16, 2023

2023-07-16 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

Tasks

  • [ ]

Items for next weeks agenda

  • BW: review the Homelaunch items homepage launch #2481
  • BW: we will move all the issues with size missing from the prioritized backlog and mark all the ones that are for design or other roles as drafts.

@wanyuguan
Copy link
Member

wanyuguan commented Jul 23, 2023

2023-07-23 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

Tasks

  • [ ]

Items for next weeks agenda

@wanyuguan
Copy link
Member

wanyuguan commented Aug 6, 2023

2023-08-06 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

Tasks

  • [ ]

Items for next weeks agenda

  • [ ]

@Josiah-O
Copy link

Josiah-O commented Oct 29, 2023

2023-10-29 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side pannel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • strikethrough dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next weeks agenda

FYIs

Notes from Meeting

Tasks

  • Kimberly is going to make an issue to add a label report that shows new labels added and any labels deleted.
  • Do an GitHub API call to get all the labels on the repo (may already be a script for this in the data science cop), and then a new script needs to be written that will compare the spreadsheet with the API results and create a data set of deleted and added labels. And then make the dashboard to show us the results of deleted and added data sets temporarily created, it will have a link to https://github.com/hackforla/website/issues?q=is%3Aissue+is%3Aopen+no%3Aproject
  • Kimberly will make an issue to create a report that charts (by week) the status of missing labels.
  • Create an issue to make a new page that will be the landing page for the Anomaly Report. This issue will have the new labels added and the labels deleted report. Additionally it will have a button to run a GitHub action which will add the "missing" series label to any issue that needs it.
  • Dev lead need to let us know which workflow they used to add missing labels to issues. We want to have it revised so that it only runs on demand via the workflow_dispatch event trigger.

Items for next weeks agenda

  • [ ]

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented May 5, 2024

2024-05-05 Agenda and notes for PM meetings

Prework

  • Weekly Label Check #2698
  • Check the icebox column to make sure that none of the issues with Dependencies have been cleared
    • click on issue title
    • review dependency in the side panel to see if issue is closed
    • if open, do nothing
    • if closed
      • move it to the new issue approval column
      • remove dependency label
      • Strike through or check off the dependency

Recurring items

New Items

  • [ ]
  • Carry items that did not get addressed down into items for next week's agenda

FYIs

Notes from Meeting

This is the planning meeting for the Month of May

  • Recap April
    • made progress on eliminating to almost zero the QA column (from over 600 issues), but it bounced back to almost 100 open issues by the end of the month
    • stayed on top of the labels
      • ready for product
      • ready for priortization
    • made no progress on the revising of the prework template (after making a lot of progress in March)
    • Started the organizing of the dashboard work
    • reduced the workload of the dev lead, in order to increase retention
      • getting the merge team members to run more meetings
      • proposing splitting the label ready for dev lead into two labels to include ready for merge team
    • Made progress on getting the new developers waiting of medium issues to make new first and small issues.
  • Plans for May
    • website relaunch
      • identify work needed by product/content
      • setup work for content person (make issues)
      • Recruit content person
    • stay on top of the labels
      • ready for product
      • ready for priortization
    • prework
      • finish first draft
      • sent draft to merge team for feedback
      • rename prework to something more accurate (journey management)
    • make progress on the dashboard work
    • get QA down to almost zero every week

Tasks

  • [ ]

Items for next week's agenda

  • [ ]

@ExperimentsInHonesty ExperimentsInHonesty moved this to Onboarding infos/links in P: HfLA Website: Project Board Jun 23, 2024
@daras-cu daras-cu moved this from Agendas to Prioritized backlog in P: HfLA Website: Project Board Jul 9, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Prioritized backlog to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Jul 12, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from ERs and epics that are ready to be turned into issues to Prioritized backlog in P: HfLA Website: Project Board Jul 12, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Prioritized backlog to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Aug 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from ERs and epics that are ready to be turned into issues to Prioritized backlog in P: HfLA Website: Project Board Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Administrative Administrative chores etc. feature: agenda role: product Product Management size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Status: Prioritized backlog
Development

No branches or pull requests

8 participants