1
2
Fork
You've already forked treehouse
1

Allow for seating size changes and no take out #248

Open
opened 2025年06月06日 16:12:45 +02:00 by rhogue · 2 comments

Hi Etienne,

One request is to allow the seating size to change. It should default to 22 as is, but if, for example someone wanted a smaller meal and only cook for 10, we wanted a way to manually change the seating size.

Related to that, we also wanted a way to say 0 for takeout - or to set a limit to the number of takeout - again, for the use case where someone wants to create a small dinner, they want to cook for 10 people and have one sitting. They don't want to have to cook any additional servings, so take out should not be permitted.

thanks
Becky

Hi Etienne, One request is to allow the seating size to change. It should default to 22 as is, but if, for example someone wanted a smaller meal and only cook for 10, we wanted a way to manually change the seating size. Related to that, we also wanted a way to say 0 for takeout - or to set a limit to the number of takeout - again, for the use case where someone wants to create a small dinner, they want to cook for 10 people and have one sitting. They don't want to have to cook any additional servings, so take out should not be permitted. thanks Becky
Author
Copy link

Tagging this again - wondering if we can move this one up the priority list ... there are people that would like to host smaller dinners - like dinners for 10 - but would like to open them up to community signup randomness rather than specific meals.

Tagging this again - wondering if we can move this one up the priority list ... there are people that would like to host smaller dinners - like dinners for 10 - but would like to open them up to community signup randomness rather than specific meals.

Hey Becky - so I made a change yesterday: you can now create a meal with a maximum number of attendees (per seating) that can go from 10 to 100.

I'd like to share a couple of concerns: I don't know how I'm feeling with the idea of creating a meal with 10 people max and have the system to send an email to everybody. This feels like a competition: "the 10 fastest people get to eat". Should a private meal then be organized over email rather than via the internal website.

Also, reimbursement of a 10-people private meal would still go through me for reimbursement. I'm ok to organize the reimbursement of community meals, but cash should be managed by the organizer of a small private meal, not me.

What do you think? Maybe we should talk in person about it.

Hey Becky - so I made a change yesterday: you can now create a meal with a maximum number of attendees (per seating) that can go from 10 to 100. I'd like to share a couple of concerns: I don't know how I'm feeling with the idea of creating a meal with 10 people max and have the system to send an email to everybody. This feels like a competition: "the 10 fastest people get to eat". Should a private meal then be organized over email rather than via the internal website. Also, reimbursement of a 10-people private meal would still go through me for reimbursement. I'm ok to organize the reimbursement of community meals, but cash should be managed by the organizer of a small private meal, not me. What do you think? Maybe we should talk in person about it.
Sign in to join this conversation.
No Branch/Tag specified
main
review-meal
concert-mailing-list
email-community-fund
add-remove-from-funds
ledger
clean-up-reminder-email
no-take-out
delete-booking
free-night
open-concerts
more-concert-2
concert-admin
car-share-whitelist
more-concert
more-car-admin
concert
meal-setting-clean-up
car-share-admin
car-payment-fund
fix-car-fund-relationship
documentation
new-farmer
add-library-item
croppie
simplify-meal-system
implement-meal-role
team-members-in-db
settigs-class
library-v1
various-fixes
seating-size
tool-library-6
meal-associations
kamal
extract-tve-meals-features
dev_setup_script
checkout-checklist
tve-controller
split-admin-controller
tve-override
scottd-dev-setup
195-meal-team-members
leftovers
sqlite-dev
multiple-seatings-1
multiple-seatings-2
google-api
portion-name-desc
data-integrity
upgrade-ruby
gem-upgrade
finish-car-booking-payment
car-booking-payments
admin-meal-payments
meal_payments
eggs-page
description-for-transfers
area-booking-max-limit
upgrade-ch-area
areas-part-3
add-remove-money-admin
manage-rooms
last-details-around-meal
close-meal-service
refine-transfers
eb-household-and-attendees
add-fund-email
meal-sign-up
add-state-to-payments
meal-screens
add-children
meal-models
66-transaction-table
66-create-tabs-for-funds
66-create-fund
add-bookings-to-car-page
note-for-car-bookings
car-owner
open-car-sharing
update-room-booking
room-booking-to-use-dates
collapse-cars
prepare-car-booking
charging-color
a-round-of-refactor
ajax-for-car-booking
fix-car-booking
add-columns-to-car-and-booking
car-sharing-algorithm
ajax-calls
reorganize-secrets
create-car-booking
master
car-calendar-color
book-a-car
remove-user
update-packages
fix-booking-confirmation
open-marketplace
pricing-options
add-cron-for-emails
19-ten-day-booking
19-some-rules-for-booking
feedback-from-becky
19-emails-and-guest-room-admin
19-pay-by-night
19-create-payments
19-ten-days-credit
19-household-name-logic
19-room-booking-confirmations
19-create-households
19-guest-room-admin
19-users-roles-table
marketplace-search
add-tests
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
etienne/treehouse#248
Reference in a new issue
etienne/treehouse
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?