search

hackforla / website

Hack for LA's website
https://www.hackforla.org
GNU General Public License v2.0
294 stars 723 forks source link

HfLA: DEV TEAM Meeting Agenda Sunday ๐Ÿงฃ #2027

Open Aveline-art opened 2 years ago

Aveline-art commented 2 years ago

Overview

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

Weekly Action Items

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
- [ ] 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.
Aveline-art commented 2 years ago

Agenda for August 01, 2021

Aveline-art commented 2 years ago

Post-meeting notes, August 01, 2021

Click for notes
- Need to write JavaScript in js folders and not in HTML files - Created elements folder - Review PR with a demonstration - Discussed adding instructions when editing PR files on GitHub vs local - Assigned reviewers on open PR
Aveline-art commented 2 years ago

Agenda for August 08, 2021

Aveline-art commented 2 years ago

Post-meeting notes, August 08, 2021

Click for notes Meeting began at 10:56 AM. 1. Announcements - Automation scripts for onboarding. It involves Google App Scripts (JavaScript). - Please reach out to Alex if you would like to learn more. - Onboarded new members, Saumil and Megan! - Announced the Milestone Category! 2. Reviewed Dev Meeting Column - #2005 - What are the next steps to this? How do we want to standardize it? - Result: Yes to cleaning the code and standardizing it. - #1928 - Waiting for requested review. - Result: Matthew Cacho and Adam will review it. - #1993 - Product suggested that the issue be brought to development; Designers would like feedback from development. - Note: There are new components that we donโ€™t have that we need to make an issue. - Result: Sent a comment to Sihem and Bonnie that the dev team said it looks good and would like to move it to the developer meeting. 3. Architecture - The codes are visible on our website. What are our next steps? (Links from discussion purposely not disclosed.) - Note: Akib once said there's a setting where we could turn it off (Configuration side) - Result: Make a new issue: Size: Large, Assigned to Matthew Cacho 4. Progress Reports - #1979 - Update: Sihem added a comment to the issue. - Feedback on Github actions: - It works. Very nice that the bot notifies us when we need to update the issue. Also nice that the bot acknowledges that an issue has been updated within the breakpoints. - Wisdom of the Day: Automation works for people. People donโ€™t work for automation. - Reviewed how to do a Progress Report! - On the comment box, click on the arrow on the top right. There should be a Progress Report Template. - Result: **Needs to be implemented. ** 5. CSS Standardization - Will need to refactor because some HTML codes look different. - Should we standardize to have the pages open a new tab? 6. Donate Link - https://www.hackforla.org/donate/ (with the forward-slash) redirects to https://www.codeforamerica.org/donate/ - Need to bring this up with Design. Meeting began at 12:06 PM. [Link to the full minutes](https://docs.google.com/document/d/1ZcE20URGmfyevE_fs9U7b5Z5MaikasjXp0s6T5YQ0I4/edit?usp=sharing)
Aveline-art commented 2 years ago

Agenda for August 15, 2021

abenipa3 commented 2 years ago

Post-meeting notes, August 15, 2021

Click for notes Meeting started at 11:42 AM - Designated a note-taker who will follow up on issue creation: - Alyssa Benipayo - Announced getting sample population for UX research team Homepage Research - Donors / Partners / Advisors #2015 - UX is in a research phase now. - They want to interview them so that the Design team can create mockups catered to Donors on our HfLA website. - If you know anyone who donates, please reach out to Kristine Eudey, Simone Campbell, and Basudhara Sen. - Assign pull requests - Bonnie reminded us to always update the Resources/Instructions section if we come across new information. - We also went over our pull request category, which looks aligned. - When looking for pull requests to review, please look at โ€œReview Requiredโ€ under PR. - Assigning Issues Session - Went over (6) available small issues. - Assigned Megan Lo #2007 Meeting ended at 12:00-ish PM
Aveline-art commented 2 years ago

Agenda for August 22, 2021

SAUMILDHANKAR commented 2 years ago

Post-meeting notes, August 22, 2021

Click for notes
Aug 22, 2021; 10:07 AM Note taker: Saumil Questions, comments and announcements 1 Design: guide pages discussion and comments (figma) changes in title and sidebar 2 Markdown and WYSIWYG discussion Dev team meeting project board items 1 #1378 (consolidate raw colors) moved back to done column after checking off items 2 #1901 (duplicate style cases) needs more discussion, audit being considered Assigned pull requests 1 #1957 2 #1498 3 #2059 added a comment after discussion 4 #2070 smaller issues to be created (needs more discussion with design regarding colors); assigned - Ava and Mathew 5 #2136 assigned - Saumil and Adrian 6 #2140 assigned - Ava and Mathew 7 #2144 already assigned 8 #2149 assigned - Sarah and Zak 9 #2150 assigned - Blakely and Saumil 10 #2152 assigned - Sarah and Zak 11 #2156 assigned - Mathew and Adam 12 #2157 assigned - Adrian and Blakely Went over new issue approval board 1 #2061 quick discussion 2 #2079 quick discussion 3 #2089 quick discussion 4 #2090 quick discussion 5 #2091 quick discussion 6 ready for milestone (ignore) 7 #2101 discussion on the comment (reviewed issue detail line items) 8 ready for milestone (ignore) 9 #2077 issue could not be replicated, tried to duplicate the problem through a live demo, maybe already resolved New issue creation, invited new members for learning and training, Saumil will learn from and help Adam. END 11:58 PM
Aveline-art commented 2 years ago

Agenda for August 29, 2021

SAUMILDHANKAR commented 2 years ago

Post-meeting notes, August 29, 2021

Click for notes
Start: 10 AM Note taker: Saumil Make announcements Abel: #2076 program areas not incrementing values , / spaces not html friendly, might redo the function Go through developer review Dev team meeting discussion column on project board - #2138 discussion on merging with the team, will be presented to product team today. Moved to questions and reviews. - #1901 add this issue on wiki @averdin2 - #2135 once wins feature 1 is merged the actions to be turned into issues @arghmatey - #2014 @Aveline-art will have meeting with @alyssabenipayo to discuss the issue Assign pull requests #2011 waiting for merge conflicts to be resolved, peer programming #2059 waiting should be done by Tuesday #2181 to be done on Tuesday meeting Monthly workflow demo: none Go through new issue approval Reminder to give a status report by the Sunday meeting Main meeting - Discussion on see more, modal, expand all... - Should we remove see more on mobile view: looks fine - See more not aligned in mobile view, need to create an issue - Went ahead with merging wins feature 1 branch, recorded. - #1996 COP information updates, only text should have been copied; back space removed, works fine. Create, edit, delete format; discussion on level of details. - Where should the check happen, image type can be included in the template. - testing library issue creation @aveline-art. - discussion on renaming of label, introducing devops label, requirement in devops CoP, might reach out to Darren. - Update on table by @averdin2: writing scripts and testing them out, adding people to google drive and GitHub (main MVP), getting all data we need, bot account that can add people to teams, looking to avoid hard coding of tokens (Person access tokens), can have a database for that, need to follow up on one password vault with Chelsea. - #2168 and #2167 moved to vrms. - Board analytics demo by @aveline-art to Bonnie - #2128 new issue forms, issue was opened. END: 12:20 PM
Aveline-art commented 2 years ago

Agenda for September 05, 2021

blakes24 commented 2 years ago

Post-meeting notes, September 5, 2021

Click for notes ## Dev Meeting ### Announcements - none ### Review Column - Sarah will create issues for wins page remaining issues #2135 - Ava will discuss deployment options with alyssa #2014 ### PRs - no progress on #2011 Mathew will reach out to Celine for pair programming - PR #1407 still draft, ask Jack if he has more questions and if not to undraft it - assign #2214 to Adrian and Megan - assign #2223 to Sarah - no labels on #2224 Ava will look into why GHAs didn't work on the PR - assign #2224 to Blakely and Gary ## Main Meeting #### Technologies dropdown - may be difficult to get projects to categorize their technologies - leave as is for now - wait until we have a CMS then we need to discuss with all teams what categories to include - voted for wide version of dropdown - responsive to screen size, however many columns fit within card area - voted for scrollbar with max height based on screen size #### Guide pages - voted for full bolded menu - voted for no emojis #### Home page Top technologies - add tooltip for technology name - add link on 29 more - create unique ids for technologies linked to url string, discuss data structures in backend meeting #### Impact section - voted to prefer blue block visually - will discuss the section design further #### Tables - tables how do we make script secure for api keys? - make a website admin folder, leads can control permissions - add security to Thursday agenda #### New Issues - new issues use refactor lables when appropriate - create new refactor lables if necessary #### Technologies - review top technologies and determine if any important technologies are missing - add Figma, data science technologies (Jupyter Notebook, Google Coloab) #### Tables automation testing - need proof of concept before gettin access to all teams - tables team needs to meet with Bonnie
Aveline-art commented 2 years ago

Agenda for September 12, 2021

adrian-zaragoza commented 2 years ago

Post-meeting notes, September 12, 2021

Click for notes Always design by committee. No Announcements Developer team meeting discussion items: - Add your duplicate classes #1901 - Added a comment to the ticket looking for an update if the ticket should be open. - Github issue forms - Adrian to do tickets to move issue templates to github issue forms - Add a refactor github form. - Additional comments section: how I landed in the problem. Context. - Feedback, or like a survey area - If you have github issue blockers - We can move any issue to the development team meeting discussion items if you want the item to be discussed in the meeting. - Add label to issue help wanted to issue or ping the channel - PR Reviews - PR #2208 - Matthew to review - Adam to review - A progress report comes from the github actions - Demo - ![image](https://user-images.githubusercontent.com/77212035/133001626-216c9e53-57c8-429a-8fed-548e331c4eff.png) - It gets auto commented into your issue if there is no update after a week.
Aveline-art commented 2 years ago

Agenda for September 19, 2021

adrian-zaragoza commented 2 years ago

Post-meeting notes, September 19, 2021

Click for notes - Announcements: None - Development Review - Issue #1901 Issue was closed. If this still is still open, please reopen. - Issue #1977 - Saumil made an issue in his repo, need to configure in progress project column. - Configure secrets to your repo - https://docs.github.com/en/actions/reference/encrypted-secrets - https://github.com/hackforla/website/projects/7#column-7198229 - Column id are the 7198229 for the done column. To select another column, click the โ€ฆ dots on the top of the column and copy the link. - Anyone can hop in to issues that have a help wanted label. - PR - #1957 Ava to contact Alex, upon no reply will figure out what is left to do before the merge is complete. - #1498 Update requested. - Creating an issue - Overview: Just a quick overview of what the issue is. Should start off like "As a developer..." then explain the problem and the benefit of the solution. - Actions: You can create a checklist with the checklist. - Resources: Add links to the pages where the code will need to be changed. Screenshots or a gif of before and after.
Aveline-art commented 2 years ago

Agenda for September 26, 2021

blakes24 commented 2 years ago

Post-meeting notes, September 26, 2021

Click for notes
- Announcements: none - Review column: - #2255 will discuss with design and PMs - #2127 missing labels comments - Need to add documentation to wiki to be linked in Additional resources - explain next steps for issue - Missing labels reminder - add comment that if you're not sure what label to add someone will review it and add correct label - Assign PRs - #2268 - Saumil and Michael - #2305 - Saumil and Tomas - New Issues Demo - demonstrate how to add labels - Required label types: Feature, Size, Role - size based on how much time it is expected to take - lead will review issue, if it meets requirements the Ready For Milestone label is added - PMs will review issue and adda milestone - milestones are numbered in order of priority
abuna1985 commented 2 years ago

Agenda for October 2nd, 2021

abuna1985 commented 2 years ago

Announcements for 10/03/2021

Let's celebrate our contributions/wins for the week of 09/26/2021 - 10/3/2021

:star2: ย A huge thank you/Congrats to @blakes24 for accepting a role to join the website-merge team. She is a welcomed addition who has many great examples of detailed pull requests and well-thought-out code. She will now have the ability to merge pull requests that she feels is ready to be added to the website. :star: :star: :star:

:star2: Congrats to @macho-catt for gettingย Refactor 'Add-Missing-Labels' GitHub Actionย #2310ย merged. A big thank you/congrats for taking over managing the back-end! :star: :star: :star:

:star2: ย Congrats to @robertestrada n getting his first PRย Refactor 'Add-Missing-Labels' GitHub Actionย #2310ย merged! You can now work on any issue with the labelย good second issue. :stars: :stars: :stars:

:star2: Congrats to @Zhu-Joseph for gettingย Add program area to adopt-civic-art.md fileย #2305ย merged. This is his 6th contribution! Keep up the good work! :stars: :stars: :stars:

:star2: Congrats to @linds-fonnes for submitting her 3rd PR (Moved wins.html script into own JS file 2116ย #2313). Feel free to pick up any size issue when your PR is merged. :stars: :stars: :stars:

:star2: Congrats to @IpshitaSingh for submitting her 3rd PR (Fixed โ€˜Delegateโ€™ image credit: name, link, and artistย #2314) Feel free to pick up any size issue when your PR is merged. :stars: :stars: :stars:

:star2: Congrats to @mdhailwood1 for submitting his 2nd PR (Add programs to shared-housing-project.md fileย #2315) and providing a PR review. Feel free to pick up any size issue when your PR is merged. :stars: :stars: :stars:

:star2: Big shout out to @R-Tomas-Gonzalez for submitting his 3rd PRย New citizen engagement pageย #2324. He completed the mockup within 2 weeks of being assigned the issue. Congrats on delivering aย Largeย size issue in a quick turnaround. Feel free to pick up any size issue when your PR is merged. :stars: :stars: :stars:

NOTE: A big and heartfelt thank you to everyone for volunteering your time to help work on this site. I know Bonnie and the leadership team appreciates everything you have done so far. Let me know if there is anything I can do to help accommodate so you can feel confident in contributing to the site. See you Tuesday night! :wave: :wave: :wave:

abuna1985 commented 2 years ago

Agenda for October 10th, 2021

blakes24 commented 2 years ago

Post-meeting notes, October 10, 2021

Click for notes
- Hacktoberfest good first issues - gh actions don't work outside organizations - add prerequisite to issues - read contributing guide - send back comment if PR doesn't have correct format - update contributing guide to clarify steps for making a pull request - create a special Hacktoberfest message for new contributers - Container size inconsistent with design system on citizen engagement page #2180, discuss with design - Audit code for b tags, should be changed to strong
abuna1985 commented 2 years ago

Announcements for 10/10/2021

@abuna1985 will update the Contributing.md file to provide a clear example of completing a pull request. He will also be creating a custom message for the Hacktoberfest participants about how to get their pull requests merged.

@abuna1985 Has created a poll for the design system name. The design team chose 3 names and now we will be listing our preference from 1-6 between Tiramisu, Mochi, Saber, Biblio, Fabric, and Nucleus. Voting will end at 10 AM PST next Sunday (October 17). The top 3 will move onto the final round of voting. If you could please vote this week it would be greatly be appreciated.

Vote here: https://app.usabilityhub.com/do/76851981216b/7fc

Let's celebrate our contributions/wins for the week of 10/3/2021 - 10/10/2021

:star2: Congrats to Blakely (@blakes24) for providing a demo of our dev/prod prototype at Thursday's meeting. I can't wait until it is implemented! :star: :star: :star: :star2: Congrats to Andrew (@aalieu) for submitting his 7th pull request (#2338). Feel free to pick up any size issue when your PR is merged. Keep up the awesome work! :stars: :stars: :stars: :star2: Congrats to Adrian (@adrian-zaragoza) for submitting his 5th pull request (#2340) Feel free to pick up any size issue when your PR is merged. Also, Thank you for picking up the GitHub issue forms for the PMs. It is greatly appreciated! :stars: :stars: :stars: :star2: Congrats to Joseph (@Zhu-Joseph) for submitting his 7th pull request(#2352). @abuna1985 has requested changes and updated the issue action items. Once updated and merged, feel free to pick up any size issue when your PR is merged. Thank you for your contributions! :stars: :stars: :stars:

NOTE: A big and heartfelt thank you to everyone for volunteering your time to help work on this site. I know Bonnie and the leadership team appreciate everything you continue to do to help us. Let me know if there is anything I can do to help accommodate so you can feel confident in contributing to the site. See you Tuesday night.

Keep up the awesome work @hackforla/website-write team! :wave: :wave: :wave:

abuna1985 commented 2 years ago

Agenda for October 17th, 2021

abuna1985 commented 2 years ago

Post-meeting notes, October 17, 2021

Click here for notes

abuna1985 commented 2 years ago

Announcements for 10/17/2021

Our final round of voting has started and will end at 10 AM PST next Sunday (October 24).

Vote for design system name here: https://app.usabilityhub.com/do/ed3e56977fd8/b9c7

Let's celebrate our contributions/wins for the week of 10/10/2021 - 10/17/2021

:star2: Congrats to Lindsey (@linds-fonnes) for accepting a job offer!!!! She will not be able to contribute to Hack for LA, but I just wanted to thank her for all her participation in meetings/contributions. Your new company is lucky to have a hard-working developer like you! We wish you the best of luck as you take on your new role! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to Andrew (@aalieu) for getting his 7th pull request (#2338) merged! Thank you for all of your contributions and keep up the great work! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€

NOTE: A giant thank you to everyone on the team for continuing to volunteer your time to help work on this site. I know Bonnie and the leadership team appreciate everything you continue to do to help us. Let me know if there is anything I can do to help accommodate so you can feel confident in contributing to the site. See you Tuesday night.

Keep up the awesome work @hackforla/website-write team! :wave: :wave: :wave:

abuna1985 commented 2 years ago

Agenda for October 24th, 2021

edeneault commented 2 years ago

Hello,

I donโ€™t seem to have a meeting in my schedule todayโ€ฆ could I be added to this schedule or alternatively how do I add myself?

Kindly,

Etienne

Sent from my iPhone

On Oct 24, 2021, at 9:56 AM, Adam Abundis @.***> wrote:

๏ปฟ Agenda for October 24th, 2021

Designate a note-taker who will follow up on issue creation Make announcements @abuna1985 has announcement Share wins/celebrations for the week Congrats to Chris @.) for getting his 1st pull request (#2387 ) merged! Feel free to pick up any issue with the label size: good second issue. ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to Etienne @.) for getting his 1st pull request (#2381 ) merged! Also Congrats on submitting your second pull request (#2394 ). Keep up the great work! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to our Hacktober participant @Aryannath for getting their1st pull request (#2358 ) merged! Thank you for contributing and feel free to join our team so you can continue volunteering! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to our Hacktober participant @SumayyaZiyad for getting their1st pull request (#2359 ) merged! Thank you for contributing and feel free to join our team so you can continue volunteering! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to our Hacktober participant @Chetana16032002 for getting their1st pull request (#2378 ) merged! Thank you for contributing and feel free to join our team so you can continue volunteering! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to Adrian @.) for getting his 5th (#2340 ) and 6th pull request (#2377 ) merged! I am sure the @hackforla/greenearthos will be happy to see their project card/page has been updated! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to Joseph @. ) for getting his 7th pull request (#2352 ) merged! Keep up the awesome work! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ The Contributing.md has been updated with the following merged pull request (#2372) made by me @.). I have one more round of edits planned. ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Congrats to Bonnie @.) for merging #2369 . I am sure the @hackforla/expunge-assist team will be happy to see their project card/page has been updated! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ Go through the developer review column Assign pull requests Monthly workflow demo (see above): 4th Sunday: Labels, milestone usage, and issue approval process Recap today's meeting Reminder to give a status report by the Sunday meeting โ€” You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

abuna1985 commented 2 years ago

@edeneault My apologies for the confusion. I have sent a calendar invite to your Gmail address for the Sunday All Team meeting (10 AM PST - 12 PM PST) as well as the Tuesday Dev meeting (7 PM PST - 8 PM PST). You can also find meeting links in our Website Team Meeting card here: https://github.com/hackforla/website/projects/7#card-47984166

abuna1985 commented 2 years ago

Announcements for 10/24/2021

Let's celebrate our contributions/wins for the week of 10/17/2021 - 10/24/2021

๐ŸŒŸ Congrats to Chris (@chrisfoose) for getting his 1st pull request (#2387 ) merged! Feel free to pick up any issue with the label size: good second issue. ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to Etienne (@edeneault) for getting his 1st pull request (#2381 ) merged! Also Congrats on submitting your second pull request (#2394 ). Keep up the great work! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to our Hacktober participant @Aryannath for getting their 1st pull request (#2358 ) merged! Thank you for contributing and feel free to join our team so you can continue volunteering! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to our Hacktober participant @SumayyaZiyad for getting their 1st pull request (#2359 ) merged! Thank you for contributing and feel free to join our team so you can continue volunteering! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to our Hacktober participant @Chetana16032002 for getting their 1st pull request (#2378 ) merged! Thank you for contributing and feel free to join our team so you can continue volunteering! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to Adrian (@adrian-zaragoza) for getting his 5th (#2340 ) and 6th pull request (#2377 ) merged! I am sure the @hackforla/greenearthos will be happy to see their project card/page has been updated! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to Joseph (@Zhu-Joseph ) for getting his 7th pull request (#2352 ) merged! Keep up the awesome work! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ The Contributing.md has been updated with the following merged pull request (#2372) made by me (@abuna1985). I have one more round of edits planned. ๐Ÿš€ ๐Ÿš€ ๐Ÿš€ ๐ŸŒŸ Congrats to Bonnie (@ExperimentsInHonesty) for merging #2369 . I am sure the @hackforla/expunge-assist team will be happy to see their project card/page has been updated! ๐Ÿš€ ๐Ÿš€ ๐Ÿš€

NOTE: A giant thank you to everyone on the team for continuing to volunteer your time to help work on this site. Especially our Hacktoberfest contributors who helped our open-source community. Let me know if there is anything I can do to help accommodate so you can feel confident in contributing to the site. See you Tuesday night!

Keep up the awesome work @hackforla/website-write team! :wave: :wave: :wave:

abuna1985 commented 2 years ago

Announcements for 10/31/2021

Click here to see the detailed final vote ![Screenshot 2021-10-31 103045](https://user-images.githubusercontent.com/21162229/139595164-9d926a53-f80d-4b9c-a09b-ef6dd3d0ae74.jpg)
name score
Nucleus 1.77
Fabric 2.00
Biblio 2.23

The winner is...

Nucleus

The Hack for LA website design system name is now Nucleus. @hackforla/website-merge @hackforla/website-design Please work with each other for the implementation of Nucleus into our design system page.

Let's celebrate our contributions/wins for the week of 10/24/2021 - 10/31/2021

๐ŸŽƒ Congrats to Etienne (@edeneault) for getting his 2nd pull request (#2394 ) merged. Feel free to pick up any Small, Medium, or Large issue in the Prioritized Backlog column. Keep up the great work! ๐Ÿฅ‡ ๐Ÿฅ‡ ๐Ÿฅ‡ ๐ŸŽƒ Congrats to Tomas (@R-Tomas-Gonzalez ) for getting his 3rd pull request (#2375 ) merged! Keep up the awesome work! ๐Ÿฅ‡ ๐Ÿฅ‡ ๐Ÿฅ‡ ๐ŸŽƒ Congrats to Matthew (@macho-catt ) for merging his 15th pull request (#2380 ). Make sure you support him because he does a lot for this team. Keep up the awesome leadership! ๐Ÿฅ‡ ๐Ÿฅ‡ ๐Ÿฅ‡ ๐ŸŽƒ @abuna1985 (I) have updated the Contributing.md with (#2399 ). I hope it helps make the onboarding process a bit easier. โญ โญ โญ ๐ŸŽƒ @abuna1985 (I) completed all requests for project team page updates (#2398 , #2402, #2403 , #2405 , #2406 ). โญ โญ โญ

NOTE: This is my (@abuna1985 ) final day as Tech Lead for the website dev team. It has been an honor and a pleasure to work with @hackforla/website-write, @hackforla/website-merge, @hackforla/website-pm, and @hackforla/website-design for the last 5 months. I have learned more about working with a team during this time than I did working for 2 years as a developer in marketing agencies. My final parting words are: Keep learning, keep growing, keep making mistakes here so you can learn and be ready for the next opportunity that comes your way. Thank you for continuing to volunteer with Hack for LA and I wish you all the best!

As always, Keep up the awesome work @hackforla/website-write team! ๐Ÿฅ‡ ๐Ÿฅ‡ ๐Ÿฅ‡

SAUMILDHANKAR commented 2 years ago

November 7, 2021

To bring up with PM/UI/UX

macho-catt commented 2 years ago

Agenda for November 14, 2021

To bring up with PM/UI/UX

macho-catt commented 2 years ago

Agenda for November 21, 2021

To bring up with PM/UI/UX

macho-catt commented 2 years ago

Agenda for November 28, 2021

To bring up with PM/UI/UX

macho-catt commented 2 years ago

Agenda for December 5, 2021

To bring up with PM/UI/UX

Notes from meeting

Click for notes December 5, 2021 Hack for LA Website Team Meeting Notes Regular room - Individual introductions - Goal for everyone to work towards is to become merge lead ____________________ Breakout room - Sunday meetings schedule: all in big room, breakout room for about 30 minutes, and regroup to large room - Wins: good first issues immediately after Tuesday meeting - Announcements: Sunday, 12/19 Matt leaving - Matt created an "Issue: Alt Text Audit" template for changing alt text to conform with guidelines - Pull request assignments - Guide for reviewing pull requests: https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests - Tomas questions about his forked repo: 1. Q: GitHub showing a message needing to create a new pull request, even though there is an existing pull request. A: Don't need to create a new pull request. Can delete the branch if the pull request already merged into Hack for LA repo. 2. Q: Fetching upstream and showing the fork is ahead in terms of commits A: git checkout -b upstream-gh-pages --track upstream/gh-pages Note: Tomas will be adding more info about this in the contributing log - Johnnie: Q: In pages/credits.html, where does site.data.internal.credits filter to? A: Each yml under _data/internal/credits ____________________ Regular room - Changing from small-medium-large to story points - Example: https://github.com/hackforla/open-community-survey/issues/13 - More info: hackforla/ops#18 - Credits page - UI/UX responsible for what alt text should say - Tip: Stay organized and help write how-tos/guides. - Going over issues in UAT column - In Figma, shows the current version of the site on desktop and mobile. - Issue #2515 assignments - Issue link: https://github.com/hackforla/website/issues/2515 - Development team complete the following columns in spreadsheet: - Area/section in the code - Current alt text - Location in the code - Webpage
SAUMILDHANKAR commented 2 years ago

Agenda for December 12, 2021

To bring up with PM/UI/UX

Notes from meeting

Click for notes Notes from today's meeting. - Jim Sunday, December 12 website meeting attendees: Anthony Sim, Jim Geist, Matthew Cacho, Miguel Lopez, Saumil, Jessica Cheng, Lindsey Dinkel, Tomas Gonzalez, Johnnie Hicks, Shantau Shende Wins celebrations (12/5 - 12/12) Following developers all finished their second issues: @sydneywalcoff (Update how 'Overview' link opens for Civic Opportunity #2564), @JessicaLucindaCheng (Updated design systems' project profile with current project team #2556), @Johnnie007 (Updated Diversity link in Credit page-2094 #2551), @anthonysim (updated overview link opens Access The Data-2234 #2549), @lopezpedres (Update ballotnav overview link 2235 #2545), @jqg123 (add link giving credits #2538) and @JimGeist ( Add new project to website: EMS Triage Tracker #2383 #2535). Feel free to pick up any Small, Medium, or Large issue in the Prioritized Backlog column. Keep up the great work! :first_place_medal: :first_place_medal: :first_place_medal: Make announcements Congrats to Miguel for gaining citizenship to Canada. Assigning pull request reviews Updated Getting Started page header text #2577 โ€“ Anthony, Johnnie remove-languages-2487 โ€“ Miguel, Jessica Update Icon Alignment Step Cards #2574 โ€“ Jessica, Jim Include project links in project page #2566 The remaining pull requests are being worked on. Go through the project board When commenting on an issue, please add following to your comments at the bottom of your issue and answer: (from https://github.com/hackforla/website/issues/1977#issuecomment-990677444) Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures: "Add any pictures of the visual changes made to the site so far." The action checks for activity every 7 days. The action checks and posts on Fridays. Alt text will get reviewed and completed by design. If they feel the text needs to change, they will note it and we will create an issue. George (not present in meeting) had a question about feature branches. You make pushes on the feature branch (feature-homepage-launch), not the main branch This pertains to issues tagged Feature: Feature Branch These issues also have Note: Feature Branch towards the top of the overview. The feature-homepage-launch branch will probably be multiple commits behind gh-pages branch. The git commands were demoโ€™d way to quickly for to document in these minutes. The gist seemed is that you have a local feature-homepage-launch branch, you keep your local feature-homepage-launch branch current with the hackforla version using commands similar to keeping gh-pages current. You create a branch for your issue off of the feature-homepage-launch, NOT the gh-pages branch. You push your issue to your github feature-homepage-launch, not gh-pages. Not sure if different remotes are needed for this. Best bet is to ask when working on Feature Branch issues. Main Meeting key topics: Today is Matthew Cachoโ€™s last Sunday meeting. Connect to Matthew on LinkedIn. His linked in is listed in the roster. Tomas is best to catch on Sunday as he does not make the Tuesday meeting. He is available always on Slack. Bonnie gave a quick figma demo. Figma is checked because it shows what the to-be designs are and what designs are currently active. The โ€˜Creditsโ€™ example showed a difference because the width on the to-be figma diagrams differed from the widths on the site. Saumil and Tomas will review the figma designs and craft issues for fixes. Link to Figma: https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=8561%3A72465 Office Hours (1 hr) -- Thursdays, 7pm PST โ€“ Saumil will continue running these. He has also been attending the office hours with Matt. Tomas is available during the week and will certainly jump in and help. Bonnie asked that we all use the slack channel and be as descriptive as possible with our issue because someone else may have had a similar issue and could help. When you are in Slack, you can also link to your issue comment by clicking on the ellipsis (. . .), Copy link, and paste it into slack. If our piers were not able to help, then reach out to Tomas or Saumil after a reasonable amount of time. Saumil and Tomas will host the Tuesday night 7pm PST website team meeting. We all need to aspire to get on the website Merge team. Do this by moving through levels to a hard issue and perform pull request reviews. These are tasks that will help us all grow as developers and team leaders. https://github.com/hackforla/website/wiki/Being-a-Part-of-the-Hack-For-LA-Team#phase-2-how-to-train-yourself-to-become-a-leader
SAUMILDHANKAR commented 2 years ago

Agenda for December 19, 2021

To bring up with PM/UI/UX

Notes from meeting

Click for notes Agenda for December 19, 2021 **Attendees:** Jessica Cheng, Jim Geist, Anthony Sim, Sydney Walcoff, Tomas Gonzalez, Miguel Lopez, Saumil Dhankar, and Shantanu Shende Wins celebrations since last meeting โ€ข Congratulations @lopezpedres for getting third pull request (small back end issue) #2590 merged. Good job! โ€ข Congratulations @sydneywalcoff for getting third pull request (small front end issue) #2574 merged. Thanks for your contribution! โ€ข Congratulations @anthonysim for getting third pull request (small back end issue) #2575 merged. Keep it up! โ€ข Congratulations @JessicaLucindaCheng for getting third pull request (medium front end issue) #2588 merged. Great work! โ€ข Congratulations @lindseyindev and @Georgema20 for getting their first and second PRs merged. Feel free to pick up any Small, Medium, or Large issue in the Prioritized Backlog column. Keep up the great work! [ ] Make announcements - Saumil will keep the Thursday office hours - When picking up a new issue, please place your availability and ETA in the issue. Availability should go into the issue, not your pre-work checklist. Saumil and Tomas will โ€˜touchโ€™ as necessary to see where we stand. - Please add your availability and ETA even if the pop-up does not appear when you self-assign or are assigned an issue. Tomas will talk to Matt about this one. - Sunday meeting will occur on Sunday, December 26 and Sunday, January 2, 2022. [ ] Assigning pull request reviews - New icons โ€“ the top of the form for the issue (Add credits for photos and icons for redesigned homepage #2528) requires more details. - Reviewer: Jim Geist - [Update citizen engage 2474](https://github.com/hackforla/website/pull/2603) (Update the Citizen Engagement page so the project data is dynamic [#2474](https://github.com/hackforla/website/issues/2474)) - Issue also discussed in larger meeting because the text on the page is place holder text. Bonnie will identify who will create new content when the issue is in QA. In the interim, complete the issue. Includes should be included (press page is a good example) of how the page should get structured so it can serve as a template for other project area pages. - Reviewer: Miguel Lopez - Update Sitemap Spelling 2465 (Ensure consistent spelling of "Site Map" across the site #2465) - Reviewer: Syndey Walcoff, Anthony Sim - Tooltip with long text cuts off when hovering over wins icons #2408 (#2408) - Reviewer: Jessica Cheng, Miguel Lopez โ€“ Update VRMS Profile (Update Project Profile: VRMS #2552) - Issue resulted in a larger discussion because changes made for the issue were not clear and additional information was available on the issue because of project card changes to pull in more links. [ ] Go through the project board [ ] Dev team meeting discussion items - There might be different command we can use when pulling issues for work. Jessica will discuss with Saumil / Tomas. - When working on an issue, fetch upstream and make sure local branch is up to date to what is committed. Fetch upstream every day to keep your local branch up-to-date. Once you know how you will approach changes to the issue, start making changes for the issue in your local brach. - Refer to pinned note in hfla-site slack on Dec. 5 from Tomas: [here are the commands for doing the work โ€” that is, bringing your local branch up to date with the upstream](https://hackforla.slack.com/archives/C4UM52W93/p1638731204070500) - Documentation on syncing up your repository is under the [Working on an issue section under **2.7.e](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#27e-working-on-an-issue-5-incorporating-changes-from-upstream)** - When you make a pull request and you realize you want to further update your issue, there is no need to cancel the pull request. The code can continue to change once pushed back up to your GitHub fork of the website, the changes are automatically visible in the existing pull request. Just make sure the pull request or the issue are not closed. - โ€œmain roomโ€ discussion โ€“ Bonnie mentioned that going live with the updated webpage is a hackforla/product-management#1 priority and is reviewing the steps involved to ensure no blockers, design issues are resolved, issues required for milestones were delivered, and to ensure that stories are not missing any issues. [ ] In progress column/questions and reviews
SAUMILDHANKAR commented 2 years ago

Agenda for December 26, 2021

To bring up with PM/UI/UX

Notes from meeting

Click for notes
SAUMILDHANKAR commented 2 years ago

Agenda for January 02, 2022

To bring up with PM/UI/UX

Notes from meeting

Click for notes
SAUMILDHANKAR commented 2 years ago

Agenda for January 09, 2022

To bring up with PM/UI/UX

Notes from meeting - Notetaker: @lindseyindev

Click for notes Welcoming new member Tamara, first meeting, who is working on their first issue. Miguel updating us on issue to add unique ids to wins objects for the Hack for LA wins page, will be coordinating with Saumil and Tomas to test permissions and implementation. Introductions Tomas did a demo on draft issues and creating new issues through ideas from > New issue approval > development issues to make You create a new issue, choose blank issue template, and then fill out the issue and keep Saumil, Jessica, and Tomas in the loop about your issue. There is a How To create issues Wiki guide [Hack for LA Wiki](https://github.com/hackforla/website/wiki) You can also search labels for the front end on current issues and you can see if there are similar issues that you can structure including action items and resources. Tomas gave recommendations on how to structure issues with examples and to include resources like links to the issue creatorโ€™s slack and designerโ€™s slack for easy communication. More information will be provided and discussion on converting draft issues at Tuesday meeting Assigning PR Reviews Moving back to the main meeting Confirmed minimum font-size for readability is 16px through design systems typography on figma Discussed needing to use the same class names and how a p tag is not sufficient as it leads to different font sizes across pages.
JessicaLucindaCheng commented 2 years ago

Agenda for January 16, 2022

Facilitator: @JessicaLucindaCheng

To bring up with PM/UI/UX

Notes from meeting - Notetaker: @anthonysim

Click for notes - Update tech dropdown implementing the mobile design and Version C of the desktop design for the Technologies/Languages dropdown. - Saumil spoke with Isaac during the Design meeting to update the Projects page, so devs know what Design Team wants for the page. - Pull Requests, went over, everyone is already designated a reviewer. - Project Board, no specific issues. - Typography, use _sass/variables/_typography.scss as reference. - Tamara added a line in an md file and used docker-compose up. If changes are not showing up delete site, .jekyll-metadata, then redo docker-compose up. - We are going to ask design if they can lowercase class names on Figma Design. - Tomas got a new job and will be off-boarding Hack For LA soon.
SAUMILDHANKAR commented 2 years ago

Agenda for January 23, 2022

To bring up with PM/UI/UX

Notes from meeting

Click for notes **Figma discrepancies** If you're working on an issue and the design on the site is different from the Figma, let Isaac (design lead) know about the change on Slack **Assigned PR review** **Tips for reviewing pull requests:** - Consult contributing.md - Thereโ€™s a pin in the general channel - Pull down the PR creator's branch using the commands listed and make sure the changes work as expected - Go through the โ€œHow to review pull requestsโ€ Wiki at least once since Hack for LA does things in a specific way **Monthly workflow demo** - How to add labels to issues: Click the cog beside โ€œLabelsโ€ section on the issue. Check relevant labels - Minimum of four labels to describe the issue: complexity, role, feature, and size (1pt = 6hrs work) - Thereโ€™s a step-by-step guide for writing issues on the Wiki: โ€œHow to create issuesโ€ **Other notes** - Ready for milestone means Bonnie will go through and put in milestones - Donโ€™t pick up issues in the new issue approval column! Pick from the prioritized backlog
JessicaLucindaCheng commented 2 years ago

Add these to the Wins for Sun, Jan 30 meeting:

SAUMILDHANKAR commented 2 years ago

Agenda for January 30, 2022

To bring up with PM/UI/UX

Notes from meeting

Click for notes Change in schedule for next week
Still work on issues, make pull requests and review pull requests
Any questions, reach out on slack
Reference Figma and Issac on slack for asking questions about design
To find the link to Isaac/Figma go to the project board and scroll through the Onboarding info/links until you find them.
You should usually be able to reach out through the link on the specific Issue to whoever would answer questions about a particular pull request
Assigned pr review
checked the Dev Team Project/Questions in Review for questions (Isaac wasn't here, couldn't ask him questions)
Work flow demo on how to do a pr review.

Going through QA with Bonnie
Specifically
Going through accomplishments page with Bonnie, to figure out how to see multiple years of accomplishments, see more link vs multiple year links vs just an accordion -PM will speak to design about it (picked accordion).
JessicaLucindaCheng commented 2 years ago

Agenda for February 13, 2022

Announcements

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

Meeting items

To bring up with PM/UI/UX

Notes from meeting - Notetaker: @blulady

Click for notes -Jess reminds us to pull gh before working on issues.
-Jess reminds us the order of issues
-Jess assigns pr reviews
-Jess goes over what happens during a pr review and posts the link to the guide
-Jess goes over pr change requests (hit circle on the right of the pr to refresh request)
-Jess reminds us to put an "To Update" label on issues that sit longer than a few days
-Saumil reminds us about the office hours from 7-8pm
-Samuil explains the comment that needs to be applied if there is a "To Update" label:
if you have been inactive on an issue for more than 7 days
remove the label, apply a new "Status Updated" to the issue (after adding the comment)
-Jess explains what "working off the feature branch" is
Conferring with Bonnie
-Development had nothing for design
-Pre-work Checklist will be white with black text
-Customize all yml files used on credits page with content type field (vs content field)
-Bonnie explains an ignore label
-Docker loading time
-Jess demonstrates what files to delete _site & .jekyll-metadata
-We delete them and start docker, noting the time to start the server
-Jess and Saumil explain git commands, explains that if you get a long printout from docker after updating a single file that you should reach out so they can try to problem solve
JessicaLucindaCheng commented 2 years ago

Agenda for February 20, 2022

Facilitator: @JessicaLucindaCheng

Announcements

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

Meeting items

To bring up with PM/UI/UX

Notes from meeting - Notetaker: @tamara-snyder

Click for notes Hack for LA Dev Meeting Feb 20 Congratulations to all who got their issues approved Pull requests: - All developers are expected to review pull requests - We will be organizing an on-call sheet so that issues are reviewed faster - First and second issues should be reviewed within 24 hours, which is why there may not always be one available to review for newcomers - If youโ€™re new, aim to review a good first or second issue before you move on to reviewing larger ones - If youโ€™re a reviewer, add your ETA in a comment once youโ€™re assigned - If a change is requested, make sure to re-request a review (in the righthand side of the issue page) so that reviewers donโ€™t have to guess whether youโ€™ve made amends PR review assignments: - #2803: Saumil and Tamara - #2384: Saumil and Carlos - #2159: Carlos and Jessica HfLA On-Call sheet: - If you have an hour or more on a given day, add yourself to the On-Call spreadsheet (https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0) to review pull requests on that day - With more experience, good first and second issues will take more like half an hour to review Help Wanted Tag: - You can add this label to your issue so that people can help you - Write a comment on your issue and link it in the Slack channel so that people can help you Discussed office hours (7-8PM PST) Issue creation: - First, see the issue creation wiki (https://github.com/hackforla/website/wiki/How-to-create-issues) - Search for the feature label on the issues page - See if thereโ€™s an existing issue that addresses the problem you found - If thereโ€™s not an issue, press New Issue and start creating one - Use the blank issue template - Issue descriptions tend to become less descriptive as the complexity of the issue grows - Link related issues - Choose at least three labels for your issue: list here (https://github.com/hackforla/website/wiki/How-to-read-and-interpret-labels) Epic Issue #2775 - We will all be creating issues from the spreadsheet - We will be changing content to content-type in all of the files - We went through the creation of one issue together in the meeting - To get the permalink, go to the line of code in the file on Github, click on the three dots, and click โ€œcopy permalinkโ€ - Spreadsheet can be found here: https://docs.google.com/spreadsheets/d/1yHo08dVVxI-Bvf_4MXJwMB9jSTr23pk_pydirWkgDgs/edit#gid=0 - Once finished, link your issue to the spreadsheet and add the issue to the project board ALL HANDS Discussed decision records on solutions not implemented - Decision records provide a template for recording problems and potential solutions that were worked on but not implemented - The point of these is to document past decisions and time spent on solving problems for the team These show up on GitHub profiles and ensure that no work was done in vain Bonnie shared a resume building tool for documenting things worked on while at Hack for LA: (https://docs.google.com/spreadsheets/d/164RGPJK3b5IdmWhici-d8Qss1_PvGPL5gwsEHujxTfQ/)
JessicaLucindaCheng commented 2 years ago

Agenda for February 27, 2022

Facilitator: @JessicaLucindaCheng

Announcements

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

Meeting items

To bring up with PM/UI/UX

Notes from meeting

Click for notes Note-taker: Sarah Jessica Cheng Tamara Snyder Jessica Cheng Utkarsh Saboo Saumil Hiram Riddle Adolf Schmuck Devin - Engineering Sarah Sanger If you don't show up for a week: let people know need to show up to Tuesday meeting or Thursday office hours Leave small/new issues for new members Assigned Pull Requests: left eta/availability on prs Reviewed On-call schedule for PR requests: reach out if you get overwhelmed on your on-call days asking for feed back on the On-Call schedule most people thought it was a good learning experience someone was struggling to find good first/second issues another person was struggling to find issues without reviewers Demo How-To-Review-Pull-Requests: go to link check the correct branch: trying to merger into gh-pages from issue-issue number go to pr & check if number is at the top of a pr then go through the issue: check for changes made check for why the changes were made check for screen shots or note: no visual changes go to files changed and can click on line number to comment specifically on that line Joined back to main room: requested approval for small issues, good first issues be "ready for milestone" made change to issue created - change because "fields are redundant" gave milestone "team work flow", prioritized Bonnie explained "technical debt" reworded weekly meeting requirements in Contributing.md discussed FIGMA "tiny text" tablet/mobile/desktop Bonnie Explained "feature branches" Joined room two again: viewing Hiram's issue Utkarsh asked about milestones and technical debt Utkarsh asked about screenshots
JessicaLucindaCheng commented 2 years ago

Agenda for March 13, 2022

Announcements

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

Meeting items

To bring up with PM/UI/UX

Breakout Rooms (Till end of meeting)

Notes from meeting

Click for notes
Jessica Cheng
Tamara Snyder
Alyssa
Gabriel Garcia
Hiram Riddle
Adolf Schmuck
Sarah Sanger
Jessica goes over how to go over a pull request and where to find the pr review guide https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests Jessica - assigns pr's - shows how to put availibility/eta - explians/shows us how to sign up for being on oncall pr spreadsheet - https://docs.google.com/spreadsheets/d/1uq65QGwIpbx60JZZpqd7juHwEytDEOJap6e6u1klSVw/edit#gid=0
Jessica talks about office hours Jessica explains about progress report - progress: - blockers: - availability: - ETA: Jessica explains the status help wated label and that we should also reach out on slack (including the link from the issue) https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#25-reporting-progress-on-your-issue - Alyssa suggests using the extension for VSCode https://marketplace.visualstudio.com/items?itemName=hnw.vscode-auto-open-markdown-preview We join the mainroom - Nothing to discuss with Bonnie - Jessica answers questions about specific issues
JessicaLucindaCheng commented 2 years ago

Agenda for March 20, 2022

Facilitator: Jessica Cheng

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

Announcements

Reminders

Reccuring Meeting items

To bring up with PM/UI/UX

Notes from meeting

Note taker: Devin Krizwold Sunday 3/20 - Dev Meeting Notes Attendance: Devin Krizwold Jessica Cheng Saumil Frank Stepanski Ben Mongomery Utkarsh Saboo Gabriel Garcia Sarah S Adolf Schmuck Carlos Perez Announcements Weekly time off Jessica Monday-noon to Tuesday afternoon Saumil Wednesdays off Please only notify on slack if extremely urgent, expect delays. Post issues to hfla-site channel If access to a file or only tech lead solvable issue then Contact Tamara on those days as well. Can mention Jessica or Saumil on slack channel, allows people to see and potentially help Thanks all for contributions/wins! Meeting Items: When picking issues, please do not choose issues out of order Ex: small issue, chose the first issue! This will help avoid older issues going unaddressed 7p PST office hours on Thursday Attempt to review 2 PRs for every 1 you create Reminder to use the PR formatting from contributing.md โ€œfixes #XXXXโ€ฆetcโ€ Make sure to update your avail if you cant review it within 48hrs. If you have an issue open and the reviewer is delayed, please @ them on slack or GitHub to check-in and update ETA/Avail - if they donโ€™t have time request another reviewer on slack (hfla-site) ! reminder to get good 1st and 2nd issues reviewed in 24 and at most 48 hours to help devs get up and running quickly. ! Reminder to add a help-wanted label and comment to slacks (hfla-site) channel to get the quickest response Creating progress reports Creating Issues Add an appropriate title and description Labels: 4 required labels (size, points(pt), feature, role) ! points are not linear but look at the description to approximate issue size in points ! scan through features to find the most appropriate label ! Primarily writing for front and/or back end Add to the project board Submit! Youโ€™re done What are milestones? Done later, not part of issue creation Used to prioritize issue backlog Other projects use them differently, can be used to mark phase completion/deadlines Automation will put the issue into the new issue creation area of the project board, depending on the issue changes or additions may be made and the issue moves to โ€˜ready for milestoneโ€™ PMs will add appropriate milestones and prioritize accordingly โ€”------ End dev Break out meeting. Main room - Main issue - Design systems 2745, long-delayed ! Prioritized backlog is sorted linearly - choose the top issues! !! Documentation needs to be edited to reflect this Make sure you understand the issues, if you are unclear it's ok to ask the person who wrote the issue, re-write the issue with them if need be. The goal is to write clear code and issues. No meetings on the first through the 7th! Keep working but lets the tech leads get to organizing new issues. No meeting on Sun 3rd, No team meeting Tues 5th, no Office hours on Thurs 7th. Reminder! If moving off an issue, move back to new issue approval so Leads can reprioritize it appropriately.