website HfLA: Dev/PM Agenda and Notes

Overview

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

Action Items

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

Resources/Instructions

Template

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

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

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

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

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


### Notes from meeting

### Tasks

### Items for next week's agenda

Prior and upcoming meetings

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

Dec 19 '21 20:12 ExperimentsInHonesty

2021-12-18 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [ ] Check to see how new team members are doing
    - [ ] Front End
    - [ ] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

Recurring items:

New Items

Notes from meeting

Tasks

[ ] Tomas will discuss issue https://github.com/hackforla/website/issues/2311#issuecomment-945154402 with Anh to get more details, and if not Anh, then Kristine. And keep Isaac informed if he is not available for the meeting you setup with either of them.

Items for next weeks agenda

Dec 19 '21 21:12 ExperimentsInHonesty

2022-01-07 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [ ] Check to see how new team members are doing
    - [ ] Front End
    - [ ] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
    - [ ] Bonnie does not seems to be keeping up, what can we do about it (see notes below)
  - [ ] Tomas
  - [ ] Samuil

New Items

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

[ ] This is a new PR(#2417), but when I look at the headers for these two pages they are different getting started page <p class="header-p"> vs the communities of practice <p>
[ ] Pre work checklist improvements: Bot comment addressing the name in subject line vs author Issue
[ ] Discussion on Figma setup for devs. and redesign.
[ ] I don't see a specific issue for developers for this, lets rewrite this one https://github.com/hackforla/website/issues/2401
[ ] https://github.com/hackforla/website/issues/2605#issuecomment-997477244
[ ] #2604 Lets discuss DRY
[ ] Please update the merge team on this card https://github.com/hackforla/website/projects/7#card-69730135

Notes from meeting

Did not go over this agenda. Instead, we went over the Wiki Audit for contributing.md.

Tasks

Figure out how we are going to track bugs
Continue working on the Wiki Audit spreadsheet

Items for next weeks agenda

Dec 19 '21 21:12 ExperimentsInHonesty

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

Dec 24 '21 00:12 ExperimentsInHonesty

2022-01-02 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [ ] Check to see how new team members are doing
    - [ ] Front End
    - [ ] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?
  - https://github.com/hackforla/website/issues/2596#issuecomment-996516112 comment can address assignee instead of author?

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

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Tomas
  - [ ] Samuil

New Items

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

[x] Next steps on PR made by an individual not onboarded yet - #2611 should the PR be closed?
[x] - #2604 next steps for issue?
[x] Should we request ETA and availability from the PR reviewers as well. Many members are in favor of it.
[x] Should the credits page be alphabetically ordered? Pros/cons.
[x] How to make sure multiple issues are not formed for same problem by multiple developers?
[x] Following up on issue #2395, unassigned and moved to prioritized backlog, more comments, reach out to Etienne?
[x] Review the process of updating wiki page. Creating an issue, review with team etc.
[x] New member looking to work on a Python project. Advice or comments!!
[x] Are the issues sorted while being added to the prioritized backlog column? Reference comment
[ ] I don't see a specific issue for developers for this, lets rewrite this one https://github.com/hackforla/website/issues/2401
[x] Nosql svg icon required? Non svg icons to be deleted from google drive? - #2624
[ ] ~Need guidance on workflow related to date live on homepage and number of times appeared on website on homepage summary prototype - #2505~
[x] https://github.com/github/super-linter and other resources shared by team members
[x] https://github.com/hackforla/website/issues/2632 new issue discussion, new page?

Notes from meeting

#2611 updated with comments.
#2604 Tomas will do a rewrite
ETA and availability to be added by reviewers, Saumil will make an issue to add instructions in wiki
Jessica to work on credits page ordering
#2395 ready for pickup after follow up comments to Etienne
New issue for svg icon for nosql Saumil
#2632 updated with comments
Super linter issue to be created by Saumil
Wiki page audit started, moving to Mkdocs

Tasks

Items for next weeks agenda

Dec 25 '21 04:12 SAUMILDHANKAR

@SAUMILDHANKAR, @ExperimentsInHonesty, @R-Tomas-Gonzalez

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, January 3, 2022 at 11:19 PM PST.}

Jan 07 '22 07:01 github-actions[bot]

@SAUMILDHANKAR, @JessicaLucindaCheng, @ExperimentsInHonesty, @R-Tomas-Gonzalez, @Providence-o

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, January 10, 2022 at 11:19 PM PST.}

Jan 14 '22 07:01 github-actions[bot]

2022-01-15 Meeting Agenda

Prework to prep for meeting

[x] Review the QA
- [x] Front end
  - [x] Once front end is checked, check backend, to make sure that there are no issues that are backend only
- [x] 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
    - [ ] Front End
    - [ ] Back End
  - [x] Can we improve the prework template based on something we see as a pattern?

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

Recurring items:

[x] review any issues that are in the new issue approval column for
- [x] Front End
- [x] Back End
[x] Accountability and Support Check.
- [x] Review assignments for each PM
  - [x] Bonnie
  - [x] Tomas
  - [x] Samuil

New Items

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

[x] On the Wins page, the star icon has a tooltip that can have various length text. On the 4th page of the Wins form, the star icon text comes from the question, "What do you want to celebrate (select all that apply)?" and choosing "Other," which allows input of various length text.
[x] In the Typography section of Figma Design System, there are paragraph classes but those don't currently exist. Should an issue be created to add paragraph classes for legible font sizes (so only for paragraph classes 1-3)?
[x] Below is the agenda from the 2022-01-07 Agenda that we did not go over. Is there anything we should go over today?
- [x] This is a new PR(#2417), but when I look at the headers for these two pages they are different getting started page <p class="header-p"> vs the communities of practice <p>
- [x] Pre work checklist improvements: Bot comment addressing the name in subject line vs author Issue
- [x] Discussion on Figma setup for devs. and redesign.
- [x] I don't see a specific issue for developers for this, lets rewrite this one https://github.com/hackforla/website/issues/2401
- [x] https://github.com/hackforla/website/issues/2605#issuecomment-997477244
- [x] #2604 Lets discuss DRY
- [x] Please update the merge team on this card https://github.com/hackforla/website/projects/7#card-69730135

Notes from meeting

Dev team needs to check in on all the new members before the meeting
we updated the prework template so that its easier to follow the steps after they pick up the good first issue
Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
~Pre work checklist improvements: Bot comment addressing the name in subject line vs author Issue~ we are not doing this because the author and assignee should be the same person.

Tasks

[x] Jessica will update the template to add herself to the accountability and support check template
- [x] Bonnie added it
[x] Jessica will make an issue to make new classes for the Paragraphs: https://github.com/hackforla/website/issues/2690
[x] Make offboarding issue and use it with Tomas. Use this an example: https://github.com/hackforla/open-community-survey/issues/92
- Tomas

Items for next week's agenda

https://github.com/hackforla/website/issues/2605#issuecomment-997477244
Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
We need to do an offboarding with Tomas. #2689
Discuss this:
- [ ] Create an issue to fix a problem with the BOP project and any other project that cannot put a hack-for-la topic tag on itself see these comments for details
- https://github.com/hackforla/website/issues/2605#issuecomment-997477244
- https://github.com/hackforla/website/issues/2605#issuecomment-1013941235

Jan 14 '22 23:01 JessicaLucindaCheng

2021-01-22 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [x] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Front End
    - [x] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

[ ] https://github.com/hackforla/website/pull/2691#issuecomment-1018056990

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

[ ] The new issues to be created for development is getting quite long. Let's talk about strategies for getting more hands to help https://github.com/hackforla/website/projects/7#card-74647681
- [ ] J: Idea - https://github.com/hackforla/website/issues/2681
[ ] https://github.com/hackforla/website/issues/2605#issuecomment-997477244
[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
[ ] We need to do an offboarding with Tomas. #2689
[ ] Discuss this:
- [ ] Create an issue to fix a problem with the BOP project and any other project that cannot put a hack-for-la topic tag on itself see these comments for details
- https://github.com/hackforla/website/issues/2605#issuecomment-997477244
- https://github.com/hackforla/website/issues/2605#issuecomment-1013941235
[ ] Did this get done : Jessica will make an issue to make new classes for the Paragraphs - https://github.com/hackforla/website/issues/2690
[ ] Tools is in some of the project cards, but is not showing up on the card, but it is showing up on their page. See Access the Data https://www.hackforla.org/projects/access-the-data
[ ] https://github.com/hackforla/website/issues/1443
[ ] Discuss 2FA for the elizabethhonest bot account @elizabethhonest
[ ] J: In terms of issues for developers, such as updating leadership on project info pages, how long should items with time sensitive label sit in the Prioritized Backlog? It's not really defined in the How to read and interpret labels
[ ] J: https://github.com/hackforla/website/issues/2674 - Jessica's not sure if this can be found. Initially, spent 20 minutes looking for it to try to make it a good first or second issue but Jessica couldn't find the image nor the artist.
[ ] J: https://docs.google.com/document/d/1qMQt84sZzcX-Sml-szhRDVsCFfd_eq_zO-tLXMIY2p0/edit - Created this checklist for Technical Leads onboarding new developers.
[ ] Discussion/details on #2663
[x] PM to let dev team know why there are new issues that got added to the new issue approval column on the project board (where they were not previously there at all)

Notes from meeting

Tasks

Items for next week's agenda

Ask Bonnie who should be moving issues with Depedency labels from the Ice Box to New Issue Approval column

Jan 16 '22 22:01 ExperimentsInHonesty

Add to the next agenda

[x] Discuss how to change the accomplishment section of about page so that it shows the current year and a has an accordion for 2020, which when the chevron or a more link is clicked it loads more accomplishments
- Accomplishments content update is done #2585
- https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it)
- https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section

Jan 25 '22 00:01 ExperimentsInHonesty

2022-01-27 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [x] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Front End
    - [x] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

[x] https://github.com/hackforla/website/pull/2691#issuecomment-1018056990
[x] https://github.com/hackforla/website/issues/2721#issuecomment-1022930427

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

[ ] The new issues to be created for development is getting quite long. Let's talk about strategies for getting more hands to help https://github.com/hackforla/website/projects/7#card-74647681
[ ] https://github.com/hackforla/website/issues/2605#issuecomment-997477244
[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
[ ] We need to do an offboarding with Tomas. #2689
[ ] Discuss this:
- [ ] Create an issue to fix a problem with the BOP project and any other project that cannot put a hack-for-la topic tag on itself see these comments for details
- https://github.com/hackforla/website/issues/2605#issuecomment-997477244
- https://github.com/hackforla/website/issues/2605#issuecomment-1013941235
[ ] Did this get done : Jessica will make an issue to make new classes for the Paragraphs - https://github.com/hackforla/website/issues/2690
- [ ] FYI: Put this in Ice Box because I need paragraph classes to continue work on this https://github.com/hackforla/website/issues/2555
[ ] Tools is in some of the project cards, but is not showing up on the card, but it is showing up on their page. See Access the Data https://www.hackforla.org/projects/access-the-data
[ ] https://github.com/hackforla/website/issues/1443
[ ] Discuss 2FA for the elizabethhonest bot account @elizabethhonest
[ ] J: https://github.com/hackforla/website/issues/2674 - I'm not sure if this can be found. Initially, spent 20 minutes looking for it to try to make it a good first or second issue but I couldn't find the image nor the artist.
[ ] Discussion/details on #2663
[ ] Ask Bonnie who should be moving issues with Depedency labels from the Ice Box to New Issue Approval column
[ ] J: I hid previous meeting agendas for this (Dev/PM meeting agenda) because I was getting confused with which was the current agenda and I was adding items to the wrong place. However, I added links to all our previous meetings at the bottom of this https://github.com/hackforla/website/issues/2607#issue-1084188455
[ ] Jessica needs access to the Zoom meetings spreadsheet.

From Product

[x] PM to let dev team know why there are new issues that got added to the new issue approval column on the project board (where they were not previously there at all)
[ ] PM to let dev team know that people are still doing prework issues and not adding them to the board. Please, when you have the new people create their own prework issue, stay with them (them screen sharing) 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.
[ ] PM to let dev team know that 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 #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?
- J - Question: How is velocity currently tracked?
[ ] Discuss how to change the accomplishment section of about page so that it shows the current year and a has an accordion for 2020, which when the chevron or a more link is clicked it loads more accomplishments
- Accomplishments content update is done #2585
- https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it)
- https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section

Notes from meeting

Currently the readme says

Once you have gone through onboarding, go to the WIKI. For developers looking for the standard README, see the CONTRIBUTING document for more details on how to get started. Also see our Code of Conduct and License documents.

We need to change it to say We require all Code Contributors to

Join our organization by going through Hack for LA onboarding. It's free to join!
Read the onboarding section of our WIKI.
Read our CONTRIBUTING document and follow the steps.

Tasks

[ ] Bonnie to write to hacktoberfest organizers with request that they add instructions for new people to read the contributing file first.
[x] Dev team leads reach out to https://github.com/hackforla/website/issues/2637

Items for next week's agenda

Jan 27 '22 04:01 Providence-o

2022-01-29 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [x] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Front End
    - [x] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

[ ] The new issues to be created for development is getting quite long. Let's talk about strategies for getting more hands to help https://github.com/hackforla/website/projects/7#card-74647681
[ ] https://github.com/hackforla/website/issues/2605#issuecomment-997477244
[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
[ ] We need to do an offboarding with Tomas. #2689
[ ] Discuss this:
- [ ] Create an issue to fix a problem with the BOP project and any other project that cannot put a hack-for-la topic tag on itself see these comments for details
- https://github.com/hackforla/website/issues/2605#issuecomment-997477244
- https://github.com/hackforla/website/issues/2605#issuecomment-1013941235
[ ] Did this get done: Jessica will make an issue to make new classes for the Paragraphs - https://github.com/hackforla/website/issues/2690
- [ ] FYI: Put this in Ice Box because I need paragraph classes to continue work on this https://github.com/hackforla/website/issues/2555
[ ] Tools is in some of the project cards, but is not showing up on the card, but it is showing up on their page. See Access the Data https://www.hackforla.org/projects/access-the-data
[ ] https://github.com/hackforla/website/issues/1443
[ ] Discuss 2FA for the elizabethhonest bot account @elizabethhonest
[ ] Discussion/details on #2663
[ ] Ask Bonnie who should be moving issues with Dependency labels from the Ice Box to New Issue Approval column
[x] J: Can I be made a maintainer?

From Product

[x] PM to let dev team know why there are new issues that got added to the new issue approval column on the project board (where they were not previously there at all)
[ ] PM to let dev team know that people are still doing prework issues and not adding them to the board. Please, when you have the new people create their own prework issue, stay with them (them screen sharing) 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.
[ ] PM to let dev team know that 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 #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?
- J - Question: How is velocity currently tracked?
[x] Discuss how to change the accomplishment section of about page so that it shows the current year and a has an accordion for 2020, which when the chevron or a more link is clicked it loads more accomplishments
- Accomplishments content update is done #2585
- https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it)
- https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section

Notes from meeting

Tasks

[ ] Bonnie to write to hacktoberfest organizers with request that they add instructions for new people to read the contributing file first.
[ ] Bonnie to make an announcement on the slack channel and all volunteer meeting on Sunday (30th January) that the meetings during the first week of February are cancelled however, they can communicate with the leads and with each other on the slack channel.

Items for next week's agenda

Jan 29 '22 03:01 JessicaLucindaCheng

Add to next agenda

This needs an update asap https://github.com/hackforla/website/wiki/Web-Developer because I need to have a landing page for people coming from the self paced onboarding slide deck
- There is a line that says "Read through Hack for LA Site Architecture. If you have questions or feedback, add it to Issue 529." but #529 is closed.
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)

The News section on the about page is formatted strangely and is not responsive https://www.hackforla.org/about/#news

Jan 31 '22 19:01 ExperimentsInHonesty

2022-02-05 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [x] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive
      - [x] Backend 2 weeks inactive
    - [x] Front End - Checked Fri, 2/4 by Jessica
    - [x] Back End - Checked Fri, 2/4 by Jessica
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

[ ] J: I put this in Ice Box because I need paragraph classes to continue work on this https://github.com/hackforla/website/issues/2555

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

[x] Discuss #2650 with Saumil, to confirm size and what milestone it falls under (excellent level)
[x] The new issues to be created for development is getting quite long. Let's talk about strategies for getting more hands to help https://github.com/hackforla/website/projects/7#card-74647681
[x] We need to do an offboarding with Tomas. #2689
[x] J: Can I be added to the website-admins team?
[x] Discuss this:
- [x] Create an issue to fix a problem with the BOP project and any other project that cannot put a hack-for-la topic tag on itself see these comments for details
- https://github.com/hackforla/website/issues/2605#issuecomment-997477244
- https://github.com/hackforla/website/issues/2605#issuecomment-1013941235
[x] Tools is in some of the project cards, but is not showing up on the card, but it is showing up on their page. See Access the Data https://www.hackforla.org/projects/access-the-data
[x] https://github.com/hackforla/website/issues/1443
[x] Discussion/details on #2663
[x] Ask Bonnie who should be moving issues with Dependency labels from the Ice Box to New Issue Approval column
[x] J: https://github.com/hackforla/website/issues/2674 - I'm not sure if the image can be found. Initially, I spent 20 minutes looking for it to try to make it a good first or second issue but I couldn't find the image nor the artist.
[x] J: https://github.com/hackforla/website/issues/2658#issuecomment-1021750650

From Product

[x] PM to let dev team know that people are still doing prework issues and not adding them to the board. Please, when you have the new people create their own prework issue, stay with them (them screen sharing) 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.
[x] PM to let dev team know that 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 #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?
- J - Question: How is velocity currently tracked? In others, what are you specifically looking at in GitHub? The number of items in the Done column? Info in the Insights tab? Something else?
[x] This needs an update asap https://github.com/hackforla/website/wiki/Web-Developer because I need to have a landing page for people coming from the self paced onboarding slide deck
- There is a line that says "Read through Hack for LA Site Architecture. If you have questions or feedback, add it to Issue 529." but #529 is closed.
[x] 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)

[x] J: https://github.com/hackforla/website/issues/2731
- [x] HfLA Website Team page
- [x] HfLA Website Team project card
[x] The News section on the about page is formatted strangely and is not responsive https://www.hackforla.org/about/#news
- [x] J: This issue addresses that problem: https://github.com/hackforla/website/issues/1498
[x] to create an issue to for development to make the footer appear on the dashboard page https://www.hackforla.org/dashboard/
[x] We need to update the size guidelines in section 2.2 How Hack for LA organizes issues on the CONTRIBUTING.md

Notes from meeting

Tasks

[x] We need to do an offboarding with Tomas. #2689
- [x] Saumil: Take a look at the lists
- [x] Both tech leads: Clean the checklist up and do offboarding with Tomas
[x] Add to pre-work checklist for devs to have check off that they have read what to do when they stop mid issue https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue
- [x] Jessica will do this
[x] https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue: Write an issue to fix this: Remove the progress in the checkboxes (all checkboxes should be empty).
- [x] Jessica will do this
[ ] ~~Create an issue to fix a problem with the BOP project and any other project that cannot put a hack-for-la topic tag on itself see these comments for details - Saumil will take a look at it.~~
- ~~https://github.com/hackforla/website/issues/2605#issuecomment-997477244 - hack-for-la topic figure out how it "works for la" does it~~
- ~~https://github.com/hackforla/website/issues/2605#issuecomment-1013941235 - this relates to the topic tag for hfla figure out how it works for "work for la"~~ Moved this to comment on 4/6/22
[x] Tools is in some of the project cards, but is not showing up on the card, but it is showing up on their page. See Access the Data https://www.hackforla.org/projects/access-the-data ---> want it on the project cards too now - Jessica
[ ] ~~https://github.com/hackforla/website/issues/1443:~~
- [x] ~~1) During dev meeting, have everyone run docker and time it. Then, have everyone put their time in the chat. figure out avg time to load. - Saumil~~
- [ ] ~~2) Then put in contributing.md that says if if takes much longer than the average time to let the tech leads know by bringing this up to us and adding a comment in the issue #1443. Also, add the issue #1443 to the dev team agenda to discuss it. - Saumil~~ Moved this to comment on 4/6/22
[x] For issue we are closing that are not worked on, we need to create labels, such as ignore: duplicate and ignore: test. - Jessica
- [x] Pausing this until I get clarification if "size: not counted" is in addition to or in place of these labels
[x] For the Wiki Web Develper page edit it. The wiki Web Developer is before doing pre-work issue and before contributing.md. Want a link from onboarding deck to this page.
- [x] First draft Jessica.
- [x] Second look Saumil.
- [x] There is a line that says "Read through Hack for LA Site Architecture. If you have questions or feedback, add it to Issue 529." but #529 is closed. - Jessica
- [x] Have a line if they have questions to send a Slack message to Technical Lead(s) - Jessica
  - [x] Not sure if it fits in there now, so left it out in first draft.
- [x] Work progress and updates will continue in this issue https://github.com/hackforla/website/issues/2746
[ ] ~~We need to update the size guidelines in section 2.2 How Hack for LA organizes issues on the CONTRIBUTING.md - Saumil~~
- [ ] ~~Create an issue to update the contributing.md to have complexity (good second issue, small, medium, large) and size will be 1pt, 2pt, etc - Saumil~~
- [ ] ~~Create an issue to update GHA to reflect the change in labeling using complexity and size (see point above) - Saumil~~ Moved this to comment on 4/6/22

Items for next week's agenda

[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
[ ] 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.
[ ] Discuss the format of the CoP update issue template. see this issue #2744
[ ] Ask the Dev leads to come to the end of onboarding and help people make their first issue and/or clean up the first issues the next morning (the challenge is Bonnie is the only one with their email address)

Feb 04 '22 19:02 JessicaLucindaCheng

I added two items to the dev agenda since they seemed time sensitive

https://github.com/hackforla/website/issues/2699#issuecomment-1033241006
https://github.com/hackforla/website/issues/2699#issuecomment-1033250666

Feb 09 '22 02:02 ExperimentsInHonesty

add this as fyi to next agenda

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

Feb 09 '22 20:02 ExperimentsInHonesty

Add to next agenda:

Clarification on whether new developers should move their own checklists from New Approval column to In Progress or if PMs want to do that in order to get introduced to new devs digitally (including removing Ready for Milestone labels and putting a milestone on the prework issues)
For issue we are closing that are not worked on, we need to create labels, such as ignore: duplicate and ignore: test.
- Are we still doing this or are we going to instead use "size: note counted"?
Confirming issue progression is good first issue --> good second issue --> small --> medium --> large?

Feb 10 '22 23:02 JessicaLucindaCheng

2022-02-12 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [ ] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive
      - [x] Backend 2 weeks inactive
    - [x] Front End
    - [x] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

[x] Add "size: not counted" label to issues that closed because they are duplicate, or we are not going to work on them.
- [ ] J: Last meeting we discussed creating labels, such as "ignore: duplicate" and "ignore: test". Are we using "size: not counted" in addition to or in place of the ignore labels?
[x] Technical Leads want to ask George Ma and Lindsey Dinkel to join the merge team.

Recurring items:

[x] review any issues that are in the new issue approval column for
- [x] Front End
- [x] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

Add issue numbers to be discussed and any notes that will be helpful
[x] Talk to leads about their total number of hours contributed
[x] discussing the problem with the Metrics Dashboard page. Start the discussion by visiting about page and then move on to the links it connects to. #542
[x] Discuss the format of the CoP update issue template. see this issue #2744
[x] Ask the Dev leads to come to the end of onboarding and help people make their first issue and/or clean up the first issues the next morning (the challenge is Bonnie is the only one with their email address)
[x] J: Clarification on whether new developers should move their own checklists from the New Approval column to In Progress or if PMs want to do that in order to get introduced to new devs digitally (including removing Ready for Milestone labels and putting a milestone on the prework issues)
[x] J: #2689 Questions with some items in the onboarding checklist
- [ ] Onboarding Jessica: https://github.com/hackforla/website/issues/2689#issuecomment-1036774288
- [ ] Offboarding Tomas: https://github.com/hackforla/website/issues/2689#issuecomment-1036717027
[x] Issue #2744, #2743 are these ready to be worked on ?
[x] #2746
[x] https://github.com/hackforla/website/issues/2768#issuecomment-1037524345
[x] !!! J: Confirming issue progression is good first issue --> good second issue --> small --> medium --> large? Also, this applies to all developers new to the team?

Notes from meeting

Tasks

[x] Bonnie https://github.com/hackforla/website/issues/2355

Items for next week's agenda

[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
[ ] Create a new email address for reaching out to devs '2 weeks inactive'
[ ] Review onboard/offboard #2689 for dev leads

Feb 12 '22 00:02 JessicaLucindaCheng

Add to next meeting agenda:

Can we include the dial-in information for Zoom meetings? Just in case someone drops off or has internet problems.

Feb 13 '22 20:02 JessicaLucindaCheng

2022-02-19 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive
      - [x] Backend 2 weeks inactive
    - [x] Front End
    - [x] Back End
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

[x] Create a new email address for reaching out to devs '2 weeks inactive'
[x] Review onboard/offboard #2689 for dev leads
[x] Can we include the dial-in information for Zoom meetings? Just in case someone drops off or has internet problems.
- [x] Tue Dev Mtg - Not sure what Zoom account it is from. I don't see it on the spreadsheet and I looked through all the Zoom accounts for this meeting.
- [x] Sun All Team Mtg
[x] J: How many of each issue by complexity (1st, 2nd, small, medium, large) should we have in the Prioritized Backlog? Sometimes I'm concerned we may run out and want to keep an eye on it.
[x] https://github.com/hackforla/website/issues/2746#issuecomment-1046099273
[x] Product: https://github.com/hackforla/website/issues/2707 ignore label not used on this issue. why? Ans: See https://github.com/hackforla/website/issues/2707#issuecomment-1029434177
[x] Product: https://github.com/hackforla/website/projects/7?card_filter_query=pre-work Bonnie to discuss with devs
[x] Product: https://github.com/hackforla/website/issues/2560 Bonnie to discuss with devs

Notes from meeting

How many of each issue by complexity (1st, 2nd, small, medium, large) should we have in the Prioritized Backlog? Sometimes I'm concerned we may run out and want to keep an eye on it.
- Ans: Calculate to see if we have 4 weeks (ideally 8 weeks) worth of issues using the points and compare it to how many points we need based on the number of developers currently on the team and what is the next issue complexity they will be working

Tasks

[x] From 01/29/2022 agenda, Product to make an issue to write to hacktoberfest organizers with request that they add instructions for new people to read the contributing file first.
[x] Saumil will add Ignore labels to issues that are closed and need them in the QA column.
[ ] ~~New issue needs to be made for why bot is moving the issue from done to QA. @SAUMILDHANKAR will check on it. Reference this issue where HackforLaBot moved this issue back to QA from done: https://github.com/hackforla/website/issues/2707~~ Moved this to a comment on 4/6/22
[x] Jessica will update password for the new dev email
[x] Devs update the template #2689
- [x] Jessica will make edits first.
- [x] Saumil will make edits second.
[x] Jessica will include the dial-in information for Zoom meetings - Sun All Team Mtg
[x] Saumil: once CTJ moves their meeting, create a meeting in one of the Zoom rooms (1/2/3) for the Tue 7-8pm meeting
- [x] Jessica: update calendar invite with new Zoom link and make sure to add dial-in info
[x] Update #2746 according to this comment https://github.com/hackforla/website/issues/2746#issuecomment-1046104161
- [x] Jessica will make first edits
- [ ] ~~Saumil will make second edits~~ moved this to a comment on 4/6/22
[x] Jessica reach out to the person to see if they are still interested https://github.com/hackforla/website/issues/2560
[x] Saumil move all the closed Pre works to Done unless there is any question in which case they can stay in Questions/Review until resolved.
[x] Pending tasks for the tech leads from previous weeks https://github.com/hackforla/website/issues/2607#issuecomment-1030273048

Items for next week's agenda

[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676

Feb 19 '22 18:02 JessicaLucindaCheng

For next agenda:

FYI:

[ ] I added and prioritized any good first issues with a milestone already added to the Prioritized Backlog column because we were running out of good first issues.
[ ] Couldn't find Shantanu's email in our roster nor the engineering roster, so I just left a comment in the pre-work: https://github.com/hackforla/website/issues/2560#issuecomment-1050392158

New Item:

[ ] Can we schedule meetings in Zoom4 or is that only for Expunge Assist team?
[ ] Similar to the first week of February, are we canceling meetings for March 1-7 for internal members but still having admins/leads meetings?

Feb 23 '22 21:02 JessicaLucindaCheng

2022-02-26 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [x] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive - Checked Fri, Feb 25
      - [x] Backend 2 weeks inactive - Checked Fri, Feb 25
    - [x] Front End - Checked Fri, Feb 25
    - [x] Back End - Checked Fri, Feb 25
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

[x] Jessica added and prioritized any good first issues with a milestone already added to the Prioritized Backlog column because we were running out of good first issues.
[x] Jessica couldn't find Shantanu's email in our roster nor the engineering roster, so I just left a comment in the pre-work: https://github.com/hackforla/website/issues/2560#issuecomment-1050392158
[x] After checking and messaging people, technical leads are leaving 2 weeks inactive for issues in the In Progress column, so it is a reminder to technical leads to check them again in a week to see if the issues were updated.

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

From Dev:

[x] We need more small issues. Ideas?
- [x] Can we write a small issue to update the leadership for our team to remove Isaac?
[ ] Want to start writing small issues related to these design issues but it's still in QA column and I disagree with some of the recommendations. Can I start writing issues for some of the recommendations?
- [ ] https://github.com/hackforla/website/issues/2571
  - [ ] Google Sheet link to the tab: https://docs.google.com/spreadsheets/d/1abMlPOX88zHTV29E4BFxAYwahCxgJN28Mn95cXr8jak/edit#gid=703949441
- [ ] https://github.com/hackforla/website/issues/2572
  - [ ] Google Sheet link to the tab: https://docs.google.com/spreadsheets/d/1abMlPOX88zHTV29E4BFxAYwahCxgJN28Mn95cXr8jak/edit#gid=456130506
[x] Can we schedule meetings in Zoom4 or is that only for Expunge Assist team? Zoom4 is used for Onboarding Sessions on Mon and Tue from 6-7:30pm
[x] Similar to the first week of February, are we canceling meetings for March 1-7, except for admins/leads meetings? Yes
- [x] If yes, is there still an onboarding session on March 1st? https://www.meetup.com/hackforla/events - Yes

Notes from meeting

Tasks

Items for next week's agenda

[ ] Dev team will let Bonnie know when they want to meet again after working on spreadsheet for #2676
[ ] Product to discuss this issue #2919 with dev team - time sensitive

Feb 25 '22 00:02 JessicaLucindaCheng

@SAUMILDHANKAR, @JessicaLucindaCheng, @ExperimentsInHonesty, @Providence-o

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, February 28, 2022 at 11:18 PM PST.}

Mar 04 '22 07:03 github-actions[bot]

2022-03-05 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [x] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive - Checked Fri, Mar 4
      - [x] Backend 2 weeks inactive - Checked Fri, Mar 4
    - [x] Pre-work Developers Checklists in QA
      - [x] Front End - Checked Fri, Mar 4
      - [x] Back End - Checked Fri, Mar 4
  - [x] Can we improve the prework template based on something we see as a pattern?

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

[x] Tamara Snyder is part of merge team

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

From PM

[x] Product to discuss this issue #2919 with dev team - time sensitive
[x] Brentwood School about their service requirements

From Dev

[x] Ideas for small complexity issues for developers? We are running low.
- [x] Have people who finished the medium issue to work on making small issues possibly. It's like a medium+ issue.
[x] Did you want Merge Team members to have editing access to Figma? Yes
[x] Currently, we have the following templates: "Blank Issue" and "Blank Issue Template". Can we change the name of "Blank Issue" to the "Blank Issue Form" to make it clearer? See: https://github.com/hackforla/website/issues/new/choose
[x] Toolkit page images on the guide cards. Okay to use png and have it show the whole image.

Notes from meeting

Students don't need to meet the requirement for attending weekly meetings. However, they should attend a meeting if they need help.
Toolkit page notes
- Images for each role type
- Set of icons to choose from for technologies and topics (Material UI)
- Filter for technologies and role
- Search function for title

Tasks

[ ] ~~Dev: Make more small issues by Monday (Saumil)~~ Moved to a comment on 4/6/22
[ ] ~~Dev: https://github.com/hackforla/website/issues/2758#issuecomment-1033403336 (Saumil)~~
- [x] Change the comment message that tells people outside of the repo they ignore the comment about adding labels
- [ ] ~~Check options for solutions:~~
  - [ ] ~~If GHA can detect the person opening the issue is not part of website-write team (Saumil)~~
  - [ ] ~~Check title if it's COP then don't send comment (Saumil)~~ Moved to a comment on 4/6/22
[x] Dev: Open issue with VRMS to change Thu 7-8pm Backend Meeting to Developers Office Hours (Jessica)
- Link to track the issue: https://github.com/hackforla/VRMS/issues/1098
[x] Dev: https://github.com/hackforla/website/issues/2749#issuecomment-1059857194: Slack message and email if possible this person (Saumil) (Reached out on slack, didn't find email in website team roster)
[x] Product still working on this issue #2919 will let dev team know when it's ready.
[ ] ~~Dev: To do service hours, we need to add pt labels to all open dev issues (due Mar 15)~~
- [x] Front end (Jessica)
- [ ] ~~Back end/devops (Saumil)~~ Moved to a comment on 4/6/22
[x] Due Mar 15: Add pts to any closed/open issues for Sakari (GitHub handle: Zak234). (Jessica)
[x] Edit 0.5pt label with description (Bonnie completed it)
[x] Make 2 blank issue forms
- [x] 1) with dependency at the top named "Blank Issue Form with Dependency" (Jessica)
- [x] 2) without dependency and named "Blank Issue Form" (Saumil) --> https://github.com/hackforla/website/issues/2954
[x] Devs: Think about accountability buddies for brand new members and how to shift responsibilities for checking the prework closer to the newer devs
[x] Give Tamara editing access to Figma (Jessica)
[x] Update onboard/offboard checklist for Figma invite and acceptance for merge team and tech leads (Jessica)

Items for next week's agenda

[ ] Discuss good first, good second and small issues that had a lot of pr request changes (Saumil: possible candidates PRs 2772, 2790, 2723, 2774)

Mar 04 '22 22:03 JessicaLucindaCheng

Add to next agenda: The CTJ team has made a new onboarding survey. We need to integrate it into the existing dashboard. Lets talk about how at our next meeting

issue https://github.com/hackforla/CivicTechJobs/issues/125
get you access to their folders, etc.

Mar 06 '22 19:03 ExperimentsInHonesty

Add to next agenda:

[ ] Ryan https://github.com/hackforla/website/issues/2749, would like to start again in winter and wants to know if he would need onboarding again or just joining the meetings would be enough.
[ ] ~issue #2936:~ No longer need to discuss this because https://github.com/hackforla/website/issues/2936#issuecomment-1064538117
- This seems time sensitive. Should I just work on it?
- Ideas for how to incorporate the credit
  - Current Credits page: https://www.hackforla.org/credits/
  - Idea 1:
    - Header paragraph wording changed to incorporate other credits besides images
    - On the bottom of the page, added "Tools" section with SoGoSurvey credit in it
    - Added headers "Images" and "Tools" to each section
    - Click to see image for Idea 1
  - Idea 2:
    - Header paragraph wording stays the same
    - On the top of the page, added "Tools" section with SoGoSurvey credit in it
    - Added headers "Images" and "Tools" to each section
    - Click to see image for Idea 2
[x] ~Did you want all closed merged prs to be moved off the board to the "Issues Closed 13 months or more" or to no board at all?~ Answered already: No board at all.
[ ] PR columns should be
- Issues that need a reviewer assigned
- issues that need changes from authors
- ready for re-review (from the original reviewer)
- reviewer has approved, waiting for merge team to merge
[ ] Issue can be archived for a board but not for the repo: https://docs.github.com/en/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board
[ ] Is the milestones "Z. Accessibility" and "Z. Excellent Level" the same level of priority?
[ ] Product to talk about #2952 and #2953 in new issue approval column with dev team
[ ] Product to talk to dev team about #2776. The problem isn't about the dashboard, it's about the Google data studio
[ ] https://github.com/hackforla/website/issues/2656: Did you want a higher milestone then this so it gets done sooner?
[ ] Ask who is going to contact GitHub regarding the Project Board crashing
- [ ] More likely to crash if there are more than 1 tabs of Project Board open (maybe)
[ ] Does the Action Item(s) in this issue need to be updated? https://github.com/hackforla/website/issues/2025
[ ] https://github.com/hackforla/website/issues/1338: Should we pull this issue from the prioritized backlog? The reasons are:
- This is no longer true "Good First Issue are all usually updates/edits to the projects collection."
- There is already information on self-assigning an issue in the Contributing.md: https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#24-claiming-an-issue
- Does the info on working on issues in the Contributing.md cover the information that is asked to be added in this issue? https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-2-how-the-website-team-works-with-github-issues
https://github.com/hackforla/website/issues/2528: Can we re-write this issue and make it into an epic, where we make small issues or good second issues from it? The reasons are:
- Some of the credits exist on the feature branch but need some of the information changed because it has outdated/inaccurate info.
- Some credits need to be created from scratch but the image exists on the feature branch already.
- One credit needs to be created and needs an image added.
- It will make it easier to review each credit.
[ ] https://github.com/hackforla/website/issues/2606#issuecomment-1050158878
- [ ] Is this okay?
- [ ] Should I update the Figma design for the project info page with the updated 16px font?

Mar 08 '22 21:03 JessicaLucindaCheng

March 12, 2022 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive Last checked 3/11
      - [x] Backend 2 weeks inactive Last checked 3/11
    - [x] Check all open pre-work developers checklists on the board and closed pre-work developers checklist in QA
      - [x] Front End Last checked 3/11
      - [x] Back End Last checked 3/11
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

From Product:

[x] The CTJ team has made a new onboarding survey. We need to integrate it into the existing dashboard. Lets talk about how at our next meeting
- [x] issue https://github.com/hackforla/CivicTechJobs/issues/125
- [x] get you access to their folders, etc.
[x] Product to talk about #2952 and #2953 in new issue approval column with dev team
[x] Product to talk to dev team about #2776. The problem isn't about the dashboard, it's about the Google data studio
[x] Talk to devs about #2459 to confirm it has been implemented
[x] We are ready to turn this issue over to the front end team #2919
[x] Discuss this tool for automatically creating good first issues

From Dev:

[x] Discuss good first, good second and small issues that had a lot of pr request changes (Saumil: possible candidates PRs 2772, 2790, 2723, 2774)
[x] Ryan https://github.com/hackforla/website/issues/2749, would like to start again in winter and wants to know if he would need onboarding again or just joining the meetings would be enough.
[x] PR columns should be
- Issues that need a reviewer assigned
- issues that need changes from authors
- ready for re-review (from the original reviewer)
- reviewer has approved, waiting for merge team to merge
[x] Issue can be archived for a board but not for the repo: https://docs.github.com/en/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board
[x] Is the milestones "Z. Accessibility" and "Z. Excellent Level" the same level of priority?
[x] https://github.com/hackforla/website/issues/2656: Did you want a higher milestone then this so it gets done sooner?
[x] Ask who is going to contact GitHub regarding the Project Board crashing
- [x] More likely to crash if there are more than 1 tabs of Project Board open (maybe)
[x] Does the Action Item(s) in this issue need to be updated? https://github.com/hackforla/website/issues/2025
[x] https://github.com/hackforla/website/issues/1338: Should we remove this issue from the prioritized backlog? The reasons are:
- This is no longer true "Good First Issue are all usually updates/edits to the projects collection."
- There is already information on self-assigning an issue in the Contributing.md: https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#24-claiming-an-issue
- Does the info on working on issues in the Contributing.md cover the information that is asked to be added in this issue? https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-2-how-the-website-team-works-with-github-issues
[x] https://github.com/hackforla/website/issues/2528: Can we re-write this issue and make it into an epic, where we make small issues or good second issues from it? The reasons are:
- Some of the credits exist on the feature branch but need some of the information changed because it has outdated/inaccurate info.
- Some credits need to be created from scratch but the image exists on the feature branch already.
- One credit needs to be created and needs an image added.
- It will make it easier to review each credit.
[x] https://github.com/hackforla/website/issues/2606#issuecomment-1050158878
- [ ] Is this okay?
- [ ] Should I update the Figma design for the project info page with the updated 16px font before I write the issue for devs to work on implementing the changes?
[x] Can we add a complexity missing label?
- [x] I want to add it to this issue in the Ice Box: https://github.com/hackforla/website/issues/2674

Notes from meeting

Bonnie experienced the board not working one of the following:
- After moving an issue
- If someone else is moving stuff on the dashboard
For onboarding survey and dashboard, https://www.hackforla.org/guide-pages/survey-reporting-dashboard-guide
If you are gone for more than a month, close the issue/unassign and when they want to come back, message us and let us know where they left off, how long its been, etc and we will make a decision on a case by case basis. If working on pre-work checklist then can pick up where the left off. If its been over a month and don't have a pre-work checklist, they need to contact us. everyone needs to write us to gain access back to repo.
Hacktoberfest Analysis to be in Ice Box until we get someone interested in leadership to work on it
role: hfla leadership means org leadership

Tasks

[x] Add to lead onboard/offboard checklist to give them access to survey reporting dashboard (Jess)
[ ] ~~CTJ team survey issue needs dependency on #2776 and have action item to request access from Bonnie (Saumil)~~ Moved to a comment on 4/6/22 below
[x] Create label role: dev leads (Jessica)
- [x] Change label for #2919 to dev leads (Jess)
- [x] Review any role: hfla leadership and change if new label makes more sense (Jess)
[x] Check out and discuss https://github.com/hoodiehq/first-timers-bot and hacktoberfest resources for beginners and see if we can apply any of these items to Hacktoberfest (both tech leads)
[ ] Think of how to remove people from the repo (both tech leads)
[x] Prioritize issues according to new milestone labels that were changed towards end of alphabet (Jessica)
[x] Prioritize Changing text size for Getting Started page #2656 (Jessica)
[x] Dev make an issue, including what's causing board crashes, what we have tried, and what automation we have. (Saumil)
[x] Close #1338 with note saying we are closing it because we are audting the wiki and link to the audit issue (Jessica)
[ ] ~~Ask team developers encountering problems/issues where you would like us to improve our instructions in the Contributing.md or Wiki (Saumil)~~
- [ ] ~~Spreadsheet with prs and analysis figuring out why it took so long (Saumil)~~ Moved this to a comment on 4/6/22 below
[x] #2459: Product will make this into an epic and add the links to each issue related to it
[ ] ~~New pr columns need issue(s) written for~~
- [ ] ~~Automation (Saumil)~~
- [ ] ~~Documentation explaining it (Saumil)~~ Moved this to a comment on 4/6/22 below

  PR columns should be
  - Issues that need a reviewer assigned
  - issues that need changes from authors
  - ready for re-review (from the original reviewer)
  - reviewer has approved, waiting for merge team to merge

[ ] Convert issue to epic with small issues: #2528
[x] #2606 have designer make changes to the actual practical project page and not just the individual card (Jessica)
[x] Add complexity missing label (Jessica)
- [x] Then add to #2674 (Jessica)

Items for next week's agenda

Mar 12 '22 06:03 SAUMILDHANKAR

Item for next meeting

[ ] Product to inform devs that a new Wins page has been created in the wiki and needs to be updated
[ ] Dev/PM to spend some of the time at this meeting to discuss with Alyssa how the issue will be progressing going forward including:
- [ ] Alyssa will complete the styling
- [ ] Alyssa will create a separate issue for completing Google AppScripts portion: https://github.com/hackforla/website/issues/2978
- [ ] Put Alyssa's code in a feature branch
- [ ] Where the Google AppScripts for converting to markdown should live: in the Google Doc Guide itself, separately, somewhere else? Currently, there is a copy of the script in Markdown Converter folder on the Website Team Google Drive.
- [ ] Does styling Alyssa is working on and issue #2978 need to be completed before this issue can be worked on: https://github.com/hackforla/website/issues/1515?
[ ] Dev asking Is it okay that the specific credit link isn't the exact same icon?
- Link to code including comment
- Credits page search for "Idea" and click on the "Idea" link.
[ ] How long should time sensitive issues be completed by after they are prioritized, such as Project Profile updates?
[ ] What do we do after all the issues for an epic are written and we are just waiting for those issues to be completed? For example, do we move the epic to a certain column?
- [ ] https://github.com/hackforla/website/issues/2211
- [ ] https://github.com/hackforla/website/issues/2775

Mar 13 '22 17:03 Providence-o

Please add to next meeting, changing out the current image we have on the about page, partner section, for these two orgs

Los Angeles County Homeless Initiative from real-help-lasting-change.svg to https://homeless.lacounty.gov/wp-content/uploads/2018/09/HI_Logo_lasting-change-v3.png

And

Golden Gate University School of Law from ggu-school-of-law.png to https://law.ggu.edu/media/shared/images/logos/2021/law-stack.png

Mar 17 '22 20:03 ExperimentsInHonesty

Mar 19, 2022 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [x] Check to see how new team members are doing
    - [x] Check 2 week inactive label on the in progress column
      - [x] Frontend 2 weeks inactive Last checked 3/19
      - [x] Backend 2 weeks inactive Last checked 3/19
    - [x] Check all open pre-work developers checklists on the board and closed pre-work developers checklist in QA
      - [x] Front End Last checked 3/19
      - [x] Back End Last checked 3/19
  - [ ] Can we improve the prework template based on something we see as a pattern?

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

[x] Taking days off on a weekly basis
- Jessica: Sunday starting after meeting through Tuesday until 4pm or 5pm
- Saumil: Wed
[x] Add Slack reminders to the private website-merge channel for updating secrets so we don't wait until it is broken to do it.

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Front End
- [ ] Back End
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [ ] Jessica
  - [ ] Samuil

New Items

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

[x] Dev/PM to spend some of the time at this meeting to discuss with Alyssa how the issue will be progressing going forward including:
- [x] Alyssa will complete the styling
- [x] Alyssa will create a separate issue for completing Google AppScripts portion: https://github.com/hackforla/website/issues/2978
- [x] Put Alyssa's code in a feature branch
- [x] Where the Google AppScripts for converting to markdown should live: in the Google Doc Guide itself, separately, somewhere else? Currently, there is a copy of the script in Markdown Converter folder on the Website Team Google Drive.
- [x] Does styling Alyssa is working on and issue #2978 need to be completed before this issue can be worked on: https://github.com/hackforla/website/issues/1515?
[x] https://github.com/hackforla/website/issues/2990: Opened today by Matt and self-assigned himself to work on it. It needs a milestone.
[x] How long should time sensitive issues be completed by after they are prioritized, such as Project Profile updates?
[x] Product to inform devs that a new Wins page has been created in the wiki and needs to be updated
[x] Dev asking Is it okay that the specific credit link isn't the exact same icon?
- Link to code including comment
- Credits page search for "Idea" and click on the "Idea" link.
[x] What do we do after all the issues for an epic are written and we are just waiting for those issues to be completed? For example, do we move the epic to a certain column?
- [x] https://github.com/hackforla/website/issues/2211
- [ ] https://github.com/hackforla/website/issues/2775
[x] Changing out the current image we have on the about page, partner section, for these two orgs

Los Angeles County Homeless Initiative from real-help-lasting-change.svg to https://homeless.lacounty.gov/wp-content/uploads/2018/09/HI_Logo_lasting-change-v3.png

And

Golden Gate University School of Law from ggu-school-of-law.png to https://law.ggu.edu/media/shared/images/logos/2021/law-stack.png
[x] Dev asking about https://github.com/hackforla/website/issues/2455. "Submit your Pitch" is a menu item but the current "Submit a Pitch" button opens an email client. Did you want the same thing to happen when it is clicked in the menu?
[ ] Dev saw https://github.com/hackforla/website/issues/2455#issuecomment-1017723029 but not sure if Bonnie addressed this.
- [ ] Related comment in another issue: https://github.com/hackforla/website/issues/2686#issuecomment-1018927250
[x] Requesting pr reviewers
- [x] How long to wait before asking for your pr to be reviewed?
- [x] How to ask for reviewers?
- [x] What happens if assigned reviewers have not reviewed the pr after x amount of days? What is the value of x?
- Notes from Tech Leads:
  - Don't ask for reviewers because you don't know who is active.
  - Also, other members may look for prs without 2 reviewers yet and if they see there are reviewers assigned, your pr will not be reviewed because they assume other people have volunteered for their pr to be reviewed.
  - We assign reviewers at Sun and Tue meetings.
  - If it's been over 72 hours and nobody has been assigned, please ask in the hfla-site-pr channel to ask if someone will review their pr.
  - If it doesn't get reviewed, then we will address at the meeting.

Notes from meeting

We just added the following to data science/PM agenda: Task for data science or research: Take a look at the pre-works for devs to see how long it takes them to do each task in the checklist in a spreadsheet.
For issue #2455 submit your pitch sub menu item should function the same as the current button for it.

Tasks

[x] Edit issue #2978 (Jess)
- [x] Add dependencies to issue #1515 and put in ice box (Jess)
[x] Look out small issues and see if there were worked out of order in the last month (to figure out why time sensitive small issues were not picked up before others) (did this with Bonnie at Sunday meeting, so it's completed)
[ ] Create issue: In the site architecture wiki under contents fix the link to pages section (Jess)
[ ] ~~Finish updating the wins wiki page (Saumil)~~
- [ ] ~~Make sure to include information for automations process and tasks devs do as relates to wins~~ Moved this to a comment on 4/6/22 below
[ ] Create issues to make a wiki page for each page on our website similar to the wins wiki page (both tech leads)
[ ] Edit #2775 making all issues as dependencies (Jess)
- [ ] Add action item to each of the issues to release dependency
[x] Epic #2211: put dependency label on it, add to ice box, add action item to issue to release (Jess)
[x] Good small issue for current image we have on the about page, partner section, for these two orgs. (Jess)
- [x] Los Angeles County Homeless Initiative from real-help-lasting-change.svg to https://homeless.lacounty.gov/wp-content/uploads/2018/09/HI_Logo_lasting-change-v3.png
And
- [x] Golden Gate University School of Law from ggu-school-of-law.png to https://law.ggu.edu/media/shared/images/logos/2021/law-stack.png
[ ] ~~Figure out what are the best practices with resetting secrets. (Q: How often to reset, general research) (Saumil to make an issue to explore the questions, role dev leads label)~~ Moved this to a comment on 4/6/22 below
[ ] Create reminders in the website-merge slack channel to update secrets. (Jess)
[ ] Automation to create an issue to notify us the secret has not been updated by a certain date, such as the date after. Person would need to update the secret and then update the date in a file, and the automation checks the file. (Discussion needed by both tech leads)

Items for next week's agenda

Mar 19 '22 16:03 SAUMILDHANKAR

Providence to reach out to the Noun project and inform then that we use their images on our website and attribution on our credits page. Sometimes the images stop appearing on the noun projects site. What (if anything) do they want us to do in cases like this.

Send links to HFLA credits page
Example credit icon affected

I realized it after I posted this image, this is another vendor Freepik. Same issue.

Mar 19 '22 23:03 Providence-o

website website copied to clipboard

HfLA: Dev/PM Agenda and Notes

Overview

Action Items

Resources/Instructions

Template

Prior and upcoming meetings

2021-12-18 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next weeks agenda

2022-01-07 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next weeks agenda

2022-01-02 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next weeks agenda

2022-01-15 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next week's agenda

2021-01-22 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next week's agenda

2022-01-27 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next week's agenda

2022-01-29 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next week's agenda

2022-02-05 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next week's agenda

2022-02-12 Meeting Agenda

Prework to prep for meeting

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

Recurring items:

New Items

Notes from meeting

Tasks

Items for next week's agenda

2022-02-19 Meeting Agenda

website
website copied to clipboard