DEV TEAM Meeting Agenda Thursday🌸

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

- [ ] writeYourNotesHere

### Post-meeting notes, monthAsText dd, yyyy

<details>
<summary>Title</summary>
<br>

insertNotesHere

<br>
</details>

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]

Agenda for July 6, 2021

• Wins Page Icon Parser - Bonnie has confirmed she would like icons for I mentored someone on my team and I mentored someone on another team. I need help creating an issue for the design team to come up with an additional icon for either. Regarding issue 1817
• @sena-ji would like assistance from the team troubleshooting some styling for her solution for Develop page for 404 Error Invalid URL page #1482
• discuss updating wins-feature-1 with changes made on gh-pages #1869
• @anonymousanemone would like assistance with change request for Added link to credits and join us page in footer #1880

[Aveline-art]

Agenda for July 8, 2021

• Announce usage of labels.
• @daniellex0 to speak about the backend-related portion of the design system.
• @ExperimentsInHonesty to discuss the api keys in these files 1, 2
• Discuss the best way to go about protected branches while allowing our workflow to remain as is. With protected branches, reviewers no longer have the instructions to do pull branches to their repository.
• Proposal: Have set themed breakout rooms (one for PRs, one for issues, one for questions) so that we prepare the rooms ahead of time
• This comment on the need to host pull request versions of the website for designers to view the changes and check for responsiveness
• Go through developer discussion item board
• What are some good weekly reminders to give out? Let us make a list so that we can make it a part of our meeting opening!
• Update the wiki articles that are out of date

[akibrhast]

Make an issue about updating the contributing.md such that, it walks people through the commands needed to do a pr review.

[aalieu]

Issues for Back-End Meeting July 8, 2021

• Collect people's info through google forms
  • Kill Action Network API key so if someone pulls it, it doesn't pull any data. Do a one time pull of data so we have it and store it on google drive and then kill it.
  • On home page, one line of code that says if hide = false, display code which is the api token?
• Hide sign up for newsletter on hackforla website.
  • Screenshot, save code for newsletter, put it in an issue with all the code
• Google calendar for special workshops/presentations, hack nights automatically pulled. Bring that back for events we want to highlight.
• No biggie since only whitelisted domain can access it.
• Our website is hosted on gh-pages, it doesn't have any way to store api keys. They have to be public or it doesn't work.
• Edit Tuesday slack reminder about breakout rooms. Chili pepper if you have a question (not sure if slack supports?) Slack polls to put questions?
• Set reminder for HFLA website designer meetings at 5pm
• Conduct research and form a proposal on architecture of design system page

[Aveline-art]

Agenda for July 11, 2021

• Announce on how to use Slack to ask for help (leads are not the only one who can help others!)

[Aveline-art]

Agenda for July 13, 2021

• See below comment

Post-meeting notes, July 13, 2021

Notes from Front-End Meeting

1. @jbubar announced he would be transitioning to the VRMS team. He would like to spend the next few weeks organizing wins-feature branch. He will provide more information later this week.

2. We discussed @averdin2 comment above

   • @jbubar and @Abel-Zambrano went through all issues tied to the P-Feature: Wins Page label and added comments below:

    IMPORTANT!! 
   This issue is working off of a feature branch!
   Please follow this wiki before creating a new branch!
   [how to work off a feature branch](https://github.com/hackforla/website/wiki/How-to-work-off-of-a-feature-branch)
   

   • After discussing with the dev team and @ExperimentsInHonesty, we determined a GitHub action for a Feature label which will send a message similar to the above.
   • issue for Feature label GitHub action needs to be made.

3. @jbubar wanted to bring up that since we removed merge privilege's, users who want to review pull request lost the command line instructions. The emphasis is that we either provide this information or restore merge privilege to all users (for access to the command line instructions).

   • @Aveline-art added a screenshot of command line instructions with a templatewithin the Pull Request Wiki (within Step 3)
   • We also determined that a GitHub action to add a comment below the pull request with the command line instructions with the info wrapped in [] replaced with the appropriate data:

   git checkout -b [nameOfCollaborator]-[nameOfFromBranch] [nameOfIntoBranch]
   git pull https://github.com/[nameOfCollaborator]/website.git [nameOfFromBranch]
   

   • issue for GitHub action to provide pull request command line instructions needs to be made

4. @Aveline-art wanted to bring up we do not have any documentation on how to create an issue.

   • issue for documentation on how to create an issue needs to be made

5. @abuna1985 and @arghmatey worked with @macho-catt on issue Standardize code for large icon page cards #1887

   • @macho-catt will standardize the card with flexbox
   • @ExperimentsInHonesty wrote a message to @daniellex0 regarding the placement of the CSS since this needs to be accessed by the Join Us and Site Map page

6. @Aveline-art designated @abuna1985 to oversee issue Standardizing the HFLA Design System #1850

7. @arghmatey will begin creating design system website prototype Create the design system pages #1927

Agenda for July 15, 2021

• Create a backend developer post here
• Discuss ways to take the load off of PMs when it comes to keeping track of in progress issues
• Discuss #1945 , HackForLA Wiki: New Wiki article on creating issues #1941
• @abuna1985 Create a research team to look up standards for various components and come up with HTML code
• Update the wiki articles that are out of date Tabled for now
• Work on the onboarding prototype
• Talk about agendas slack notifications
  • check the pr before the meeting and if you are stuck bring it up in the stand up
• @jbubar will talk about the messy wins backend.. what is the plan to transition to with wins form on the site, and to make sure that no ones private data is visible
• Discuss designer liaison tabled for now
• Create a virtual happy hour for H4LA. Not sure how this will work, but intuitively maybe like Discord chat. nope

Post-meeting notes, July 15, 2021

Notes from Back-End Meeting

1. @Aveline-art Workshop on Github Actions.
2. What are our human resources for issue #1945?
3. How many people do we have to work on a bigger project like Donations? => @abuna1985, @macho-catt, @averdin2
4. Pull requests per week challenge e.g. nums of lines of code, nums of commits, etc.
5. Reach out to Sihem about analytics
6. Look up Github API endpoints to see how many commits have been made => @macho-catt
7. Assign small issues off of the large issue Standardizing the HFLA Design System #1850. Do a meeting to teach new developers how to create issues (aka Workshop)
8. “I do, we do, they do” - @jbubar technique.
9. Who wants to work on [Onboarding Prototype](#1833)? @averdin2 and @jpandh are encouraged to pair program on it.
10. Deploy Wins Page before Danielle leaves.

[averdin2]

I am not going to be able to attend the July 13th meeting, but I want to raise an issue I think needs to be addressed. I recently reviewed PR #1929. The main concern is that this issue deals with making changes to the wins page. It was not made clear in the initial issue that in order to work on the wins page, you should be making a new branch off of wins-feature-1 and not gh-pages, and also be directing the pull request to the wins-feature-1 branch. I want to make sure that we are making this clear with the team and on issues relating to the wins page, and to also let people who are reviewing wins page issues to be looking out for this.

[abuna1985]

Notes from Front-End Meeting July 13, 2021

1. @jbubar announced he would be transitioning to the VRMS team. He would like to spend the next few weeks organizing wins-feature branch. He will provide more information later this week.

2. We discussed @averdin2 comment above

   • @jbubar and @Abel-Zambrano went through all issues tied to the P-Feature: Wins Page label and added comments below:

    IMPORTANT!! 
   This issue is working off of a feature branch!
   Please follow this wiki before creating a new branch!
   [how to work off a feature branch](https://github.com/hackforla/website/wiki/How-to-work-off-of-a-feature-branch)
   

   • After discussing with the dev team and @ExperimentsInHonesty, we determined a GitHub action for a Feature label which will send a message similar to the above.
   • issue for Feature label GitHub action needs to be made.

3. @jbubar wanted to bring up that since we removed merge privilege's, users who want to review pull request lost the command line instructions. The emphasis is that we either provide this information or restore merge privilege to all users (for access to the command line instructions).

   • @Aveline-art added a screenshot of command line instructions with a templatewithin the Pull Request Wiki (within Step 3)
   • We also determined that a GitHub action to add a comment below the pull request with the command line instructions with the info wrapped in [] replaced with the appropriate data:

   git checkout -b [nameOfCollaborator]-[nameOfFromBranch] [nameOfIntoBranch]
   git pull https://github.com/[nameOfCollaborator]/website.git [nameOfFromBranch]
   

   • issue for GitHub action to provide pull request command line instructions needs to be made

4. @Aveline-art wanted to bring up we do not have any documentation on how to create an issue.

   • issue for documentation on how to create an issue needs to be made

5. @abuna1985 and @arghmatey worked with @macho-catt on issue Standardize code for large icon page cards #1887

   • @macho-catt will standardize the card with flexbox
   • @ExperimentsInHonesty wrote a message to @daniellex0 regarding the placement of the CSS since this needs to be accessed by the Join Us and Site Map page

6. @Aveline-art designated @abuna1985 to oversee issue Standardizing the HFLA Design System #1850

7. @arghmatey will begin creating design system website prototype Create the design system pages #1927

[Aveline-art]

Agenda for July 18, 2021

• Insert items here
• @averdin2 There seems to be an issue with the credits page loading alt text for the images
• @averdin2 How should header tags be used
• @jpandh needs assistance completing a pull request for Change Alt Text for Review Icon on Credit page #1583

[alexeysergeev-cm]

Backend Meeting Notes July 15, 2021

• @Aveline-art Workshop on Github Actions.
• What are our human resources for issue #1945?
• How many people do we have to work on a bigger project like Donations? => @abuna1985, @macho-catt, @averdin2
• Pull requests per week challenge e.g. nums of lines of code, nums of commits, etc.
• Reach out to Sihem about analytics
• Look up Github API endpoints to see how many commits have been made => @macho-catt
• Assign small issues off of the large issue Standardizing the HFLA Design System #1850. Do a meeting to teach new developers how to create issues (aka Workshop)
• “I do, we do, they do” - @jbubar technique.
• Who wants to work on Onboarding Prototype? @averdin2 and @jpandh are encouraged to pair program on it.
• Deploy Wins Page before Danielle leaves.

[Aveline-art]

In the meeting July 18, 2021

Issues to be made:

• @Zak234 the alt text is not loading properly, will make an issue
• @arghmatey updating the label wiki Audit Website Team Labels #1983
  • Wiki page for all labels does not exists, but a page for updating issues with status labels does so I created an issue to update that.

Action items:

• The resources list will be mentioned during the engineering CoP @arghmatey