hackforla
FOLA: Leads/PM Agenda
Overview
This issue tracks the agenda for our weekly meetings
Issue Template
## [ Date ] Meeting Agenda
### Prework to prep for meeting
- [ ] #
### Recurring items: Happens on the Thursday meeting
- [ ] review any issues that are in the [new issue approval column](https://github.com/orgs/hackforla/projects/59/views/1)
- [ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
- [ ] [Robleh](https://github.com/hackforla/food-oasis/issues/assigned/farahrobleh)
- [ ] [Bonnie](https://github.com/hackforla/food-oasis/issues/assigned/experimentsinhonesty)
- [ ] [Sumit](https://github.com/hackforla/food-oasis/issues/assigned/sumit-sharma92)
- [ ] [Muthamil](https://github.com/hackforla/food-oasis/issues/assigned/MuthamilselvanG)
- [ ] [Nate](https://github.com/hackforla/food-oasis/issues/assigned/neom500)
- [ ] [John Darragh](https://github.com/hackforla/food-oasis/issues/assigned/entrotech)
- [ ] [Qiqi Zheng](https://github.com/hackforla/food-oasis/issues/assigned/qiqicodes)
- [ ] [Hannah](https://github.com/hackforla/food-oasis/issues/assigned/hanapotski)
- [ ] [Bryan Wu](https://github.com/hackforla/food-oasis/issues/assigned/fancyham)
- [ ] [Gigi P](https://github.com/hackforla/food-oasis/issues/assigned/GigiUxR)
- [ ] [Shienny](https://github.com/hackforla/food-oasis/issues/assigned/Shienny1)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further (if necessary)
- [ ] Review to see if there are any members to Onboard or Offboard
- [ ] #
### New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
### FYIs
-
### Notes from Meeting
### Task Items
Links to other agenda issues for your team
(so that you can easily post on their agendas items that come up at yours)
- Agenda: FOLA: Design
- Agenda: FOLA: PM Agenda (Google Doc - Deprecated) and FOLA: PM Agenda (GitHub Issue - Current)
- Agenda: FOLA: Leads/PM (Google Doc - Deprecated)
- Agenda: FOLA: UXR
Previous Meetings (link to each comment with the date)
2024-09-26 Meeting Agenda
Prework to prep for meeting
- [x] Ask John where open PRs are supposed to live on the project board. (Reference: https://github.com/orgs/hackforla/projects/59/views/1?filterQuery=is%3Apr)
- [x] Do they still need this column?: https://github.com/orgs/hackforla/projects/59/views/1?filterQuery=status%3A%22In+Development%22
- [ ] add a link to the most recent label check to the agenda
Recurring items: Happens on the Wednesday meeting
- [ ] review any issues that are in the new issue approval column
- [ ] Accountability and Support Check.
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further (if necessary)
- [ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ] BW to JD: what is the dependency on these issues
- [ ] https://github.com/hackforla/food-oasis/issues/535
- [ ] Carry over Items to next meeting that don't get addressed
- [ ] SS to everyone: We need to review these issues in the new issues approval list
- [ ] #376
- [ ] #1631
- [ ] #1908
- [ ] #1939
- [ ] #2068
- [ ] #2072
- [ ] #2116
- [ ] #2117
- [ ] #1725
- [ ] #1638
- [ ] #1661
- [ ] #1675
- [ ] #2166
- [ ] #2172
- [ ] #2187
- [ ] #2188
- [ ] #2189
- [ ] #2201
- [ ] #2211
- [ ] #2218
- [ ] #2221
- [ ] #2226
- [ ] #2227
- [ ] #2228
FYIs
Notes from Meeting
- We'll go to all the PRs in the board and remove them and prevent any from going on the project board in future.
- "ready for dev lead" column is being used right now for any issues that are ready to new worked upon by the devs. Bryan says "In development" column will be helpful in future for the author of bug report/issues to update the status.
- Reviewed all the issues with "ready for dev lead" label to clear the backlog. Below is a summary of work done.
- #2068 BW says: We need to update the approval date filter in the backend before the issue can be worked upon. Priority set to Could have
- #2072 Priority set to "Won't have this time"
- #1908 BW says: it is big lift so getting priority to "Won't have this time"
- #2116 BW says: priority "MUST HAVE"
- #1725 priority "Could Have"
- #2187 priority "Should Have"
- #1939 Dependency on #1725 , moved to icebox
Task Items
Notes from 2024-09-26 meeting
- removed the In Development column
- removed the ready for dev lead label from all closed issues
- prioritized all the issues in the new issue approval column into the ER / Epic ready to be made into issues column
2024-10-03 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Task Items
2024-10-10 Meeting Agenda
Prework to prep for meeting
- [ ] Review reboot effort of Reboot Partnership Engagement (Impact Sprints 2022) milestone https://github.com/hackforla/food-oasis/issues/2241
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Bryan says:
- Sliding effect on the food bank/pantries list should be made slightly less 'notchy' so it would slide more fluidly
Mapbox
- Pull request created to solve the centering of the map which works well and has been deployed to prod.
- Might need to refine more as the pin appears 2/3 way up from the bottom on the map and isn't actually centred
Suggestions:
- Make the map show on 50% on the search/map landing page screen (New issue)
- Hide the survey on prod but should be available on dev till we can recode it in dev (New issue - feature label to be added)
No gps button on the screen - dev issue for that already in place
New mapbox issues discussed:
-
Using the app as a widget when you have a region that represents an NC - John
-
Issues added by Bryan on GitHub
-
Sorted the incomplete issues on GitHub and introduced the milestones to be used for prioritization as per the category. Labels to be used in addition to highlight the time sensitivity.
Task Items
2024-10-17 Meeting Agenda
Prework to prep for meeting
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] Review assignments for each Team member
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard
- [ ] #
New Items
[ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Feasibility questions should be discussed at all team meetings, or can be elevated by the lead to the leads/pm meeting. These questions should be prior documented in a feasibility issue or in the issue where it's being worked on, and a link can put in the feasibility issue. That way we can document the answer and turn that into permanent documentation for the team.
Task Items
Make an issue to have the current location clear the location bar and replace the text with your "current location"
2024-10-24 Meeting Agenda
Prework to prep for meeting
- [x] Current Location Button Fails to Update Location Bar issue has been created.
- [ ] Review the FOLA team roster, validate which members are still active versus inactive.
- [ ] Review https://github.com/hackforla/food-oasis/issues/1409 - get more context on issue/determine if it's really a bug fix.
- From the website team, we have a new issue saying that a new wins form submission has been created, and needs to be reviewed. Review issue https://github.com/hackforla/website/issues/5975
- [x] Review this issue (which has currently been moved to New Issue Approval): https://github.com/hackforla/food-oasis/issues/1128 - seeking clarity on why we need to sync with existing partners?
- [x] Review this issue: https://github.com/hackforla/food-oasis/issues/1131 - what is the current state of the Suggestions page/Suggestions Administration board and modals, and would this be considered expanding on an existing feature, or creating a new one?
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] Review assignments for each Team member
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard
- [ ] #
New Items
[ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Task Items
Items for next agenda
- https://github.com/orgs/hackforla/projects/59/views/2 why do we have a reference column? do we still need?
2024-10-31 Meeting Agenda
Prework to prep for meeting
- [x] Review over-assigned design issues with @fancyham - we should potentially unsassign design team members from specific issues here to prevent overburden. There is one issue in here: https://github.com/hackforla/food-oasis/issues/1544
- [x] Review over-assigned research issues with @GigiUxR - we should potentially unsassign research team members from specific issues here to prevent overburden. There is one issue in here: https://github.com/hackforla/food-oasis/issues/2216
- [x] @MuthamilselvanG has sent out messages on certain dev issues asking for status updates, to better determine active versus inactive team members; review this with @entrotech today.
- [ ] Review https://github.com/orgs/hackforla/projects/59/views/2 why do we have a reference column? do we still need?
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] Review assignments for each Team member
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard
- [ ] #
New Items
[ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Task Items
Items for next agenda
2024-11-07 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ] Ask John about creating column in database (if doesn't exist already) for out of state listings like from Texas, Hawaii or NC - so we can tag the listings from those places.
- [ ] Ask John if database has data for US congress and Senate and state assembly and senate persons and city council persons?
- [ ] https://docs.google.com/spreadsheets/d/1gSkcGyxeN-p06uIWceKpGrCs5YNs8x4tYoP_rA8WkoU/edit?gid=0#gid=0&fvid=1071295059 - The sheet shows about 1300 rows but the website has about 600 listings only
- [ ] Need a volunteer to go through the addresses in the csv file and find out which NC it belongs to
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Task Items
2024-11-14 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ] FOLA:Application User permissions - Process for exporting the user permissions data to a spreadsheet.
- [ ] Diff b/w admin and coordinator roles for volunteers on FOLA:Application
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
- Gigi -> Bonnie: “For now, the most important info is that we plan to have 4 researchers (1 project lead + 3 support ) and the address of the pantry site is 3200 Sawtelle Blvd, Los Angeles, CA 90066. For the meantime would it be possible to move forward with insurance and writeup with this information?”
Notes from Meeting
Task Items
We need to talk about the $5,000 KARST grant, which will expire in a few weeks if we don’t claim it. If we are not going to take it, we need to let them know.
2024-11-21 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
-
[ ] Bonnie -> We need to start adding appropriate labels to the new issues while creating them. - https://github.com/hackforla/food-oasis/issues?q=is%3Aopen+is%3Aissue+label%3A%22Missing%3A+Role%22 - https://github.com/hackforla/food-oasis/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone+label%3A%22Missing%3A+Milestone%22
-
[ ] Carry over Items to next meeting that don't get addressed - Could make this issue an epic and create issues for each step - https://github.com/hackforla/food-oasis/issues/334
-
[ ] We need to talk about the $5,000 KARST grant, which will expire in a few weeks if we don’t claim it. If we are not going to take it, we need to let them know.
FYIs
Notes from Meeting
Task Items
A question about FoodCycle / FOLA integration:
We have received a survey response from a person who is helping Food Cycle explore integration with FOLA website. This person left an email for follow-up: details in a Slack link.
Is anyone on the development team, project managers, leads, already in touch with Food Cycle? Should I try to get in touch with this person? I'd like to hear if they are experiencing any issues with the FOLA widget, and whether they want our pop-up survey to appear in FOLA widget.
PMs, please add to the next meeting agenda:
FoodCycle wants to work with us to add their missing pantries (perhaps what they mean by 'integration').
We need to figure out how to
- Work with them to get this a list of their pantries (probably a John D or PM-led thing), and then
- how to filter their list for duplicates with existing data (possibly our volunteers? - they'd need additional training)
- gather any missing info like 'eligibility requirements', etc. (possibly/likely with our volunteers — they'd need additional training)
@jelenaUX , John has been in touch with someone from Food Cycle about getting these new listings ('integration'), and I suspect that's what the person from the survey from was asking about.
- Talked about the hot-fix that manually added announcement to all pages re: ‘fire and some info may be outdated’. Doesn’t look great on mobile, but works for now.
- Talked about long-term replacement for this and worked through designs and functionality.
- Bryan: Created issue: https://github.com/hackforla/food-oasis/issues/2326 (edited)
Jan 23 2025 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [x] #
New Items
- [ ] Updates on connecting with LA foodcycle — last email was Jan 13 from Nancy Beyda asking for a meeting. Seems like FoodCycle wants to work with us to add their missing pantries (perhaps what they mean by 'integration'). (John leading this effort?
- [x] Updates on UCLA volunteers cohort — who is managing it? : Bonnie and Sumit are partnering on managing the UCLA volunteers
- [ ] Updates on PMs and what they're working on?
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
- Food Cycle Bonnie wrote to John (via emai in the info address) to ask him if he is going to meet with Nancy to discover what she has in mind for foodcycle integration
- We need to add a tool tip to Category in the validation interface, and provide in the tool tip what the difference between food bank and food pantry is. Check to see if there is an issue for the tool tips and if not make one.
- Discussed https://github.com/hackforla/food-oasis/issues/2281
- probably need a freeform field so that we can learn new socials (see task item)
- It was requested by Gigi that we try to change the meeting time since so many pms have rolled off. We also need to do it because it makes it impossible to recruit. We will put out a lettucemeet (see task item)
- we think we should change the closed for covid to closed temporarily (see task item)
- Bonnie and Sumit are co-managing the volunteers (see task items)
- We have a need to be able to search freeform text fields on the site in order to find specific listings. At a minimum we need to be able to do this internally. But it might be helpful for users as well. Examples are:
- someone wrote to us asking for pantries that have a drive in feature (if we could search the notes, we know is at least one listing we validated Fall 2024 that was a drive in and that info got added.
- we will need it if we add the free form other field for socials, so that we can learn about new socials and add fields to the db as needed.
Posted in slack by Shienny
Here are some updates from me:
- BA team : a. Tom and I have been meeting since January 7th. He has been busy with his two jobs and have not made much progress on the dashboard but would like to continue to build the FOLA dashboard. b. Megh Dave still wants to participate but has not attend any meeting this year due to conflict of schedule. ..I am keeping an eye on this. c. I have off-boarded Chenxi Wang today due to no response. d. I would like to recruit 1 data scientist with Google LOOKER skill.
- VERY BASIC Dashboard Mock-up in FIGMA @Bonnie - if you are interested, this is the basic data dashboard I asked the BA team to build first. Please feel free to add your comments/suggestions. https://www.figma.com/design/9hPmNSsyaH2VMGNz5mffmI/FOLA-Design-%232?node-id=640-133&t=wJQgSwVuGOcHXvnK-1
- FOLA Instagram Campaign: @Bryan Wu Per our conversation last week, I have started a quick spreadsheet to plan out the content of our IG Posts. Please feel free to give input/ comments / suggestions. I would like to recruit the ux-designers to help create some graphics for this please. https://docs.google.com/spreadsheets/d/1g9NrYxN00nmQRlSboHHgtF1UKouRG-9J3PeNO9cC8ZA/edit?usp=sharing
Task Items
- [ ] Bonnie/Rabia to handle students
- check their status
- get them to onboard
- once their accounts are set up
- assign them 5 listings
- [x] look for issues related to closed for covid, if there is no issue to change it, create one for product/dev discussion. Add that issue to next leads agenda.
- [ ] look at #2881 and see if we want to expand it, or make a new issue to have a freeform field for other socials, so that we can learn about them and eventually add fields.
- [x] Bonnie/Rabia will make a LettuceMeet to find out peoples availabilities so that we can reorganize the meetings before we start recruiting new pms. Goal, to move the meeting to a time that research can be involved (day time / morning). https://hackforla.slack.com/archives/CMER3R1RD/p1737740584841129
channel if you are currently on the Food Oasis team, please fill this LettuceMeet out with your general availability. It has the dates Feb 1-7, but just treat it as a sample week.
Why we are asking you to do this? We are trying to reschedule our meetings so that all the teams (design, research, dev, pm) could meet at a time that works for everyone currently on the project. Right now, we have some meetings that happen early afternoon, some that happen in the evening, and its making it really hard to recruit new team members as well as accommodate and coordinate across practice areas, because people are generally available in the daytime or night time but not both. This is time sensitive.
Please add this to today's agenda. Please see the rest of this message in our Leads and PM slack channel.
///////////////////////////////////// TIME SENSITIVE //////////////////////////////////
Subject: Prioritizing Data Validation for “No Known Eligibility Requirements” Listings
Please add to agenda (I repeated this message from the Leads and PM slack channel)
@sumit-sharma92 @bonniewolfe
Earlier today I started an analysis of our eligibility data and identified a data consistency issue in our directory related to eligibility information. Currently, eligibility details are intermingled with intake requirements and service notes, leading to inconsistencies in how information is structured and presented.
Key Issues Identified Blurring of Critical Categories:
-
Eligibility (who qualifies) is frequently mixed with intake requirements (what must be provided upon arrival) and service notes (miscellaneous information, e.g., appointment needed).
-
This inconsistency makes it difficult to ensure we fully capture all necessary details for each category, which could lead to incomplete or misleading information for users.
Broad vs. Granular Information:
-
Some listings use general terms like “proof of income,” while others specify exact documents like a W-2 or pay stub.
-
Without standardization, it’s unclear whether “proof of income” means any form of documentation is accepted or if specific documents are required.
-
This inconsistency can result in missing key details, making it harder for users to determine whether they qualify for services.
Proposed Solution: Volunteer Training & Decision Support Tools To improve data accuracy and usability, I propose developing:
A Standardized Checklist for Volunteers
-
A few new slides to educate volunteers on the distinct broad categories and the most frequent eligibility and intake subcategories based on current data trends.
-
It will ensure each category is captured distinctly and guide volunteers on where more specificity is required (e.g., listing exact types of accepted documents under proof of income).
A Decision Tree to Guide Validation Calls
-
A structured decision tree will help volunteers systematically ask the right questions when validating pantry listings.
-
This will ensure we capture missing details, prevent assumptions, and standardize how we collect eligibility and intake data.
Automated Timestamping of Data Entries
- Implementing field-level timestamps would allow us to track when each piece of information was last validated.
- This would improve data quality assurance and help prioritize outdated listings for review.
I can execute on the first two items (standardized checklist and decision tree) and have it ready before Wednesday. The third item will take a bit longer to achieve.
2/6/2025 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] Eligibility validation and checklist that Gigi describes above
-
[ ] Marketing approvals — set up strategy and kick off marketing efforts
-
[ ] Leads meeting reschedule?
-
[ ] Who is usually responsible for managing this meeting’s agenda?
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Task Items
notes john will call nancy or bonnie will email next week gigi needs to redo her hours in the lettucemeet because right now it shows 7:30 pm only on two days https://lettucemeet.com/l/0MNAJ
Wednesday 2pm - time decided for All team meeting starting 25th February
2/20/2025 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] Eligibility validation and checklist that Gigi describes above
-
[ ] Marketing approvals — set up strategy and kick off marketing efforts
-
[ ] Leads meeting reschedule?
-
[ ] Who is usually responsible for managing this meeting’s agenda?
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
- New feature proposal - https://github.com/hackforla/food-oasis/issues/2117
Task Items
- Decide the meeting time starting next week to match other team members' availability
- Focus on Altadena listings validation
Wednesday 2pm - time decided for All team meeting starting 25th February
The 25th is a Tuesday, which is what John and I recall we changed it to, so I’ll update the calendar
I don’t know how to do the zoom meeting link, so let’s use the Google Meet link in the invite
2/25/2025 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] Finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [x] Review Eligibility validation and checklist issues that Gigi that she created:
- Would like to see a diff between previous version and the new edits when volunteers make their updates DRAFT: Implement Field-Level Timestamping for Data Quality Assurance #2349
- Reviewing our database to pull out and come up with an ontology/checklist of required documents / eligibility DRAFT: Standardize Eligibility and Define New Related Fields (Data Taxonomy Standardization) #2346
- [x] "No known Eligibility Requirements" filter omits fields that have "None" in them…
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
- New feature proposal - https://github.com/hackforla/food-oasis/issues/2117
Task Items
- Bryan to get list of text to remove (like 'none', 'no requirements!') from those fields and John will run a batch job to make those fields blank
03/05/2025 Meeting Agenda
Notes from Meeting
-
PM & Issues board John mentioned that the issue board is getting a bit hairy! Bonnie explained that Validation Volunteer management is using up all of our current PM's time. She has solutions for picking back up the momentum by introducing new type of PMs with 20-hour week availability (but likely short-term availability) and a designated student volunteer manager who can dedicate themselves with us as a stakeholder longterm.
-
We want to grow our database with new listings.
- John D is continuing his next steps with LA FoodCycle.
- GigiUxR mentioned Mutual Aid LA' s site for listings. John said that they might be worth exploring as an opportunity for new partner. Bonnie suggested a data science contact (see below in tasks) at Slack that could help us attain listings.
-
Issue #2346
- GigiUxR briefly described first steps to avoid overlap with Bryan's review of eligibility data. (The process is detailed in Slack chat earlier this day.)
- John D suggested as a possible resource an organization focused on standards / taxonomy: https://openreferral.org/
Task Items / Review next meeting
- [ ] Reconfirm next steps regarding Mutual Aid LA, is GigiUxr to contact Sophia Alice, Data Science Slack Channel for scraping code?
- [ ] Bonnie to begin process for bringing in new 20-hr a week PMs
- [ ] Bonnie to post an ad for student volunteer program manager
- [ ] GigiUxR to access https://openreferral.org/
- [ ] GigiUxR to bring UxR dashboard sheet next meeting so Bonnie can help integrate the dashboard into a github alternative.
- [ ] GigiUxR to finish discussing interactive onboarding example for student volunteers.
2025-03-11 Meeting Agenda
Prework to prep for meeting
- [ ] #
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed
FYIs
Notes from Meeting
Task Items
Notes:
- Summit availability
- Student status
- Bonnie to begin process for bringing in new 20-hr a week PMs
- one more week on the process and I will know if we can get pms that way
- Design: Brian added open role, and it's posted to the open roles board #2369
Labels we need mapped to the labels we have (all made)
- p-feature: Search by Address
- p-feature: search results - p-feature: search
- p-feature: Filters - N/A
- p-feature: Map - p-feature: Map
- p-feature: List - N/A
- Interface: Food Seeker - N/A
- Interface: Admin Dashboard - p-feature: Admin Dashboard
Notes:
Nate (Won't be able to attend today's meeting but here are a list of open (didn't comb through closed issues) issues I wasn't sure if they fall as a Food Seeker issue, Admin Dashboard issue, or both):
- #2344 (backend but linked to both food seeker/admin views
- #2339 (same as 2344)
- #2313
- #2252
- #2251
- #2172
Would like to discuss:
- want to add text tags to Eligibility Requirements field like “serves-veterans”, “serves-under-18” — to call out populations a location explicitly says they serve. Similar text-tags for requirements; also,
- split Eligibility Requirements field into two separate fields: Eligibility, and Requirements
Also, is it just me? Using this issue for hundreds of comments is really balky in my browser, making it hard to add or edit.
04/22/2025 Meeting Agenda
Prework to prep for meeting
Recurring items: Happens on the Thursday meeting
-
[ ] review any issues that are in the new issue approval column
-
[ ] Accountability and Support Check.
-
[ ] finish adding labels to the issue that are still missing them (see audit links above)
-
[ ] review issues with [epic label] and define how to break down further (if necessary)
-
[ ] Review to see if there are any members to Onboard or Offboard - [ ] #
New Items
- [ ] Carry over Items to next meeting that don't get addressed
- [ ] Onboarding is happening on 2025-04-28 and currently here are the open roles. If you want more people, please make new open role issues
FYIs
- https://github.com/hackforla/fola-geog-482-582/issues/18
Notes from Meeting
- Update on the project with the student
- Student is still working on reviewing the LA County list for the bus data set.
- He knows Python script
- Discussing separate design - development issues
- https://github.com/hackforla/food-oasis/issues/1115
- When the design issue is done, there should be an action item to hand-off for dev
- Devs can finish the action items
- Make a note in the design issue that it's been handed off the dev
- Development Handoff Issue as a template, Example template from TDM
- FOLA Design team can try the Dev Handoff Issue
- QA process, launching labels
- when dev issue gets completed, then a front-end QA label will get added, so that it can be reviewed
- if you do have a PR that does need changes, then we can just make a Bug Issue, Example Template from TDM
- Discussing design of the buttons
- No strong recommendations from Bonnie, can make changes in the design (lowercase/uppercase of text, "…")
- Bryan says: Younger folks don't like … and ALL CAPS because of what they mean in text chats (pending/typing and shouting)
- Discrepancies in Developer version and Public LA (outdated) version of the Style Sampler Sheet
- Example: Gray section in Dev ver, doesn't exist in the public ver
- public LA version is outdated
- Bryan : after the meeting, I created #2421 to add all UI element styles to the sampler page
- Ingrid will reach out to John about the designs of the buttons and discuss the discrepancies
-
TWE Design System Figma and TWE Microsite Ready for Dev pages Figma
- Design System is in process of being built
- Idea is that developers can see the CSS for every state
- Bryan brought up that pulling CSS from actual website as a source of truth could be more helpful than using Figma as the source of truth
- Figma can be easy to lose track of what's change
