Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Special case around community fridges #380

Open
mveytsman opened this issue May 28, 2024 · 0 comments
Open

Special case around community fridges #380

mveytsman opened this issue May 28, 2024 · 0 comments

Comments

@mveytsman
Copy link
Member

From Michelle:

Last year, i asked people's preference and then tried to assign people based on that + how much capacity the fridges can handle - like we can send a couple small/medium riders to one fridge but unless it's brock, we don't want to end up with a couple trailers to one fridge?

Suggestion from @chadmohr

One easy way to achieve some of the needs would be to exclude market/fridge runs from the automated riders needed CTA on the Home screen. That way tasks could be added for all fridges without messing up the widget.


I think the underlying issue here is that our model is based on delivering discrete items (e.g. food hampers) to addresses, with each address geting a fixed amount (usually one). Community Fridges is different in that we're fanning out a big load of groceries to the fridges. In practice we will sometimes even decide who goes to what fridge on site.

In some sense it's more about total rider capacity needed - which chad's suggestion is about - we want to be able to fill a roster with riders and not specifgy specific fridges exactly.

See also #379 which is related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant