HfLA: DEV TEAM Meeting Agenda Sunday 🧣

[Aveline-art]

Overview

This issue tracks the agenda for the HFLA website team and weekly roll call.

Weekly Action Items

• [ ] Designate a note taker who will follow up on issue creation
• [ ] Make announcements
• [ ] Monthly Workflow Demos
  • [ ] 1st Sunday: No demo because all leads meeting
  • [ ] 2nd Sunday: Progress Report creation
  • [ ] 3rd Sunday: Pull Request review demo
  • [ ] 4th Sunday: Issue creation, including labels and issue approval process
• [ ] Do below agenda items
  • [ ] Go through project
  • [ ] Dev team column
  • [ ] In-progress
    • [ ] Help wanted label
    • [ ] To Update ! label
  • [ ] Pull requests

Weekly Agenda Markdown

### Agenda for monthAsText dd, yyyy
Facilitator: TBD

**Welcome to the Sunday All Website Teams meeting. Thank you for joining us!**

## Announcements & Reminders
  - [ ] https://www.vrms.io/
  - [ ] Devs only team meeting on Tuesdays from 7-8pm PST
  - [ ] Office hours on Thursdays from 7-8pm PST 
  - [ ] No meetings for the first 7 days of every month
  - [ ] Open the floor for celebrating any announcements

## Meeting items 
### [Pull Requests](https://github.com/hackforla/website/pulls)
  - [ ] Go over open PRs to assign reviewers
    - [ ] Check on any PRs with `Changes requested`
    - [ ] Explain how to re-request a review after you make the requested changes
  - [ ] All developers are expected to review pull requests 
  - [ ] Encourage team members to review open PRs
    - [ ] [How to Review Pull Requests](https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests)
    - [ ] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
    - [ ] [On-call for Reviewing PRs](https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0)

### [Project Board](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=)
- [ ] Explain the project board and the flow of issues between status columns
- [ ] Explain how to use the various views: "@me", "dev: GFI", etc.
- [ ] Check the ["In Progress (actively working"](https://github.com/orgs/hackforla/projects/86/?filterQuery=status%3A%22In+progress+%28actively+working%29%22+label%3A%22Status%3A+Help+Wanted%22) status column for issues with `Status: Help Wanted` label 
- [ ] Check the ["Questions/In Review"](https://github.com/orgs/hackforla/projects/86/?filterQuery=status%3A%22Questions+%2F+In+Review%22) status column

### HFLA Journey Advice
- [ ] [Being a Part of the Hack for LA Dev Team](https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team)

### To bring up with UI/UX

### To bring up with PM

Example Agenda

Agenda for November 9, 3012*

- [ ] Discuss when to have a meeting about making origami - [ ] Get feedback on 3 different brands of folding paper - [ ] Create issue about the origami ship project

*Note: Date is written out because of cultural differences in date formatting.

[JessicaLucindaCheng]

Agenda for Mar 27, 2022

Facilitator: Jessica Cheng

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Ryan Cahela (RyanCahela) took notes at Tuesday's meeting and got pr 3006 merged
• Tamara Snyder (tamara-snyder) reviewed pr 2962 (including re-review), 3007, 2977, 3013, 3017
• Adolf Schmuck (answebdev) reviewed pr 3001, 3006, 3010 (including re-review)
• Devin Krizwold (Sparky-code) reviewed pr 3007, 3006, and writing issue 3018
• Luke Karis (luke-karis) reviewed pr 2962
• Carlos Perez (Carlos-A-P) reviewed pr 3001
• Saumil Dhankar (SAUMILDHANKAR) reviewed pr 2790, 2988, 3010, 2962, 3012
• Harshita Sao (harshitasao) reviewed pr 3013
• Steve Carter (scarter31191) reviewed pr 3012 and got pr 3013 merged
• Jaret Balba (Jaretzbalba) got pr 3007 merged
• Jovanni Morales (jnmrles) got pr 3001 merged

Announcements

• [x] Will open the floor for any announcements

Reminders

• [x] No meetings from April 1st-7th
• [x] Work only on one of each of the following complexity issues: good first issue, good second issue, small.
• [x] Wait for your pr to be merged before picking up a new issue. (Show what a merged pr looks like.)
• [x] Office hours on Thu from 7-8pm Pacific. The room will be open for any questions/help, or if you want to see what is being worked upon.

Meeting items

• [ ] Pull requests (PRs)
  • [x] All developers are expected to review pull requests. (Aim for every pr you create, review at least 2 prs.)
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets if they have completed their good first and second issues already.
  • [x] You can self-assign a pr to review yourself at any time.
• [x] Team survey: check if members are using the zoom link from Slack, Google calendar, join us wiki or project board cards onboarding info column
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column with label:"Status: Help Wanted"
  • [x] Questions/In Review column with label:"role: front end" or label:"role: back end/devOps" .
• [x] Monthly Workflow Demo: Pull Request review demo
• [ ] Discussion and feedback on the issue creation process
• [ ] Demo on how to resolve merge conflicts?

To bring up with PM/UI/UX

Notes from meeting

Click for notes

Note-taker: Sarah Sanger Attendees: - Jessica Cheng - Tamara Snyder - Steve Carter - Ryan Cahela - Frank Stephanski - Utkarsh Saboo - Ben Montgomery - Kathryn Conway - Carlos Perez - Adolf Schmuck - Hiram Riddle - Anna Filatova - Sarah Sanger - Gabriel Garcia - Jesica announced no meetings for general & invited those who are interested to leadership - Jessica reminded us to work on first, second and medium if we haven't or to leave them for beginners - Jessica reminded us that we can do more than one medium issue/large issue (but only one at a time) - Jessica reminds us about office hours thursday 7-8 (not the first week of the month) - Jessica reminds us about how to review prs - Jessica assigns pr's - Jessica reminds us about the On-call pr schedule https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0 - Jessica refers us to the wiki on how to create an issue https://github.com/hackforla/website/wiki/How-to-create-issues - Jessica shows us where to create a new issue (she recommends issues to new issues & select a template) https://github.com/hackforla/website/issues/new?assignees=&labels=&template=blank-issue-template.md&title= -she recommends to check by label & keyword (in issues) to make sure there isn't already an issue for that & - Jessica explains the approval process -Saumil goes over where to find the links to the meetings & asks which one folks are using - Jessica checks for help wanted labels, Questions in Review - Jessica demos how to do a pull request - update your forked gh-pages and then locally git checkout gh-pages and then git pull to get changes locally on your computer - that the branch comes from the same person who is completing the issue - check the branch to go into & come from - check/read the linked issue number - check for screen shots or no visual changes statement - pull the branch - if you have already pulled the branch before and you are re-reviewing, make sure to delete the branch from your previous review before using the commands given by github-bot in the pr to pull the branch again for a re-review - make sure gh-pages is updated before pulling Jessica goes over merge conflict - go into file & delete the one of the code options that is trying to go on the same lines (see which change you recently made) - gives us link to vscode solution to merge conflicts https://code.visualstudio.com/docs/editor/versioncontrol - Tamara ask Providence about Bonnie's bad linkden address and how to correct that - and if there can be a change to the google form to validate links - or how to go about validating links before putting them on the website Jessica reminds us of her time off - Jessica: sunday - Tuesday - Saumil: Wednesday

[JessicaLucindaCheng]

For next Sunday agenda, revisit resolving merge conflict demo and do it more completely.

[SAUMILDHANKAR]

Survey results for team meeting link preference: Total 14 Members using team meeting link from Google calendar (7): Ben, Sarah, Saumil, Jessica, Carlos, Kathryn, Steve Members using team meeting link from Slack (4): Utkarsh, Tamara, Frank, Adolf Members using team meeting link from Join us wiki (0) Members using team meeting link from project board (0) No response 3

[ExperimentsInHonesty]

Please check this at the end of your team meeting today https://github.com/hackforla/website/issues/2728#issuecomment-1086903359 - hopefully they have updated by then.

[JessicaLucindaCheng]

Agenda for Apr 10, 2022

Facilitator: Jessica Cheng

• [x] Ask design before going to break out rooms about green circles https://github.com/hackforla/website/issues/2392#issuecomment-1089659051
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Note-taker: Sarah Sanger

Let's celebrate our contributions/wins since last team meeting

• Adolf (answebdev) reviewed pr 3020 (and re-reviewed), 3033, 3037, merged 2 pr
• Ryan (RyanCahela) got pr 3008 merged
• Jessica (JessicaLucindaCheng) reviewed pr 3014, 2723, merged 2 prs, wrote issues 3022, 3023, 3025, 3026, 3027,
• Harshita (harshitasao) got pr 3014 merged, reviewed pr 3037
• Carlos (Carlos-A-P) reviewed pr 2723, got pr 2977 merged
• Saumil (SAUMILDHANKAR) reviewed pr 2790, 2962, 3033, merged 4 prs, wrote issue 3031
• Kazushi (KazushiR) got pr 2790 and 3037 merged
• Kathryn (kathrynsilvaconway) reviewed pr 2723 (and re-reviewed), 3020, 2977, got pr 3029 merged, and took notes at last Tuesday meeting.
• Luke (luke-karis) reviewed pr 2962
• Devin (Sparky-code) reviewed pr 3030
• Jaret (Jaretzbalba) reviewed pr 3030, got pr 3020 merged
• Bonnie (ExperimentsInHonesty) got pr 3033 merged
• Frank (frankstepanski) got pr 3030 merged
• Tamara (tamara-snyder) reviewed pr 2962, 2977, 3036, merged 1 pr

Announcements

• [x] Will open the floor for any announcements
• [x] Welcome Adolf to the merge team
• [x] Requesting all team members not to take screenshots in dark mode as may use the images in our guides and we want all images to be consistent. Thus, screenshots should be taken in light mode.
• [x] If you have experienced project board sluggishness or frequent crashing, please add your comments (with gifs if possible) to #3031

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Survey: how much time did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue (This should be posted in your pre-work checklist issue. Then post a link to your pre-work issue in the chat)
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted"
  • [ ] Questions/In Review column
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Sun, Apr 17, Demo will be issue creation, including labels, milestone usage, and issue approval process. Does anyone want to volunteer to do it? Devin
• [x] Monthly Workflow Demo: Progress Report creation. Would anyone like to volunteer to demo this?

To bring up with PM/UI/UX

• [x] PM: Devin's issue https://github.com/hackforla/website/issues/2061 requires clarification

• [x] PM: Similar vague issue problem https://github.com/hackforla/website/issues/2173.

• [x] Design: Carlos's pr https://github.com/hackforla/website/pull/2977 encountering Galaxy Fold problems

• [x] PM: Problem: The 'size missing' label automation will show a size missing because we changed the good first issue label to prework label for the pre-work checklists. Temporary solution: Add a size point label to UX and Design pre-work templates.

  • [x] PM: Follow-up question, is the prework going to be a complexity label? If yes, is it going to be complexity: prework or prework? --> Ans: prework will be part of complexity labels but will keep the wording just as "prework" label.

• [x] PM: Should we add an action item in the pre-work dev checklist: --> Ans: Yes. PS: Added it in pre-work.

  • [x] Copy this question into a new comment below and answer it:

    How much time did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue?

• [x] PM: For this issue https://github.com/hackforla/website/issues/3031, what do you mean by the action item "Write up the issue (trying to be as factual as possible with a few words)"? Do you mean describe the problem you are encountering? --> Ans: Means add details about the issue.

• [x] Breakout rooms again to answer more questions.

Notes from meeting

Click for notes

Jessica goes over wins/contributions Opened the floor for announcements Jess reminds us not to take screenshots in darkmode - so images are consistent - so you can reuse shots Asked for reporting on project board performance
- moving issues from one column to another
- waiting for a github message
- filtering issues by clicking on a label
- opening projectboard in more than one tab
- searching for a keyword
- https://github.com/hackforla/website/issues/3031
- put a gif demonstrating the performance issue
- screen shot internet speed Jess assigned pull requests - but there weren't any available for assigning Jess goes over how to review pull requests - https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests - goes over how to assign yourself to pr - reminds us to assign ourselves to the OnCall PR sheet - https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0 Jess has us take a survey: - How much time did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue? - go to issues (on github website) prework and close it if it is not closed - but then post how long it took to complete it - and post it in chat - https://github.com/hackforla/website/issues/2683#issuecomment-1094333071 - https://github.com/hackforla/website/issues/2664#issuecomment-1094333189 - https://github.com/hackforla/website/issues/3009#issuecomment-1094333020 - https://github.com/hackforla/website/issues/2782#issuecomment-1094333680 Jess goes over office hourse on Thursday 7-8 Jess demos how to do a progress report (every week) - recommends doing it before sunday meetings Progress: what you have completed so far and what is left Blocker: what's stopping process, can add the help wanted label & post a slack message on the hfla or bring it up during a meeting Availability: hours you have this week to work on it ETA: when you think you'll be done with this issue can add pictures Jess introduces the idea us taking turns doing the demos (creating issues, labels, mielstone usage, issue approval, progress report creation) - Devin offers to demo next week Jess introduces us to Chrome extension GoFullPage to take a full page screenshot - https://chrome.google.com/webstore/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl?hl=en Carlos mentions another way to take a full page screenshot - you can also take full screen shot in dev tools > toggle device toolbar > click on the three dots to the top right >capture full size screenshot Samuil & Michael go to a private room - to go over how to pick a good first issue Adolf goes over a question he has on a specific issue - how to add a link to a nav bar if it's an email - add the email in the nav bar file Then Bonnie & crew joins us - QA review: decides to use 'ready for dev leads' and move issues into new issue for dev lead review - adding alt text to unique images with wording on the HackForLA website (that isn't elsewhere on the page) Carlos & Jess go over Galaxy Fold Issue - https://github.com/hackforla/website/pull/2977#issuecomment-1094334610 - Carlos made a fix - Bonnie doesn't want to make the fix without the data of how many Galaxy Fold users visit the site Devin goes over how scope expanded - https://github.com/hackforla/website/issues/2061 - https://docs.google.com/spreadsheets/d/10-c3jpf4vtXKcwLiBC4Z3wqN777xlxbErHS4QNq-e8o/edit#gid=1157217661 - he then explains the spreadsheet to Bonnie (who then changes it) Bonnie goes over the Design Sytem: Audit Sticky Side Nav element #2173 - makes changes to clairify an issue - create a standard for sticky side nav component

[ExperimentsInHonesty]

• https://github.com/hackforla/website/pull/2977#issuecomment-1094334610

[JessicaLucindaCheng]

Agenda for April 17, 2022

Facilitator: Jessica Cheng

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Note-taker: Tamara

Let's celebrate our contributions/wins since last team meeting

• Saumil (SAUMILDHANKAR) reviewed pr 3036, merged pr 3036
• Kathryn (kathrynsilvaconway) got pr 3036 merged, reviewed pr 3044, 3043, 3046
• Jaret (Jaretzbalba) reviewed pr 3046
• Sarah (blulady) reviewed pr 3043
• Jessica (JessicaLucindaCheng) reviewed pr 3043
• Devin (Sparky-code) reviewed pr 3046
• Adolf (answebdev) merged pr 3046, reviewed pr 3057
• Carlos (Carlos-A-P) reviewed pr 3057

Announcements/Reminders

• [x] Will open the floor for any announcements
• [x] You may work on or review a pr that says to work from a feature branch. Thus, the pr may be merged into one of the feature branches or you may need to start work by pulling the feature branch.
• [x] Jessica hasn't been feeling well that last few days and is behind in getting back to GitHub comments and Slack messages.
• [x] Jessica will be leaving the team May 7 or 14 (tentative dates).

Meeting items

• [x] Try Jekyll version 3.9.0 in local branches with the team
• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [x] label:"Status: Help Wanted"
  • [ ] Questions/In Review column
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Next Sun, Apr 24 demo will be: Pull Request review demo. Does anyone want to volunteer to demo it? Jessica
• [x] Today's Workflow Demo: Issue creation, including labels, milestone usage, and issue approval process, facilitated by Devin Krizwold

To bring up with PM/UI/UX

• [x] Design: Is it possible to get image specifications for sponsor images on the homepage? As per the following comment: https://github.com/hackforla/website/pull/2984#issuecomment-1094476174, it is difficult to exactly replicate how the sponsor images currently look like on the homepage. (Ans--> Bonnie suggested that the homepage sponsor images should look like the images on About page. We can try copying the code from the about page for the images and see if that works. Saumil will follow up)
• [x] PM: Docker is not building up for some of our new members that joined this week. Here is the beginning of the thread with the error log: https://hackforla.slack.com/archives/C4UM52W93/p1649956155001459. Based on the following comment in the thread can we update the docker-compose.yml file: https://hackforla.slack.com/archives/C4UM52W93/p1650062694670859?thread_ts=1649956155.001459&cid=C4UM52W93 (Eric Vennemeyer will write the issue to fix this and then work on that issue. Also, follow up with Trisha's question on how to fix this problem)
• [x] PM: What is the overall plan for the Design System webpages? --> Ans: Not doing it now because Design System changes too much then to have to manually update the webpages. Then it will never be up to date. It's too much work right now. (Jessica will follow-up on writing a decision record)
  • [x] Follow up question: Are the mds to be edited after the audit of a component? For example, after this audit issue is completed https://github.com/hackforla/website/issues/2061 and then the components are standardized in this issue https://github.com/hackforla/website/issues/2226 completed, should we write an issue for editing _design-system/components/page-card.md?--> Ans: No. Jessica will follow-up in Devin's issue.
• [x] CTJ team would like to know the usage stats on the HfLA website by browser and browser version. We can get that from Google Analytics but would need your help to access that account. Related comment: https://hackforla.slack.com/archives/C4UM52W93/p1650083395389389 (both tech leads will follow up. Saumil will let them know the ETA on getting the information on slack)
• [x] PM: https://github.com/hackforla/website/issues/1850: Do you know anything about the status of this issue? What it encompasses? (Jessica will add a link of the decision records of the Design System webpages on this issue)
• [x] PM: Where should we save the remark about research following up after homepage launch so it doesn't get forgotten? https://github.com/hackforla/website/issues/2481#issuecomment-1100764836 --> (Saumil will add to Research/PM agenda)

Notes from meeting

Click for notes

Hack for LA Meeting Notes - April 17, 2022 Note-taker: Tamara Snyder Dev meeting Meeting attendance: Kathryn Silva Conway Saumil Jessica Cheng Eric Utkarsh Saboo Trisha Johnson Steve Carter Devin Krizwold Adolf Schmuck Tamara Snyder Congrats to all who made contributions this week! Announcements: Jessica demonstrates how to read through issues and check if you need to pull from a feature branch on an issue Jessica hasn’t been feeling well and is working to catch up with GitHub comments and Slack messages Jessica is moving to another HfLA project team on May 7 or May 14 Meeting Items: Issues with Docker for new members Eric thinks Ruby 3 is incompatible, so we need to downgrade to older version of Jekyll which uses an older version of Ruby (2.7) in docker-compose.yml Steps to fix: Make sure gh-pages is up to date Make new branch from gh-pages Change image line (line 4) in docker-compose.yml Assigned reviewers for PRs Discussed reviewing and re-reviewing PRs and how to see latest code pushed Went over Developer On-Call sheet All team (UX Research) Get Analytics on “Share your wins” button on Wins page Vivian Lin wants to know if we can track metrics on the “Share your wins” button in Google Analytics For instance, if people leave the form on page three, research wants to know so that they can investigate Bonnie thinks this is not possible within the form We could think about converting the Google form to a form on the site, but then we would need a backend or way to send data to the Apps Script We already have a spreadsheet for the Wins data. How would we MVP: Track the “Share your wins” button and the “Submit” button on the form to see how many responses are opened vs submitted Steve Carter will investigate further and write this issue Mismatched sets of sponsor images on current version of website Bonnie says to copy the images from the About page to the Home page so that they are the same size That way we are referring to the same image folder Delete redundant image folder Jessica asks Bonnie about account for Google Analytics so that she can get usage stats about browser/browser version to the CTJ team Website for design system: Design system in Figma is not finished and keeps experiencing changes Site will always be out of date Low priority project/tech debt Saumil is going to open a ticket with GitHub since a whole organization cannot do it He is going to update [webadmin@hackforla.org](mailto:webadmin@hackforla.org) so everyone can see updates Bonnie creates filters so that tech leads will receive updates Bonnie demo on creating desktop shortcuts for gmail Go to chrome://settings/manageProfile and click “create desktop shortcut” at the very bottom Valuable for using different emails for testing Handy to have a folder for various shortcuts Back to Dev meeting Devin gives demo on issue creation and adding labels to issues. More info can be found in the Wiki There are only four required labels: Feature, Role (front-end/back-end), Size (how many points?), and Complexity (Good First Issue, Good Second Issue, Small, Medium, Large) Bonnie adds that “The Overview should always be ‘We need to do X for Y reason’” Bonnie talks about Standardizing the HfLA Design System issue Issue got scope creep because of vague issue overview Started with discussions and audits with fixes to be made Conversations in comments made the scope grow larger Went through three lead teams Tasks were to Create reusable components for the website in Figma Page for components turned into full webpage designs Separate pages on the site were built as individual websites and didn’t reuse classes An audit was done, which led to design system for various elements Only worked for buttons and may still be out-of-date Trying to standardize designs and classes

[JessicaLucindaCheng]

https://hub.docker.com/r/jekyll/jekyll/tags

[JessicaLucindaCheng]

Agenda for Apr 24, 2022

Facilitator: Jessica Cheng

Before Breakout Rooms

• [x] Let UX team know Simone isn't going to be at the meeting today
• [x] Reminder no meetings the 1st-7th of every month. There will be an all leads meeting on Sun, May 1st; if you are interested in joining, please put your email in the chat and we will add you.

Dev Meeting

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Note-taker: Kathryn

Let's celebrate our contributions/wins since last team meeting

• Tamara (tamara-snyder) reviewed pr 2962, 3076, 3072, 3075, took notes at Tuesday's meeting, and wrote a report of issue 2141.
• Trisha (trishajjohnson) got pr 3072 merged
• Erick (eodero) got pr 3073 merged
• Carlos (Carlos-A-P) reviewed pr 3072
• Devin (Sparky-code) reviewed pr 3076, 3073
• Jessica (JessicaLucindaCheng) reviewed pr 3043 and reviewed report for issue 2141
• Saumil (SAUMILDHANKAR) reviewed pr 2962

Announcements/Reminders

• [x] Will open the floor for any announcements
• [x] When opening a pr, please make sure any changes in the Files Changed are part of your issue.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Question: Do you see Dependabot alerts?
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted"
  • [x] Questions/In Review column
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Monthly Workflow Demo: Pull Request review demo

To bring up with PM/UI/UX

Notes from meeting

Click for notes

Note-taker: Kathryn Silva Conway Notes from Dev meeting on 4/24: Saumil Trisha Johnson Carolos Perez Adolf Schmuck Frank Stepanski Erick Odero Hiram Riddle + If you are changing your Jeckyll image 4.2.0 as a temporary fix to get Docker to run, please make sure you change it back when you push your code. We don't want to make this change permanently until we have done more research so that the fix can be applied uniformly. + Reminder that there will be no meetings from May 1-7, except for the team lead meeting. + Reminder that Bonnie will be taking off the 21st through the 27th of each month from now on. + All Developers are expected to review PRs. Our goal is to review 2 PRs for every 1 we submit. Be sure to add your availability/ETA in a comment. + Trisha & Kathryn were assinged to PR reviews. + Github is giving everyone a warning that node-fetch has a security vulnerability and needs to be updated. We are in the process of creating an issue to address this. + If you use the "status help wanted" label on an issue, be sure to leave a comment on the issue to let us know know what kind of help you need and also leave a comment on the slack channel. This will alert everyone that you need help. + We all introduced ourselves and welcomed new members Olanrewjau and Khadijah. + Jessica gave us a demo on reviewing pull requests.

[JessicaLucindaCheng]

Agenda for May 8, 2022

Facilitator: Jessica Cheng

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Note-taker: Saumil

Let's celebrate our contributions/wins since last team meeting

• Adolf (answebdev ) answering questions, reviewed and merged pr 3083, reviewed pr 3108, 2984
• Devin (Sparky-Code) answering questions, reviewed pr 3076
• Carlos (Carlos-A-P ) answering questions, reviewed pr 3086
• Jessica (JessicaLucindaCheng) reviewed pr 3076, pr 2723, pr 3043, merged pr 3043, 3076
• Jay (JayBarbanel) got pr 3076 merged
• Wilny (Wny-Duong) reviewed pr 3083
• Jaret (Jaretzbalba) got pr 3043 merged
• Ryan (RyanCahela) reviewed pr 3083
• Matt (matt-arofin) reviewed pr 3086
• Saumil (SAUMILDHANKAR) wrote issues 3088, 3089, 3090, 3091, 3092, 3093, 3094, 3095, 3096, 3097, 3098, 3099, 3100, 3101, 3102, 3103, 3104, 3105, 3106, 3107, 3109, 3110, 3111, 3112, merged pr 3108
• Luke (luke-karis) reviewed pr 2984, 3086
• Harshita (harshitasao) reviewed pr 3108

Announcements

• [x] Will open the floor for any announcements

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Assign issues with label:"time sensitive" that are 30 days or older or label:"Status: Urgent" that are 14 days or older
  • [x] https://github.com/hackforla/website/issues/2728
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted"
  • [x] Questions/In Review column
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Next Sun (May 15) demo will be: Pull Request review demo. Does anyone want to volunteer to demo it?
• [x] Monthly Workflow Demo: Progress Report creation

To bring up with PM/UI/UX

• [x] For Design and PM: https://github.com/hackforla/website/issues/2802#issuecomment-1110506971
• [x] Ask Bonnie to make a vault for 2FA recovery codes
• [x] Ask Bonnie if there will be new members onboarded on Mon, May 16

Notes from meeting

Click for notes

Notetaker: Saumil Attendance: Saumil Jessica Devin Hiram Trisha Olanrewaju Adolf Kathryn Ahmad Jessica's last day with the website team is June 8. Trisha would be out of town May 20-22. Devin would have reduced availability in the coming week. Assigned PRs to review and went over all PRs to check progress and blockers. Discussion on the best practices to take meeting notes. Discussion with design to determine next steps for issue #2464: [Comment](https://github.com/hackforla/website/issues/2464#issuecomment-1120468995)

[JessicaLucindaCheng]

Agenda for May 15, 2022

Facilitator: Jessica Cheng

• [x] Everyone introduce yourself
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Note-taker: Carlos

Let's celebrate our contributions/wins since last team meeting

• Jessica (JessicaLucindaCheng) created issues 3129, 3130, 3131 and updated the feature-homepage-launch branch
• Saumil (SAUMILDHANKAR) created issue 3132, updated feature-tech-dropdown branch, facilitated Tuesday's meeting, and merged pr 3134
• Adolf (answebdev) reviewed pr 3134
• Luke (luke-karis) took notes at Tuesday's meeting

Announcements/Reminders

• [x] Will open the floor for any announcements
  • [x] Jessica will be taking days off from Sun, May 15th (starting after All Team Meeting) until Tue, May 24th (right before Dev Team Meeting).
    • [x] Thank you to Devin for stepping up to facilitate the meeting on Sun, May 24th.
    • [x] Thank you to Saumil for covering my Sunday on-call day for pr reviews.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [ ] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Assign issues with label:"time sensitive" that are 30+ days or label:"Status: Urgent" that are 14+ days since it was added to the Prioritized Backlog column
  • [x] https://github.com/hackforla/website/issues/3082
  • [x] https://github.com/hackforla/website/issues/2955
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted"
  • [ ] Questions/In Review column
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Next Sun (May 24th) demo will be: Issue creation, including labels and issue approval process. Does anyone want to volunteer to demo it?
• [x] Monthly Workflow Demo: Pull Request review demo

To bring up with PM/UI/UX

• [x] For Design; https://github.com/hackforla/website/pull/2984

Notes from meeting

Click for notes

Notes for Sunday 5/15/2022 meeting Note-taker: Carlos Perez Attendence: Jessica Cheng Carlos Perez Saumil Julian Smith Devin Krizwold Fank Stepanski Jason Yee Khadija Ibidapo Rejoice Devin to re-review issue #2355 Plan to check on issue #3085 again in Tuesday's meeting Discussed how to review pull requests Didn't need to assign any PRs to review and checked on Progress for current PRs and blockers Design team wants to share design with website dev team: - Bonnie told one of designers to present work to dev team and determine what frame is the best. Issue #3034 - Description page: # 3 was chosen - Discussed with design team to go over Jason's issue.

[Sparky-code]

Agenda for May 22nd, 2022

Facilitator: Devin Krizwold

• [ ] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Adolf (answebdev) reviewed 3163, 3158, 3134, 3162, merged 3163.
• Harshita (harshitasao) reviewed pr's 3163, 3159
• Jarat (Jaratzbalba) reviewed pr's 3159, 3134, 3162, 3146
• Gerardo (geedtd) got pr 3163, 3159 merged
• Tamara (tamara-snyder) reviewed, 3158, 3160, 3146 merged 3159, 3160, 3158
• Julian (juliansmith0) got 3160 merged
• Seth (scorbz9) got 3158 merged
• Ryan (RyanCahela) got pr 3134 merged
• Saumil ((SAUMILDHANKAR) merged 3134
• Thank you all for being here!

Announcements

• [ ] Will open the floor for any announcements
• [ ] Devin (sparky-code) will be picking up Sundays going forward as on-call for the merge team.
• [ ] Bonnie & Jessica will not be at this meeting since they are on vacation
• [ ] Please update your zoom so that you can access 'whiteboard' which we will be using going forward

Meeting items

• [ ] Pull requests (PRs)
  • [ ] All developers are expected to review pull requests
  • [ ] Go over open PRs to assign reviewers
  • [ ] #3161 (?) Alyssa (alyssabenipayo) may be joining to discuss
  • [ ] Helpful link: How to Review Pull Requests
  • [ ] Allow some time in the meeting for all reviewers to add ETA and availability
  • [ ] Check on any prs with "Changes requested"
  • [ ] #3162 (Trishajjohnson)
  • [ ] #3146 (macho-catt)
  • [ ] #3087 (Jaretzbalba)
  • [ ] #3044 (PMKnight)
  • [ ] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [ ] Assign issues with label:"time sensitive" or label:"Status: Urgent" that are 30 days or older
  • [ ] #3031
  • [ ] #3082
  • [ ] #2955
  • [ ] #2777
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] #2625
  • [ ] #1562
  • [ ] #1563
  • [ ] #1566
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted"
  • [ ] Questions/In Review column
• [ ] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [ ] Next Sun (Mmm DD) demo will be: PR Review. Devin will be demoing it
• [ ] Monthly Workflow Demo: Issue Creation w/ Devin

To bring up with PM/UI/UX

Review of issues 1562, 1563, 1566 < May all be redundant to https://github.com/hackforla/website/issues/2572

Notes from meeting

Click for notes

Attendence: - Julian Smith - Carlos Perez - Devin Krizwold - Saumil - Khadijah Ibidapo - Adolf Schmuck - Murtaza Mogri - Frank Stepanski - Hiram Riddle - Sarah S - Olanrewaju-Ak - Didn't need to assign any PRs to review and checked on progress for current PRs and blockers - Need to come back to issue #2777 to assign a dev to work on it - Need to reach out to Steve about issue #2625 - Need to check up with jessica on issue #1562 to see if it needs to be closed - Devin demoed how to review a pull request

[Sparky-code]

@Sparky-code next week's PR review demo

[JessicaLucindaCheng]

Agenda for May 29, 2022

Facilitator: Jessica Cheng

• [x] Nominate a note-taker who will take notes during the meeting. Note-taker: juliansmith0
  • [x] Please note the names of members present in the meeting as well.
  • [x] After the meeting, Slack message the Technical Leads with the notes.

Let's celebrate our contributions/wins since last team meeting

• Harshita (harshitasao) for reviewed pr 3172
• Devin (Sparky-code) for merged pr 3085, 3172, and reviewed 3173, 3075 (and merged it)
• Adolf (answebdev) for reviewed pr 2984, 3162, 3176
• Kathryn (kathrynsilvaconway) for reviewed pr 3174
• Trisha (trishajjohnson) for reviewed pr 3173, 3174
• Tamara (tamara-snyder) merged pr 3174
• Carlos (Carlos-A-P) reviewed pr 3086
• Jessica (JessicaLucindaCheng) re-reviewed and merged pr 2723
• Utkarsh (usaboo) reviewed pr 2984

Announcements/Reminders

• [x] Will open the floor for any announcements
• [x] We are looking for 2 new Tech Leads if you are interested in becoming a Tech Lead.
• [x] Working on a guide for your CoP should be when people are waiting for their prs to be reviewed and merged because guides don't have a timeline. Thus, the priority should be on the issue being worked on for this team first.
• [x] Welcome Jaret to the merge-team.
• [x] New developers might face an error while setting up their dev environment, please take a look at the temporary fix in our slack channel.
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: No Sunday nor Tuesday meetings and no Thursday office hours the 1st-7th of every month as it is a planning week.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Monthly Workflow Demo: PR Review facilitated by Devin
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted"
  • [ ] Questions/In Review column

To bring up with PM/UI/UX

• [x] For PM: Answering this https://github.com/hackforla/website/issues/3153#issuecomment-1138445664, is the following definition accurate?

  Technologies are any software, frameworks, or anything else used by developers on your team.

• [x] For PM/Design: https://github.com/hackforla/website/pull/3087#discussion_r884293946

Notes from meeting

Click for notes

Note-taker: Julian Smith IN ATTENDENCE: Jessica Cheng Julian Smith Saumil Kathryn Silva Conway Frank Stepanski Carlos Perez Adolf Schmuck Devin Krizwold Trisha Johnson Tamara Snyder Utkarsh Saboo Alan Zambrano Hiram Riddle 2 NEW TECH LEADS NEEDED - Last actual meeting Jessica and Saumil will be in attendence will be Tuesday, the 31st of May - Via Bonnie: If anyone steps up in the next 2 weeks, Jessica and Saumil will help train them - If no one steps up, meetings will start being cancelled - Merge team folks are the most likely candidates for leads - TIME COMMITMENT FOR TECH LEADS: Average 20 hrs per week, but if you're doing bare minimum, at least 10. - RESPONSIBILITIES: - IF BARE MINIMUM (10 hrs): Meetings, prepping for meetings (agendas, etc.), answering questions - https://docs.google.com/document/d/1bm7Kzft9GGwMgbWFDri46V__cQfUGjPjs-x5kOOvRSc/edit#heading=h.7h03id9hh8bj MISC NOTE - If you don't have your name in your github handle, please add it. - To do that: - Go to your profile - On the left hand side, you can edit your name (see screencap below) - Hit the "Save" button at the bottom of the left column ABOUT MEETINGS THIS UPCOMING WEEK - All leads meeting on Sunday the 5th - contact Saumil with your email address to receive an invite if you want to sit in MISC NOTE - ~Once you submit a pull request, you can delete your local branch right away. Even if you need to make changes later, you can always pull it back onto your local machine.~ -->This is incorrect. Edit/correction/what it should be: - For PR reviewers: Once you review a pull request, you can delete the local branch that you created to review the pull request right away. Even if you need to re-review the pr, you can always pull it back onto your local machine. - For PR creators: If you created/opened the pr, do not delete your branch. Once your pr is merged, then you can delete it. ON-CALL 1st/2nd REVIEW - If you need to change when you're on call for good first and second issues, please do that. This can be done here: https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0 - You can add yourself to the above spreadsheet if you've already completed your good second issue - If you have at least an hour any time during the day you're assigned, that works! DESIGN/PM/UI GET-TOGETHER - Per developer question to PM: - Languages: Javascript, Python, etc. - Tools: Zoom, Slack, Google Docs, Miro, Figma - Technologies: Everything else! React, Vue, other Frameworks, etc. - PM PROPOSED MAKING A WIKI PAGE OUT OF THIS TO DEFINE THE TERMS. - ANNOUNCEMENT FROM BONNIE - BONNIE is taking a 2-day a week gig working for GitHub; will be cutting back on Hack for LA so things might be slower TITLE SIZE/WEIGHTS Font weight origins for titles are currently quite muddled—it was very strongly advised we find a way to simplify this issue And, if needed, the screencap for adding your name to your GitHub profile, as referenced in the section "MISC NOTE":

Screencap for adding your name to your GitHub profile

[tamara-snyder]

Agenda for June 12, 2022

Facilitator: Tamara Snyder

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Arpita (arpitapandya) got PRs #3221 and #3185 merged
• Jason (JasonY188) got PR #2458 merged
• Matt (matt-arofin) got PR #3215 merged and finished the Pre-Work checklist
• Donald (DonaldBrower) got PR #3226 merged
• Alan (alan-zambrano) opened PR #3224 and reviewed one PR
• Wilny (Wny-Duong) reviewed three PRs
• Seth (scorbz9) opened PR #3225
• Akinola (Olanrewaju-Ak) opened PR #3235
• Hiram (riddle015) opened PR #3237 and finished the Pre-Work checklist
• Monica (mchavezm) finished the Pre-Work checklist
• Saumil(SAUMILDHANKAR) wrote four issues
• Adolf (answebdev) reviewed three PRs
• Utkarsh (usaboo) reviewed one PR
• Luke (luke-karis) reviewed one PR
• Kathryn (kathrynsilvaconway) reviewed two PRs

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Looking for someone to run the Tuesday developer meetings. This involves creating the meeting agenda from a template and facilitating the discussion on items from the agenda.
• [x] Tamara will be taking Fridays and Saturdays off. Message the merge team (Adolf, Devin, Jaret, Kathryn) with any questions.
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
  • [x] Next Sunday (June 19) demo will be: Pull Request Review. Does anyone want to volunteer to demo it?
• [x] Monthly Workflow Demo: Progress Report Creation

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[tamara-snyder]

Agenda for June 19, 2022

Facilitator:

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Kathryn (kathrynsilvaconway) merged a PR
• Trisha (trishajjsohnson) got a PR merged
• Olivia (oliviaywangn) opened a PR
• Adolf (answebdev) reviewed two PRs and merged one PR
• Troy (troywzhu) opened a PR
• Carlos (Carlos-A-P) reviewed a PR
• Devin (Sparky-code) reviewed and merged a PR
• Hiram (riddle015) got a PR merged
• Monica (mchavezm) got a PR merged
• Alan (alan-zambrano) reviewed a PR

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Tamara will be taking off Fridays and Saturdays. Please reach out to merge team members (Adolf, Devin, Jaret, Kathryn) or the general website team with any questions.
• [x] Looking for volunteers to run meetings. You can sign up to lead a meeting on this spreadsheet
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Please only work on one issue at a time. You can review other team members' PRs while you wait for your PR to be merged.
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [ ] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [ ] Check on any prs with "Changes requested"
  • [ ] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted"
  • [ ] Questions/In Review column
• [ ] Next Sun (June 26) demo will be: Issue creation, including labels and issue approval process. Does anyone want to volunteer to demo it?
• [ ] Monthly Workflow Demo: Reviewing pull requests

To bring up with PM/UI/UX

Notes from meeting

Click for notes

Dev team notes from 6/19: - Attendees: - Kathryn Silva Conway - Tamara Snyder - Eric - Murtaza Mogri - Adolf Schmuck - Utkarsh - We are looking for volunteers to help run team meetings on Sundays and Tuesday. Please Slack message Tamara if you are interested in being a meeting host.

[tamara-snyder]

Agenda for June 26, 2022

Facilitator: Tamara Snyder

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Devin (Sparky-code) reviewed and merged PRs #3285, #3288, and #3298, reviewed PR #3287, and wrote an issue
• Kathryn (kathrynsilvaconway) wrote three issues and merged PRs #3224, #3220, #3291, #2897, #3297, and #3287
• Adolf (answebdev) wrote an issue and reviewed PRs #3264, #3298, and #3297
• Sakari (Zak234) reviewed PRs #3262 and #3301 and opened PR #3299
• Lily (lilyarj) got PR #3287 merged, opened PR #3304, and finished the Pre-Work Checklist
• Beckett (BeckettOBrien) got PR #3288 merged, opened PR #3298, and reviewed PR #3224
• Tung (tunglinn) got PR #3291 merged
• Sarah (blulady) reviewed PRs #3264, #3262, #3261, #3288, #3291, and #3293
• Ethan (ethanstrominger) wrote an issue and completed the Pre-Work Checklist
• Clayton (clayton1111) opened PR #3297
• Utkarsh (usaboo) got PR #2962 merged
• Melodie (MCoding1) finished the Pre-Work Checklist
• Matt (matt-arofin) opened PR #3301
• Riya opened PR #3303

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: Aim to review two PRs for every one PR you make so that other developers can move onto their next issue sooner.
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Reminder: No team meetings on the 1st-7th of the month. This is a planning week for tech leads. You are encouraged to still meet on your own in the usual Zoom room.
• [x] Reminder: Only use the old Project Board. We are not using the New (Beta) Project Board yet
• [x] Sign up to lead a weekly team meeting here (no experience necessary!): https://docs.google.com/spreadsheets/d/1i3hz062eETOgiIdwFPPHyhShlQ6joUj0TSFLJFClnHw/edit#gid=1878346698

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted"
  • [x] Questions/In Review column
• [x] Monthly Workflow Demo: Issue creation, including labels and issue approval process, as demonstrated by Hiram
• [ ] Issue-writing session. We will all write issues that are part of an epic issue.
  • [ ] Epic issue: Creating issues to update alt texts on Events page
  • [ ] Issue tracking spreadsheet
  • [ ] Sample issue (click to edit and then copy and paste into your own blank template)

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[tamara-snyder]

Agenda for July 10, 2022

Facilitator: Tamara Snyder

• [x] Nominate a note-taker who will take notes during the meeting. Please note the names of members present in the meeting and other discussion topics of the meeting. After the meeting, Slack message Tamara with the notes.

Let's celebrate our contributions/wins since last team meeting

• Alan (alan-zambrano) opened PR 3322
• Beckett (BeckettOBrien) reviewed PR 3322
• Utkarsh (usaboo) reviewed PR 3225
• Riya (raswani2023) opened PR 3323
• Tung (tunglinn) opened PR 3324 and reviewed PR 3326
• Kathryn (kathrynsilvaconway) reviewed and merged PRs 3323 and 3087
• Lily (lilyarj) reviewed PRs 3322 and 3324 and opened PR 3327
• Wilny (Wny-Duong) merged PRs 3319, 3322, 3324, 3221, and 3225 and reviewed 3326 and 3225
• Sarah (blulady) reviewed PR 3321 and merged PR 3326
• Seth (scorbz9) finished the Pre-Work checklist
• Olivia (oliviaywangn) finished the Pre-Work checklist
• Clayton (clayton1111) got PR 3326 merged
• Ryan (RyanCahela) finished the Pre-Work checklist

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• [x] Tamara's last day is July 15

Meeting items

• [x] Developer Tasks: Spreadsheet with issues to write
• [x] Sign up to lead a team meeting
• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (July 17) demo will be: Pull Request review. Does anyone want to volunteer to demo it? @blulady
• [x] Monthly Workflow Demo: Progress report creation

To bring up with PM/UI/UX

Notes from meeting

Click for notes

**Meeting items** - Sakari Salminiitty - Tamara Snyder - Tung Lin - Lily - Riya Aswani - Tung Lin - Beckett O'Brian - Murtaza Morgri - Sarah Sanger - Hiram Riddle - Olanrewaju - Utkarsh Saboo Tamara goes over Developer task list: where developers can create issues https://docs.google.com/spreadsheets/d/183s91su1M8gLs3n7_fVA1RWrHwEZfpW-3-v_6jr4j5U/edit#gid=0 Tamara goes over signing up to lead a meeting https://docs.google.com/spreadsheets/d/1i3hz062eETOgiIdwFPPHyhShlQ6joUj0TSFLJFClnHw/edit#gid=282052975 We go through PR's share the link on how to do pull requests https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests We go through Project Board Tamara goes over updating progress on your issues We go back to Bonnie Who goes over Beckett's issue of Html in the project is there a way to separate strings without html Beckett went through and tried the different ways & none of them worked... people using the website won't be able to liquid inject on the website

[blulady]

Agenda for July 17, 2022

Facilitator: Sarah

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Sakari

Let's celebrate our contributions/wins since last team meeting

• Robenus (RobenusW) opened their first PR with Hack For LA 3362
• PR merged by Kathryn (Kathrynsilviaconway) 2554
• Angie (Angieintech) opened PR 3363 and 3371
• Lily(lilyarj) reviewed PR 3348, 3363, 3372, 3371, and opened PR 3368
• Riya(raswaniI2023) reviewed PR 3363
• Tung(tunglinn) reviewed PR 3363
• Wilny(Wilny-Duong) merged PR 3363, 3369, 3372, 3371
• Sean(seantokuzo) opend PR 3369
• Zak(Zak234) reviewed PR 3348, 3373 and 3375
• Sarah(blulady) reviewed and merged PR 3348
• Justin opened his first PR 3372
• Clayton(clayton1111) opened PR 2961
• Arpita(arpitapandya) opened PR 3374 and 3375
• Beckett(BeckettOBrien) reviewed PR 3372 and 3373

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: making a pull request. Does anyone want to volunteer to demo it? @tunglinn
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

- Contributions and Wins - No announcements - Tung assigned as reviewer for pr #3375 - Discussed branch name error for pr #3362 - Checked On-Call Reviewer spreadsheet, Lily assigned as a reviewer on Saturday - Addressed question from Sakari on Issue #2104. 3 out of 8 changes in the issue did not work properly. Decided to update the css for the buttons to correct errors. Sakari received approximate location of said css code from Kathryn. - Demo of How to Review Pull Requests - Lily had an issue with pulling Beckett’s pull request for review. There was also an issue with uncommitted changes from Beckett’s repository showing up in Lily’s along with changes from Beckett’s branch showing up in Lily’s gh-pages branch. Sakari pulled Beckett’s pr and had similar issues along with finding that deleting the changes from one branch deleted them from all branches. Issue was solved by having Beckett update his fork of the repo. -Reviewed Tung’s decision recored. Was approved -Discussion with Research/Design: -Informed research/design of git issues. Was decided that if someone experiences the error, they should film it and post it in slack and in GitHub discussion “PRs problems with staged and uncommitted changed visible across branches” along with putting it in https://drive.google.com/drive/folders/1HbA3zKVKVqGxzGD-dsKd29s7sId1o7Zi?usp=sharing - New features. Suggested by design: - Search function - Adding filters to pages outside of the home page - Discussed creating new issues for toolkitresources.yml. Decided to hold until design decides how the search will work. - Discussed with Bonnie issue #3361 which was approved - Satya joined meeting and was asked about proper usage of git especially commits. Related to earlier problem with reviewing pull request and uncommitted changes

[blulady]

Agenda for July 23, 2022

Facilitator: Sarah

• [ ] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Zakari

Let's celebrate our contributions/wins since last team meeting

• Beckett(BeckettOBrien) reviewd #3394, #3385, #3342
• Wilny (Wny-Doung) reviewed #3395, #3407 and merged #3407, #3393
• Justin(jdingeman) opened PR #3407
• Sakari(Zak234) reviewed #3407, #3421 and opened #3422
• Kathryn(kathrynsilvaconway) merged #3260
• Sarah(blulady) reviewed #3394 and merged #3394, #3368
• Lily(lilyarg) reviewed #3393
• Asher(AsherEngelberg) reviewed #3393, #3419, #3419
• Angie(angieintech) opened #3419
• Neev(neevliberman) opened #3421,

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: How to Review Pull Request. Does anyone want to volunteer to demo it? Utkarsh
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[kathrynsilvaconway]

Agenda for July 31, 2022

Facilitator: Kathryn

• [ ] Sign in to vrms.io
• [ ] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Danny (d-perez-8) closed his pre-work checklist #3388 and opened PR #3441
• riya (raswani) opened PR #3432 and had her per-work closed out
• Sakari (Zak234) created isuues #3433 and #3437 and merged PR #3430
• Eric (ericvennemeyer) closed his prework checklist #3048 and opened PR #3435
• Justin (jdingeman) opened PR #3436
• Beckett's Perwork was closed #3267
• Clayton closed his per-work checklist #3266
• Matt (Mattre7) closed his pre-work checklist #3243 opened PRs #3439, #3444 and #3442
• Ava (aveline-art) created issue #3440
• Wilny (Wny-Duong) merged PRs #3435, #3442, #3436, and #3439
• Angela (angieintech) opened PR #3443

Announcements & Reminders

• [ ] There are no meetings this week, except for lead. We don't meet the 1st through 7th every month.
• [ ] Reminder: Please only work on one issue at a time. Your issue is not completed until the PR is merged. Wait for the merge before you pick up your next issue.
  • [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
  • [x] Will open the floor for any announcements

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] label:"Status: Help Wanted" (link)
• [x] Next Sun () demo will be: How to Review Pull Request. Does anyone want to volunteer to demo it? Utkarsh
• [x] Today's Demo: How to test a Github action in your local repo.

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[blulady]

Agenda for August 14 2022

Facilitator:

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (August 21) demo will be: how to make a pull request. Does anyone want to volunteer to demo it? Utkarsh
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

attendees: Kathryn Silva Conway Eric Vennemeyer Sakari Salmiitty Danny Perez Arpita Pandya Neev Lieberman Olenrewaju Utkarsh Saboo Lily Ruo John Barrett Matthew Toledo Tung Lin -Before you review a pull request, make sure your gh-pages branch is up to date before you create a new branch. -Sarah reminded us of the correct procedure for reviewing pull request. - we reverted an unwanted commit on a PR as discussed best practices for doing this. - A/B testing of the new filter menu design with Bonnie.

[blulady]

Agenda for August 08 2022

Facilitator: Sarah

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• Sakari merged #3470 and reviewed PR #3470
• Justin reviewed #3468
• Arpita reviewed #3468, #3475
• Wilny merged PR #3468
• Sarah reviewed #3384 and #3436 and merged #3475 and #3436
• Matthew created his first PR #3464
• John reviewed #3475
• Lily reviewed #3475
• Luke reviewed #3471

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: How to Make A PR. Does anyone want to volunteer to demo it? Utkarsh
• [x] Monthly Workflow Demo: Sakari Github Actions

To bring up with PM/UI/UX

Notes from meeting

Click for notes

-Wins/Contributions -No announcements -No new reviewers were assigned for pull requests -Sakari gave demo for how to test Github Actions -Utkarsh’s demo was postponed until next Sunday

[blulady]

Agenda for August 28, 2022

Facilitator: @blulady

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. @Zak234

Let's celebrate our contributions/wins since last team meeting

• @Zak234 reviewed #3482 and merged #3482
• @ericvennemeyer opened PR #3483, #3484, #3485 (ALL PERTINENT TO THE FIRST PR) and reviewed #3476
• @blulady opened PR #3485, reviewed #3452
• @jdingeman closed #3365, his pre-work checklist
• @kathrynsilvaconway reviewed #3452, #3483 merged #3452 and opened #3491, #3495
• @neevliberman opened PR #3490
• @d-perez-8 reviewed #3490

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: how to review a pull request. Does anyone want to volunteer to demo it? Arpita
• [ ] Monthly Workflow Demo:

To bring up with PM/UI/UX

• @jdingeman he might need Bonnie to do something so he can link the data in #2276 https://github.com/hackforla/website/issues/2776 https://datastudio.google.com/reporting/16J9XI19pQejSDNFvjl_V3ZezJ502rM_a/page/qx6RB
• @ericvennemeyer #3488 updating docker image locally

  Notes from meeting

  Click for notes

[blulady]

Agenda for September, 11 2022

Facilitator:

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [ ] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
  • [x] discuss updating the new project board
• [ ] Next Sun (Mmm DD) demo will be: ____. Does anyone want to volunteer to demo it?
• [ ] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[blulady]

Agenda for September 11, 2022

Facilitator: Arpita

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• @arpitapandya merged PR #3517, #3519 and reviewed #3518, #3519, #3431
• @giroz reviewed PR #3515, #3518, #3521
• @plang-psm opened RP #3519 , #3521
• @neevliberman reviewed #3519
• @lilyarj reviewed #3521
• @blulady reviewed #3521 and merged #3521
• @ericvennemeyer reviewed #3476
• @kathrynsilvaconway reviewed #3431 and merged #3431

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (September 18) demo will be: How to create a Pull Request. Does anyone want to volunteer to demo it ? - Philip
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

• @ericvennemeyer #3488 updating docker image locally
• project board
• https://github.com/hackforla/website/pull/3414 we have a git dependabot that creates pr's is there a reason there needs to be an issue too?

Notes from meeting

Click for notes

- Not going to merge Mattre's pr without cleaning up the code, Sarah needs to complete reveiw today - we should continue to work on the old board - lots of new issues ready for us to work on - erik is working on docker image - talk to Ava about beckit - went through pre-work development & have an issue that summarizes what's going on with people falling through the cracks - github action that goes to everyone as soon as they self assign & says developer want's it to say "team member" - will see - seeing things newissues approval column, seeing a lot of ready for dev lead, should be a note on the bottom that says what should be done (dev lead make an issue to impliment it) then write dev has taken the handoff (comment on the bottom of the issue) and the new issue is done (if there isn't a comment at the bottom - comment @ bonnie at the bottom of the not issue & add a ready for milestone) - onboarding tonight bonnie will add them to the calendar invite & start the pre-work checklist - tuesday & thursday night eliminate folks with x's send them a message saying if we removed them in error to go back the previous week's calendar invite and reinvite themselves

[github-actions[bot]]

Hi @Zak234, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[github-actions[bot]]

Hi @Zak234, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[github-actions[bot]]

Hi @Zak234, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[github-actions[bot]]

Hi @Zak234, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[arpitapandya]

Agenda for September 18, 2022

Facilitator: Arpita

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• @AzaniaBG opened PR #3423 and reviewed PR #3557
• @jdingeman reviewed #3551
• @Unity7 opened PR #3557 and PR #3561, good job don't forget to review other pull requests
• @kathrynsilvaconway reviewed #3556 and merged PR #3556
• @plang-psm opened PR #3558 and reviewed PR #3557
• @giroz reviewed PR #3551, #3561
• @palomasoltys opened PR #3559
• @mariareeves opened PR #3560
• @arpitapandya reviewed PR #3557, #3558 and merged #3557
• @neevliberman reviewed PR #3561 and #3558
• @lilyarj reviewed PR #3560

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your PR is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any PRs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (September 25) demo will be on How to create a Pull Request. Does anyone want to volunteer to demo it? Lily
• [x] Monthly Workflow Demo: Sarah for GitHub Actions workflow on September 25

To bring up with PM/UI/UX

Notes from meeting

Click for notes

- Google drive has changed so non users can make things in the shared drives - Asking for owners of forms to move to the shared drive along with the spreadsheets but they own the spreadsheet, they are the only one who can have move their spreadsheet - We have a new google drive (google drive migrations) - Bonnie found a paired linter/vs code extension to work with

[arpitapandya]

Agenda for September 25, 2022

Facilitator: Arpita

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• @carolemlago opened PR #3567
• @AzaniaBG opened PR #3574
• @arpitapandya opened PR #3575 , merged PR #3566 , #3561 , #3573 , #3564 , #3574 , #3576 , #3577 , #3578
• @kathrynsilvaconway merged PR #3567 , #3568
• @michaelmagen opened PR #3576
• @GRISONRF opened PR #3577
• @Carlos-A-P opened PR #3578
• @Unity7 opened PR #3579
• @aricforrest opened PR #3580 Announcements & Reminders
  • [x] Will open the floor for any announcements
  • [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
  • [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (October 9) demo will be: How to create a Pull Request. Does anyone want to volunteer to demo it? Justin
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

- No new announcements - Discussed Justin’s issue with Liquid/Jekyll not displaying Markdown files or accessing the files outside of `site.data` - Sarah’s GHA workflow demonstration - Worked on Matt’s issue with git - Sijia from Design requested feedback on the mobile view

[7kram]

Please add this to your agenda:

https://github.com/hackforla/website/issues/2569#issuecomment-1261204054

[arpitapandya]

Agenda for October 9, 2022

Facilitator: Arpita

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• @jdingeman opened PR #3597
• @blulady opened new issue #3598
• @michaelmagen opened PR #3599
• @Suman2795 opened PR #3600
• @arpitapandya merged PR #3599

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: The issues in the prioritized backlog column with the label time-sensitive are a high priority to work on. When picking up an issue, consider working on a time-sensitive issue first.
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (October 16) demo will be: How to create a Pull Request. Does anyone want to volunteer to demo it? Justin
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

- Announcements for devs to work on `time-sensitive` issues as a priority from `prioritized-backlog` - Seek assistance regarding WCAG speech bubbles that appears when hovering icons on the wins page - Arpita shall meet the previous lead. - On Justin's question - refer to the message next to Figma design - We are taking December month off, No meetings, but devs are welcome to continue contributing and reviewing. Announcements will be made as we come close to mid-November. - Discovered incorrect logo size for `access-the-data` project card on hackforla website after the merge - Bonnie updated the size of logo, Arpita shall fix it and open a new PR.

[arpitapandya]

Agenda for October 16, 2022

Facilitator: Arpita

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• @MattPereira opened PR #3615 #3621
• @DmitriiTsy opened PR #3616 #3622
• @gstemmann opened PR #3617 #3623
• @jyaymie opened PR #3618 #3624
• @kathrynsilvaconway merged PR #3618
• @blulady merged PR #3616 #3615
• @jdingeman created an issue #3619 ,merged PR #3621 #3622 #3624
• @esantiano opened PR #3620
• @t-will-gillis opened PR #3625
• @Suman2795 opened PR #3628

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: The issues in the prioritized backlog column with the label time-sensitive are a high priority to work on. When picking up an issue, consider working on a time-sensitive issue first.
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [ ] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (October 23) demo will be: How to review a Pull Request. Does anyone want to volunteer to demo it? Azania
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

- Attendees: - Azania Baker Garcia - prep for interview - Eric Santiano - will review PRs on Saturdays - George Stemman - will review PRs on Sunday - Sarah S - Arpita Pandya - Justin Dingeman - Matthew Toledo - Did not receive invite to Sundays meeting - Jamie Park - gone from Oct 27th - 31st, will review PRs on Tuesday - Johnny Wu - Dmitrii TS - Leon Dawson - Bishr - Akram Nour - How to ask for help on issues: help wanted label. Comment any blockers, share link - Pull Request Demo - Add screen shots for small, medium, large issues - Reviewing PR’s based on Figma Design - How closely a change is supposed to model Figma design? Up to our discretion, ask Bonnie or Design. - WCAG Issues - Donate Page Problems - Alt Text - Reopened PR - Changes not shown on live website, changes made on pages folder not donate card - Will make a new issue - Sticky Side Bar/Nav Accessibility - Navigable by keyboard alone for key board users - Visible focus to tell which link they’re on - How do Sunday meetings work? - Meet Sunday start with Agenda - Blockers - Questions from Bonnie or other teams? - Github Wiki isn’t allowing merges - Tung Issue - Discussion moved to Monday

[blulady]

Agenda for October 23, 2022

Facilitator:

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. Eric

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.
• announcements: Danny, Jamie (until Nov1) and Bay (until Nov 5) going on Vacation

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [ ] Next Sun (Mmm DD) demo will be: Eric S. Does anyone want to volunteer to demo it?
• [ ] Monthly Workflow Demo:

To bring up with PM/UI/UX

• Jamie's issue about how to work on figma https://github.com/hackforla/website/issues/2392 left justify, mores space between immage of 3 circles and next header(h3) is bigger in reality needs to go back to design for a clean up- figma might make it grey - Sijiia will update create 3 different cards this issue goes back to the ice box

• Azania Baker-Garcia new figma design from design in this issue https://github.com/hackforla/website/issues/2173 adding an underline when the mouse hovers over the link so people knows its a link or make the size bigger decided to make the font bigger and go from there, going to put a red box around the figma image that solves this issue

• Aric access to the Elzabeth's Honest Account https://github.com/hackforla/website/issues/3417

• Justin needs design approval https://github.com/hackforla/website/issues/2027#issuecomment-1280008003 looks good just need to check that the card size changes looks ok across all projects

• Matt Review with product/front end lead https://github.com/hackforla/website/issues/2292 get rid of team name use the yes/no question if the answer is no then no content will be expected

Notes from meeting

Click for notes

All hands Meeting Hack for LA 10/23/22 Danny Perez - on vacation 3 weeks Bay Bui - on vacation nov 5th Jamie Park - out Thursday to Halloween Matt Pereira Dmitrii TS Justin Dingeman Matt Bozin Azania Baker-Garcia Eric Santiano Peter Yoo Matthew Toledo Aric - git hub bot Joshua Juarez Arpita Pandya Sarah S George Stemman How to Review a Pull Request Demo with Azania Issues for Bonnie: Jamie - CSS Changes, Figma visual changes. Some changes not noted. Azania - Accessible design page not key board navigable. Add visual cue Justin - Project resource cards, spacing issue Matt - GitHub form Aric - Wins page, API Token for bot account is not valid Peter - no good first issues Volunteers for medium issue PR - George Eric - Anything to do after pull requests or issues? Eric to Demo creating a pull request.

[arpitapandya]

Agenda for October 30, 2022

Facilitator: Arpita

• [x] Sign in to vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

• @ldaws003 opened PR #3676
• @str-xjua24 opened PR #3675
• @esantiano opened PR #3674
• @PeterSYoo opened PR #3673
• @MattPereira opened PR #3672

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: The issues in the prioritized backlog column with the label time-sensitive are a high priority to work on. When picking up an issue, consider working on a time-sensitive issue first.
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: ____. Does anyone want to volunteer to demo it?
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[jdingeman]

Agenda for November 13, 2022

Facilitator:

• [x] Sign into vrms.io
• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. -- Roslyn

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun November 20, 2022 demo will be: Issue creation, including labels and issue approval process. Does anyone want to volunteer to demo it? -Sarah
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

• [ ] Discussion about icebox for Sunday meeting
• [x] #3437
  • [x] What is intended outcome for this issue? Should it have the links or not have the links? Figma design differs from images on issue.
• [x] #3672
  • [x] Need approval from @ExperimentsInHonesty
• [x] #2174
• [ ] #2634
  • [ ] Tung needs authorization token
• [ ] #3027

Notes from meeting

Click for notes

Attendees - Justin - facilitator - George Stemman - Arpita Pandya - Jessica Cheng - Matt Pereira - Derek Lui - Sarah S - Jamie Park - Peter Yoo - Angelene Manalo - Danny Do - Matthew Toledo - Johnny Wu - Ernia Pelayo - Roslyn Wythe

[blulady]

Agenda for November 20, 2022

Facilitator:

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. George

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: Progress Report creation. Does anyone want to volunteer to demo it? Matt
• [x] Monthly Workflow Demo:
• [ ] discussion of a docker tutorial

To bring up with PM/UI/UX

• [x] #3109
• [x] #3719 names of the partners (e.g., Metro versus Los Angeles Metro)
• [x] add Matt & Philip to Google Data Studio: Hack for LA Organizational Dashboard
• [x] calendar for december
• [x] letter of recommendation

Notes from meeting

Click for notes

attendance: sarah s george stemmann roslyn wythe satenik matthew toledo matt p jessica cheng arpita pandaya eric santiano sarah reminds everyone that december has been taken off the calendar for meetings and that has been confirmed with bonnie in real time she saw they are all still on december and there may be office hours available for the month of dec. ---> this will be confirmed with bonnie eric santayo most likely has a job offer as a full stack tech company sarah reminds everyone to consder working on back end issues after getting a pr merged sarah reminds someone we need to fix the bug in the vrms data not displaying a PR developer spreadsheet for PRs needs to be filled for Thursday we are skipping questions on issues for those that are not in attendance today george asked about to add to the list of demos. matt asked for issue creation and george asked for docker tutorial (this may be brought up in future meetings) sarah added a point to discuss at the end of the meeting go over this ^^^ matt p will be taking the demo to create a progress report sarah posts link to teach everyone how to create an issue and then walks the team through how to do it jessica and sarah cleared up that a dependency on an issue is actually a release to the issue that it's dependent on and the issue goes into the ice box we go over eric's issue (design system audit color swap color swap #3730) -- matt p discusses a previous comment that adding a span tag can help resolve the issue we check to see if there is a line of code that needs to be deleted and the consensus is that it should be deleted from the .md file we go to meet bonnie in the main room and we go over any issues that may need to be brought up with research and design team. sarah introduces #3719 with some of the name and image ---> bonnie and sarah decide the participants in the issue were not present today so it is tougher to be resolved and skip the issue discussion bonnie officially gave confirmation that we have absolutely no meetings for december sarah confirmed matt p and () are officially onboarded to the merge team ---> sarah was granted access by bonnie to onboard members to the hfla dev team bonnie removed older dev leads permissions sarah asked who should be closing pre-work issues and bonnie confirmed it will soon be the responsibility of the dev team to close those issues a questions was raised about a team member that needed a letter of recommendation and bonnie clarified this with Sarah and how to do this bonnie asked the dev team to make sure they are all onboarded and satenik was warned about being onboarded before the Christmas break bonnie shared her screen and made sure that satenik needed to be added to the drive #3109 ---> bonnie made sure to tell devs to extract information from an old issue instead of adding a link to reference the old issue jessica asked what's the difference between a 3rd issue and a small issue ---> bonnie's answer was that third issue is a fun issue to help with boredom and motivation.. bonnie suggested we may not need the words "third issue" and we may just change to label to "fun bonnie found a bug with the github wiki search and then deduced it may just be the particular wiki page bonnie in real time took out the "third-issue" label from the one issue that contained it sarah asked where do you find the page to "read and interpret labels" ---> bonnie helped her find the link in the wiki there was a question asked about nov 29th and then reseach changed it

[blulady]

Agenda for November 27, 2022

Facilitator: Justin

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well. - Phillip

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: ____. Does anyone want to volunteer to demo it?
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

• [x] Suman's letter of recommendation (gave her the link Bonnie gave me, does she need to make a separate issue for it?)
  • [ ] She should make a dedicated issue for LOR so Bonnie can view the resources
• [ ] GitHub Actions: 2 weeks inactive label bug #2634 https://github.com/settings/tokens?type=beta and Tung will need a GitHub Token with read-only access to Content, Issues, Metadata, PRs
• [ ] finding a zoom room in the schedule for monday's new meeting
  • [ ] Since there are no more Onboardings for the rest of the year, Jessica temporarily scheduled the Dev/PM meeting for Zoom 4 on Monday, 11/28/2022.

Notes from meeting

Click for notes

Sunday Meeting 11/27/22 Attendance - Justin Dingeman - Presenting - Matt Pereira - Phillip Sanchez - Notes - George Stemmann - Arpita Pandya - Danny Do - Will Gillis - Jessica Cheng - Yoojin Chang - This Sunday and Tuesday are last meetings until after the holidays - Demo next meeting when we have more attendees - No assigning demo, we will assign when we return - Dev to research - No questions - Bonnie Project board and questions column - Update citizen engagement pages H4 titles to match Figma design #2464 - Kathryn not here but why was it moved to icebox - Moving back to new issue approval - How do we want to handle issues that come up while working on an issue - Dev should open a ticket when they come across another issue - Possible issue template? - Emergent Requirement - Problem - Issue you discovered this emergent requirement in: - Issue # and link - Date Discovered - Did you do something temporary? - [ ] Yes - [ ] No - Who was involved? - What happens if this is not addressed? - Explanation of possible issues - Resources - Recommended Action Items - [] Make a new issue - [] Discuss with team - [] Let a Team Lead know - Potential solutions [draft] - Slack reminder in channel - Automated creation of new issue on X day of month - Add to agenda - Label: - Ready for dev lead - Size - Feature - Role - Time sensitive - Project board: - new issue approval - Justin will talk to Aric and Sarah regarding: - https://github.com/hackforla/website/issues/3417 - Need to remove or remake the ‘How to review a PR’ project slide. - Remove no-labels-template.md file #2898 - Make a new issue to document the change in the wiki - HfLA-GitHubActions in the wiki – document our GHA changes - Apply new gradient overlay for project pages #2600 - Reopen and apply new image from archived. - Make sure we’re reviewing visual changes closely.

[jdingeman]

Agenda for January 8, 2023

Facilitator: Justin

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: Pull Request Review. Does anyone want to volunteer to demo it? - @arpitapandya
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

Notes from meeting

Click for notes

[jdingeman]

Agenda for January 15, 2023

Facilitator:

• [ ] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [ ] Will open the floor for any announcements
• [ ] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [ ] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [ ] Pull requests (PRs)
  • [ ] All developers are expected to review pull requests
  • [ ] Go over open PRs to assign reviewers
  • [ ] Helpful link: How to Review Pull Requests
  • [ ] Allow some time in the meeting for all reviewers to add ETA and availability
  • [ ] Check on any prs with "Changes requested"
  • [ ] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted" (link)
  • [ ] Questions/In Review column
• [ ] Next Sun (Mmm DD) demo will be: ____. Does anyone want to volunteer to demo it?
• [ ] Monthly Workflow Demo:

To bring up with PM/UI/UX

• 2675

  • Test file does fix the question marks in place of apostrophes
  • Unable to test on production code as the Google Apps Script cannot connect to Github (see execution log below)
  • I believe this might be due to the authorization token being expired, but I am not entirely sure. I think the file is owned by Matthew Cacho
  • Google Apps Script Execution Log

    

Notes from meeting

Click for notes

[MattPereira]

Agenda for Jan 22, 2023

Facilitator:

• [ ] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [ ] Will open the floor for any announcements
• [ ] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [ ] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [ ] Pull requests (PRs)
  • [ ] All developers are expected to review pull requests
  • [ ] Go over open PRs to assign reviewers
  • [ ] Helpful link: How to Review Pull Requests
  • [ ] Allow some time in the meeting for all reviewers to add ETA and availability
  • [ ] Check on any prs with "Changes requested"
  • [ ] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [ ] Go through Project Board for any questions and items that need to be discussed
  • [ ] Dev team column
  • [ ] In-progress column
  • [ ] label:"Status: Help Wanted" (link)
  • [ ] Questions/In Review column
• [ ] Next Sun (Mmm DD) demo will be: ____. Does anyone want to volunteer to demo it?
• [ ] Monthly Workflow Demo:

To bring up with PM/UI/UX

• MP: Confusion about getting this issue Ready for Milestone https://github.com/hackforla/website/issues/3118
• JD: #3209 -- does this simply need to be reverted, i.e. the dev will just add the alt-hero back to what it originally was? Or does that text need to be added back as some other attribute (e.g. credit:)?

Notes from meeting

Click for notes

[MattPereira]

Agenda for January 29, 2023

Facilitator:

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (Mmm DD) demo will be: ____. Does anyone want to volunteer to demo it?
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

• Bitian needs to be added to the Sunday meeting. Is it possible to allow merge team to add new members to google calendar sunday meetings?
• Consistency of labels concern brought up by Bitian working on #3109
  • Capitalization and : inconsistency among missing labels group
• Need "host key" for zoom in order to create breakout rooms at Tuesday Night Meeting

Notes from meeting

Click for notes

[jdingeman]

Agenda for February 5, 2023

Facilitator: Justin

• [x] Nominate a note-taker who will take notes during the meeting. After the meeting, Slack message the Technical Leads with the notes. Please note the names of members present in the meeting as well.

Let's celebrate our contributions/wins since last team meeting

Announcements & Reminders

• [x] Will open the floor for any announcements
• [x] Reminder: When you are done with your current issue and your pr is merged, consider working on a back end issue next. (Remember to filter by back end role and complexity - first, second, small, medium, large).
• [x] Reminder: Office hours on Thu from 7-8pm Pacific. The room will be open for any questions / help, or if you want to see what is being worked upon.

Meeting items

• [x] Pull requests (PRs)
  • [x] All developers are expected to review pull requests
  • [x] Go over open PRs to assign reviewers
  • [x] Helpful link: How to Review Pull Requests
  • [x] Allow some time in the meeting for all reviewers to add ETA and availability
  • [x] Check on any prs with "Changes requested"
  • [x] Assign junior developers to On-call PR Review for 1st and 2nd Issue spreadsheets
• [x] Go through Project Board for any questions and items that need to be discussed
  • [x] Dev team column
  • [x] In-progress column
  • [x] label:"Status: Help Wanted" (link)
  • [x] Questions/In Review column
• [x] Next Sun (February 12, 2023) demo will be: How to Make a Pull Request. Does anyone want to volunteer to demo it? - Roslyn
• [x] Monthly Workflow Demo:

To bring up with PM/UI/UX

• [ ] #2901

Notes from meeting

Click for notes

[MattPereira]

Agenda for Febuary 12, 2023

Facilitator: Matt Pereira

Announcements & Reminders

• [x] Paste to chat
  • [x] https://vrms.io/
  • [x] https://github.com/hackforla/website/wiki/Meetings-and-Agendas
• [x] Dev team meeting on Tuesdays from 7-8pm PST
• [x] Office hours on Thursdays from 7-8pm PST ( All Q/A time no dedicated PR or Project Board walk-through )
• [x] No meetings for the first 7 days of every month
• [x] Open the floor for celebrating any announcements

Meeting items

Pull Requests

• [x] All developers are expected to review pull requests
• [x] Encourage team members to review open PRs
  • [x] https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
  • [x] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
• [x] Check on any PRs with Changes requested
  • [x] Explain how to re-request a review after you make the requested changes

Project Board

• [x] Reminder to only assign yourself to issues from the Prioritized backlog column
• [x] Check the In Progress column for issues with 2 weeks inactive label
• [x] Check the In Progress column for issues with Status: Help Wanted label
• [x] Check the Questions/In Review column

To bring up with UI/UX

To bring up with PM

• Trigger happy 2 weeks inactive label example: #3875
• Consider moving Prioritized backlog column farther left on project board to prevent new devs from seeing it

[MattPereira]

Agenda for Feb 19, 2023

Facilitator: Justin

Announcements & Reminders

• [x] Paste to chat
  • [x] https://vrms.io/
  • [x] https://github.com/hackforla/website/wiki/Meetings-and-Agendas
• [x] Dev team meeting on Tuesdays from 7-8pm PST
• [x] Office hours on Thursdays from 7-8pm PST ( All Q/A time no dedicated PR or Project Board walk-through )
• [x] No meetings for the first 7 days of every month
• [x] Open the floor for celebrating any announcements

Meeting items

Pull Requests

• [x] All developers are expected to review pull requests
• [x] Encourage team members to review open PRs
  • [x] https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
  • [x] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
• [x] Check on any PRs with Changes requested
  • [x] Explain how to re-request a review after you make the requested changes

Project Board

• [x] Reminder to only assign yourself to issues from the Prioritized backlog column
• [x] Check the In Progress column for issues with 2 weeks inactive label
• [x] Check the In Progress column for issues with Status: Help Wanted label
• [x] Check the Questions/In Review column

To bring up with UI/UX

• [x] Are there any new design/UI/UX on the team?

To bring up with PM

• [x] Just move to closed? #3361

[MattPereira]

Agenda for February 26, 2023

Facilitator: Matt

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Announcements & Reminders

• [x] https://vrms.io/
• [x] Devs only team meeting on Tuesdays from 7-8pm PST
• [x] Office hours on Thursdays from 7-8pm PST
• [x] No meetings for the first 7 days of every month
• [x] Open the floor for celebrating any announcements

Meeting items

Pull Requests

• [x] All developers are expected to review pull requests
• [x] Encourage team members to review open PRs
  • [x] https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
  • [x] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
• [x] Check on any PRs with Changes requested
  • [x] Explain how to re-request a review after you make the requested changes

Project Board

• [x] Explain the project board
• [x] Check the In Progress column for issues with Status: Help Wanted label
• [x] Check the Questions/In Review column

HFLA Journey Advice

• [x] https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team

To bring up with UI/UX

To bring up with PM

[jdingeman]

Agenda for March 12, 2023

Facilitator: Justin Dingeman

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Announcements & Reminders

• [x] https://vrms.io/
• [x] Devs only team meeting on Tuesdays from 7-8pm PST
• [x] Office hours on Thursdays from 7-8pm PST
• [x] No meetings for the first 7 days of every month
• [x] Open the floor for celebrating any announcements

Meeting items

Pull Requests

• [x] All developers are expected to review pull requests
• [x] Encourage team members to review open PRs
  • [x] https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
  • [x] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
• [x] Check on any PRs with Changes requested
  • [x] Explain how to re-request a review after you make the requested changes

Project Board

• [x] Explain the project board and the flow of issues between columns
• [x] Check the In Progress column for issues with Status: Help Wanted label
• [x] Check the Questions/In Review column

HFLA Journey Advice

• [x] https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team

To bring up with UI/UX

To bring up with PM

• [ ] ### Agenda for monthAsText dd, yyyy Facilitator: TBD

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Announcements & Reminders

• [ ] https://vrms.io/
• [ ] Devs only team meeting on Tuesdays from 7-8pm PST
• [ ] Office hours on Thursdays from 7-8pm PST
• [ ] No meetings for the first 7 days of every month
• [ ] Open the floor for celebrating any announcements

Meeting items

Pull Requests

• [ ] All developers are expected to review pull requests
• [ ] Encourage team members to review open PRs
  • [ ] https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
  • [ ] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
• [ ] Check on any PRs with Changes requested
  • [ ] Explain how to re-request a review after you make the requested changes

Project Board

• [ ] Explain the project board and the flow of issues between columns
• [ ] Check the In Progress column for issues with Status: Help Wanted label
• [ ] Check the Questions/In Review column

HFLA Journey Advice

• [ ] https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team

To bring up with UI/UX

To bring up with PM

• [ ] https://github.com/hackforla/website/issues/3722
• [x] https://github.com/hackforla/website/issues/3881
• [ ] https://github.com/hackforla/website/issues/4101
• [ ] https://github.com/hackforla/website/issues/3334
  • [ ] Probably not a solveable issue due to GitHub API/race condition
  • [ ] Wording for issue is not clear
  • [ ] What to do with Emergent Request
• [x] https://github.com/hackforla/website/issues/3985
• [x] https://github.com/hackforla/website/issues/3805
• [x] https://github.com/hackforla/website/pull/4110
• [x] https://github.com/hackforla/website/issues/3635

[jdingeman]

Agenda for March 19, 2023

Facilitator: Justin Dingeman

Welcome to the Sunday All Website Teams meeting. Thank you for joining us!

Announcements & Reminders

• [x] https://vrms.io/
• [x] Devs only team meeting on Tuesdays from 7-8pm PST
• [x] Office hours on Thursdays from 7-8pm PST
• [x] No meetings for the first 7 days of every month
• [x] Open the floor for celebrating any announcements

Meeting items

Pull Requests

• [x] All developers are expected to review pull requests
• [x] Encourage team members to review open PRs
  • [x] https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
  • [x] Remind PR reviewers to add their ETA and availability after requesting themselves for a review
• [x] Check on any PRs with Changes requested
  • [x] Explain how to re-request a review after you make the requested changes

Project Board

• [x] Explain the project board and the flow of issues between columns
• [x] Check the In Progress column for issues with Status: Help Wanted label
• [x] Check the Questions/In Review column

HFLA Journey Advice

• [x] https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA--Dev-Team

To bring up with UI/UX

To bring up with PM

• [x] https://github.com/hackforla/website/wiki/Meetings-and-Agendas
  • [x] VRMS also needs to be updated, check tomorrow if there is anything updated
• [x] https://github.com/hackforla/website/issues/4033
  • [ ] Signed off by Bonnie
• [ ] https://github.com/hackforla/website/issues/2651
  • [ ] Dependency for https://github.com/hackforla/website/issues/1442 ?
  • [ ] Work with @bootcamp-brian to clarify current issue
  • [ ] Local installation requires a roll out plan to ensure devs download the extension
  • [ ] The VS Code Spell checker should be implemented first
  • [ ] Brian should document in DR's Solutions Adopted with notes:
    • [ ] Requires roll out plan
    • [ ] Dependency is spell checker
    • [ ] Is dependency for the GitHub implementation
    • [ ] New issue to be made for implementation
    • [ ] Reach out to @jdingeman to work on issue completion
• [x] Ask about Wiki to MKDocs migration