HfLA: PM/ORG/UX Meeting Agenda of 2022

[Sihemgourou]

Dependency

When we have a new research lead

Overview

This issue tracks the agendas and notes for the meeting that PM has with UI/UX

Template:

## 2022-MM-DD Agenda and Notes 

### Prework to prep for meeting
Review and prepare items that have [ready for research lead](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22ready+for+research+lead%22#column-15235217) labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agenda.


### Recurring items: 
 - [ ] review any issues that are in the new issue approval column
   - [ ] [Research](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+user+research%22#column-15235217)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Lead and Org rep
       - [ ] [Isaac](https://github.com/hackforla/website/issues/assigned/IsaacDesigns)
       - [ ] [Bonnie](https://github.com/hackforla/website/issues/assigned/ExperimentsInHonesty)
       - [ ] [Simone](https://github.com/hackforla/website/issues/assigned/sacamp)


### New Items


### Notes from meeting
- 
### Tasks


### Items for next meeting agenda

Participants :

Things to discuss:

Things discussed:

Actions to take:

Weekly Agenda

21/06/20
21/06/21
21/06/22
21/06/23
21/06/24
21/06/28
21/06/29
21/06/30
21/07/06
21/07/07
21/07/09
21/07/13
21/07/14
21/07/15
21/07/20
21/07/21
21/08/02
21/08/03
21/08/05
21/08/09
21/08/11
21/08/17
21/08/24

fill in the rest

2021/12/08
2021/12/15
22/01/08

[Sihemgourou]

Meeting 21/06/20

Participants : @ExperimentsInHonesty & @Sihemgourou

Done:

• Assigned feature labels to issues with feature missing + created new labels
• Cleaned the project board
• Made some comments about the Getting started page Develop Updated Getting Started page #1619
• @Sihemgourou has now access to the google analytics account Google Analytics #1730
• @Sihemgourou has been made owner of the HFLA Github so that she can edit the website write team
• Talked about the program areas page (@Sihemgourou has to contact Ali for the SDG issue)
• Created ALL TEAM agendas for the Sundays meetings
• Talked about a new way of organizing the ALL TEAM (time keeping + how to talk the issues)
• @ExperimentsInHonesty showed @Sihemgourou how to clean an old issue (how to hide comments)
• Checked if people were assigned to multiple issues
• Checked if Danielle was still assigned on issues

Todo:

• Talk with @akibrhast about the winssubmissions issue template (it shoud appear as any other template so we can edit it) => Done: Its not possible to have the issue template because the issue is made from the google app script. He will made variables on the script so that we can update the labels. The process would be to create an issue for the devs in order to update it.
• Ask the other pms if they want to join on the 1v1 with @Sihemgourou & @ExperimentsInHonesty => Done : see slack
• Review the design to development hand-of (Creating a file in gdrive to stock the figma images?)
• Finish cleaning the board by adding features on the Icebox
• Prioritized the issues on the prioritized backlog
• Create a roll call spreadshit ? (HfLA: ALL TEAM Meeting Agenda☀️ #1734)

[Sihemgourou]

Meeting 21/06/21

Participants : @akibrhast & @Sihemgourou

Things discussed:

• Wins page :
  • The github pitcures are not showing on the page. There is a bug.
  • Should we remove the question about getting the github pitcure and take it directly ? Because we are already showing all the contributors pitcures on the project profile cards (see akib comment in PR toggle see more/see less on wins card #1732)
  • Should we have the linkedin & github icons in all the cards and just gray the buttons when we don"t have the info

Actions to take:

• Ask Bonnie why the Member Feature page has the same objectives as the wins page.
• Ask Bonnie about the things discussed with Akib about the wins page
• Adding descriptions to the newly created labels => gdoc with list of all the labels + add caracters limits and run it through the pm team
• Talk with Bonnie about this issue Research on the Wins submission process #1789
• Should we remove the question about getting the github pitcure and take it directly ? Because we are already showing all the contributors pitcures on the project profile cards (see akib comment in PR toggle see more/see less on wins card #1732) => we wanted to ask which image they prefer

[Sihemgourou]

Meeting 21/06/22

Participants : @Sihemgourou & @ExperimentsInHonesty & @daniellex0

Things discussed:

Home page :

• We want to test the design with people who do not know us (people with a donator profil would be ideal)
  Getting started page :
• Discussed about the suggestions in this comment. (All checked boxes are changes are validated changes)

Actions to take:

• @Sihemgourou will rewrite the description text on the top of the Getting started page so that it can be more adapted to volunteers. Something like "Volunteers..." / Done : see comment
• @ExperimentsInHonesty has to check the wiki for tomorrow's meeting
• Ask @ExperimentsInHonesty about the zoom faq in the getting started page
• Write a template message to ask potential donators if they want to do a user test, and publish it in HFLA slack so that volunteers can spread it through their networks.

[Sihemgourou]

Meeting 21/06/23

Participants : @Sihemgourou & @ExperimentsInHonesty @sayalikotkar

Things discussed:

• VRMS: David from the VRMS team, is working on something that will affect the jobs team, he's building a CMS for people to update their meeting time and any infos that the projects hold on the website.
• Wins page:
• Getting started page => "Start your Hack for LA volunteer journey"
• Wiki : Changes proposed to the side bar
• Home page : The UX research should be a more general analysis (user interview), ask questions as what are you looking for on project website in order to donate and then make a usability testing. The user interview should be made by all the UX CoP. We should test it with the fund raising team first.
• Onboarding automation

Actions to take:

• @Sihemgourou will connect with David to know more about the features his project would have => Done: The VRMS team is not actively working on what needs to be displayed on the website. Maybe they could internalise the updating process on their interface but this should come up with V.05.
• @Sihemgourou will present another alternative which will be more compatible with the design
• Review the home page research strategy with @DanielekPark
• Talk about the github picture permission on the sunday meeting
• Write a template message to ask potential donators if they want to do a user test, and publish it in HFLA slack so that volunteers can spread it through their networks.
• Talk with Bonnie about this issue Notify Win's submitter Research on the Wins submission process #1789
• Ask Bonnie why the Member Feature page has the same objectives as the wins page
• Review the design to development hand-of (Creating a file in gdrive to stock the figma images?) => Done: @sayalikotkar is going to ask devs about what needs to be checked before handing the issues from design to dev.
• Finish cleaning the board by adding features on the Icebox
• Prioritized the issues on the prioritized backlog

[Sihemgourou]

Meeting 21/06/23

Participants : @Sihemgourou & @daniellex0

Things discussed:
Getting started:

• @daniellex0 said: It's ok if the header is not standardized because this page is unique + the other pages are not standardized either
• Ashley will come back with more ideas about the headers
• We have to write hypothesis about the flows to analyze on GA

Home page research:

• Why do we want to involve the UX Cop? Who are the person involved in the fund raising team?

Actions to take:

• @Sihemgourou will connect with Rosalyn to documents the UR strategy (waiting @DanielekPark approval first)

[Sihemgourou]

Meeting 21/06/24

Participants : @Sihemgourou & @ExperimentsInHonesty @sayalikotkar

Things discussed:

Actions to take:

• Talk with the devs about the amount of front end good second issues
• Make 3 bugs issues about the project cards bugs
• Do a serie of test of the mobile version of the website (design). @Sihemgourou need to make an issue with a list of all the pages connected to the menu (use this all the other links are secondary. If things are not right, the design team should edit the issue with how it should look like. For that, @Sihemgourou needs to create a template issue so that designers could use it. Process: put the issue in the review column to see if the devs would need additional details on the issue. All the page which are not live are here

[Sihemgourou]

Meeting 21/06/28

Participants : @Sihemgourou & @ExperimentsInHonesty

Things discussed:

• https://github.com/hackforla/.github where to put issue template to spread to all other project repository
• hidden issues on the board https://github.com/hackforla/website/issues?q=is%3Aissue+is%3Aopen+no%3Aproject => we are going to try a manual process (asking people if they need help putting it in the repo) and maybe automate it ?

Actions to take:

• Make an audit about everything that is in figma and be ready to be developped

• All team : talk about people taking two issues at the same time

• Onboarding/contributing md is too big ?

• @Sihemgourou will put [this issue ](Updating the HfLA Website Team Meeting Roster Discussion: HfLA website/other projects Team Meeting Roster #1343) on the ice box and put a date on it.

• All team : how to create a note to cite an issue for the dev team meeting

• issue 1445 : the issue should be self explanatory

• @Sihemgourou will gather the status on every page of the website on the sitemap for tomorrow's meeting. and if there are issues assigned to it

• @Sihemgourou assign those issue to the right labels