Repository navigation
Dinnerbell 0.11.0
Added
-
Ratings move your own score (#18, FR-55, ADR 0008). When you rate a meal, your score for that place or recipe moves toward your rating, from −2 for Hated it to +2 for Loved it: halfway, or three-quarters of the way for Hated it and Didn't like it. The change halves every 3 months, counts only on calls you eat at, and never vetoes anything. Logged meals count. Setting a score on Preferences, even back to 0, replaces your earlier ratings of it. Preferences shows you, and only you, what your ratings make your score, such as "From your ratings: about +1".
-
A hint for each place, from the whole household. Once two people have rated a place, everyone sees Well liked, Mixed reviews, or Not well liked, without names, and recent ratings count more. The most important problem checked in the last 3 months adds to it, as in "Mixed reviews · recently late", or shows alone, as in "Recently cold". The hint is the first reason on a drawn pick, on the web and in Slack, and shows on the catalog. Words written for Other are never shown.
-
Feedback on the Ranking tab of Members: how far each rating pulls a person's score, 0 (off), 1, or 2. A new household starts at 2. Hints show at every setting.
-
Adjust the plan in Slack (#149). Once a call is decided, the coordinator taps Adjust on the decision message, their App Home card, or the message saying a guest with a role left, and one modal changes the meal time, who cooks, picks up, or orders (someone who's in), and who coordinates. It saves only what they changed from what the modal showed, so a change made elsewhere meanwhile, such as with Assign roles, is never written back, and hands off last. A refusal, such as a meal time before the decision, shows next to its field without saving anything; if a later part is refused after an earlier one saved, the reply says which. Everyone sees Adjust on the decision message; anyone but the coordinator who taps it is told why not, an admin included. Someone the coordinator assigned is told they can ask the coordinator to pick someone else with Adjust.
-
Adjust switches how you get it (#154). When the decided place allows more than one way, the coordinator's Adjust modal has How (cook, pickup, or delivery), and its Who does it field assigns that person the chosen way, as Assign roles does: switching pickup to delivery with Alex selected makes Alex the one who orders, and they're told. Someone who can't do it that way, such as someone off a home meal's cook list, is refused next to the field. On the web, the coordinator's Assign roles form already switches the way at any time until the meal is done.
-
Coordinating, a page for the household: what a coordinator is, how you become one, what you can do while answering, voting, and after the decision, in Slack and on the web, what an admin can do beyond that, and what happens when nobody coordinates or someone drops out. The README links it, with the other household guides.
-
Stuck calls show on
/healthzand Admin (#142). A call whose next scheduler step has been due for more than an hour, because the step keeps failing, is stuck./healthzreports how many asstuck_callsand sets"status": "degraded"with HTTP 200, so the container health check doesn't restart Dinnerbell, which can't fix the step. The scheduler checks once per tick, so/healthzruns no extra queries. A banner on every Admin tab lists each stuck call with its meal, day, state, and how long it has been stuck, and links to the call, where you call it off (or re-run it, for a voting or decided call). A call that can't be checked counts as stuck, for an unknown time. A step that fell due while Dinnerbell was down counts from the start, so a call that catches up after a restart isn't stuck. -
Optional: start at boot on podman (#135). Rootless podman has no daemon, so after a reboot Dinnerbell stayed down until someone ran
podman-compose up -d.deploy/dinnerbell.serviceanddeploy/dinnerbell-test.serviceare systemd user units that runpodman-compose up -danddeploy/dinnerbell-test up -dat boot and stop them at shutdown. They're in the install bundle, and "Start at boot" in docs/setup.md installs them. Rootful Docker needs neither: its daemon restarts the container. At shutdown they runstop, so the containers and their logs survive a reboot, and whenupexits with an error, they try again 30 seconds later, a few times. On systemd older than 244, such as RHEL 8, addRestart=noin a drop-in. CI checks both units withsystemd-analyze verify.dinnerbell initmentions them in one optional line at the end. -
History and the Catalog come in pages (#153). History shows 20 meals a page, still grouped by week, and the Catalog 20 matches a page, with Newer and Older (or Previous and Next) around "Page 2 of 5". The Catalog's page links keep your search and filters, so a page's address is a bookmark. A page past either end shows the nearest page. Logging, editing, or deleting a meal, giving feedback on it, and adding or editing a catalog item return to the page that lists it.
-
Stats has two tabs (#153), like Admin's: Yours, with your badges and counts, and Household, at
/stats/household, with the household's totals and newest badges. Badge posts and the monthly recap in Slack link Household; App Home's Stats link stays on Yours. Guests see only their own badges, as before, and a guest who opens Household lands on them. -
Documentation only: "Switch between a clone and the bundle" in docs/setup.md moves an install from a git clone to the release bundle, or back, keeping both instances' data volumes,
.env,.env.test,secrets/,secrets-test/, andcompose.override.yaml. It replaces 0.10.0's upgrade note, which said to copysecrets/: your account can't read the secret files, so they have to be moved. -
Fun mode: Dinnerbone's Den (#153, FR-62). Dinnerbone, the hamster in the logo, now lives in a den beside your greeting on Today: a bed of straw with his bowl and the dinner bell, and his wheel. He follows the next open call. While answers are open, he runs laps around the call's card; while it's voting, he runs in his wheel; once it's decided, he eats at his bowl; once it's done, he sleeps in the straw. He walks between them as the call changes, without a reload. With no call, he follows the clock: a nibble at breakfast, pottering about at lunch, a doze in the afternoon, waiting at his bowl at dinner, and asleep late at night, unless a call keeps him up. The den's light follows the household's time of day, and the season's weather falls in the den and down the page's edges, with snow, leaves, or a puddle that grow as the season goes on; he shakes the snow off his wheel before it turns. Tap him and he hops and a heart pops. Celebrations: tap Lock this on Today and the bell rings and he sprints to his bowl ("Pad thai it is!"); tap Mark done and he pats his belly and waddles to bed; earn a badge and he backflips the next time you open Today, once. Everyone else gets a quiet caption, with no animation, and so does everyone when a call is decided by the vote or in Slack. With reduced motion, he holds still and celebrations are a caption. It never makes a sound. A long name shrinks the greeting to fit beside him, then wraps. It's on by default: members turn it off with Fun mode on Preferences, and guests on their dietary-needs page, and only you change yours. With it off, pages load none of it and are exactly as before.
Changed
- Layout fixes, mostly for phones (#153). Card titles on Schedule (Dinner, Lunch, Breakfast) and on Admin's Ranking and Badges tabs sit inside their cards instead of on the border, and those cards have room between fields. The navigation's links take two even rows on a phone instead of a ragged second row. Taps are easier: the logo, every + heading that opens a section, the tabs, the tag names on Tags, a call's title, and the catalog's meal and tag chips are at least 44 pixels tall to tap. On History, How was it? no longer touches the line above it.
- Whoever coordinates is in (#154). Tapping I'll coordinate changes your answer to In if you said Out or Maybe or hadn't answered, and so does being handed coordinating or assigned it by an admin. During the vote, you join late, as I'm in (late) does, but your vote counts, as a coordinator's always did; a late joiner who takes it on gets a counting vote too. A guest who coordinates is in but never late, so their dietary needs keep filtering the proposals. Someone a hand-off or an admin put in this way gets a direct message saying so. Saying Out ends your coordinating, as does being switched off as a late joiner, still being a maybe when answers close, or being deactivated by an admin: nobody coordinates, the call's messages say so, and anyone can tap I'll coordinate. Once a call is decided, only someone who's in can be handed coordinating or assigned it. A late joiner the coordinator switched off can't claim it, be handed it, or be assigned it. Each release is audited as
event.coordinator_released. The Home reply says "You're in, and coordinating dinner." - Someone assigned after a hand-off is told whom to ask (#154). When one Adjust both assigns a role and hands off coordinating, the assignee's message says to tell the coordinator, who can pick someone else with Adjust, instead of the one who just handed off.
- Whoever loses a role is told (#154). When the coordinator or an admin gives your cooking, pickup, or ordering to someone else before the meal time, you get "Sam changed the plan for dinner on Thursday, Oct 22: you're no longer picking up." From the meal time on, a change corrects the record of who did what, and messages nobody, the new assignee included.
- Adjust never writes over a change saved meanwhile (#154). Each part of an Adjust, the meal time, the role, and the hand-off, checks again as it saves that it's still what the modal showed, so a change saved on the web between pressing Save and the save itself is refused with "The plan changed since you opened this. Open Adjust again." instead of being overwritten.
- Documentation only: the spec (FR-10, FR-17, FR-58, FR-61, and sections 4, 5.7, and 10) and
docs/channels.mddescribe coordinating as built (#154), including that the coordinator corrects who did what after the meal until it's marked done, which is what contributions count. - Admin overrides are web-only, as built (#149). Spec 5.7 and
docs/channels.mdsaid an admin could assign the coordinator, move a window, re-run a call, skip a day, and correct an assignment from Slack; those are on the web app only. They now say so, and list what an admin can do in Slack: lock a pick, assign roles, and, with nobody coordinating, break a tie, shuffle, and switch late joiners. - The catalog shows each item's hint in place of how many loved it (FR-49). The hint names nobody; nothing else about anyone's rating or issues is shown.
- The issue checkboxes are in order of importance: Wrong order, Late, Cold, then Other, on the web and in Slack. The hint picks the first one checked in that order.
- Feedback is one rating per meal (#18). Instead of rating the food and, for a restaurant, the place, each member gives the meal one rating: Hated it, Didn't like it, It was fine, Liked it, or Loved it. Every meal takes a rating, home or restaurant, and it stays optional (No answer). The issue chips (Wrong order, Late, Cold, Other) stay for restaurants, and Other gets a box to say what went wrong, up to 200 characters; typing in it checks Other. Only the member who wrote the text sees it, as with their rating and chips.
- "Proposals" everywhere (#149). Slack and the web call the places up for a vote proposals, as the web's Proposals heading did: the channel post is titled "Dinner proposals · Tuesday, Oct 27", Add proposal opens Add a proposal, the coordinator's button is Shuffle proposals, App Home links "See the proposals and vote in the channel", and the web's form adds with Add (or Join late and add), as Slack's does, instead of Propose. Messages and refusals that said "pick" say "proposal", such as "Pho Place is already a proposal (delivery). Vote for it instead." and "(already proposed)" beside a catalog item. "Pick up", the role, keeps its name.
- In, Maybe, Out reads the same everywhere (#149). The web now orders answers In, Maybe, Out, as Slack does, and shows them as one joined control on a row of their own, with your choice filled and checked, above the role offers, which turn on and off one by one. A guest's answers on the web get the same control. In Slack, the response reminder puts In, Maybe, and Out in a row of their own, apart from View on web, as the Your answer card and App Home already do. The web and Slack draw their button and confirmation words from one list (
domain/labels.py): the web's roster says Can cook, Can pick up, and Can order instead of Cooks, Picks up, and Orders, which read like assignments; the buttons for a guest you answer for say Can cook, Can pick up, and Can order on both the web and your Slack card; Break the tie and Details have the same name on both; and Lock this, Break the tie, Shuffle proposals, Mark done, and Close now ask the same question on both. - App Home follows the call past the answers (#149). While voting, Home still doesn't vote, but the call's card says which proposals you voted for, or that you haven't, and links the proposals post in the channel. With nobody coordinating, it offers I'll coordinate, and so does the web, as the call message already did. Once it's decided, the card names the meal time ("The plan: Sam's Tacos at 6:45 PM") and your own role ("You're picking up."). Home's link row adds Stats and Schedule, whether or not badge art is uploaded, and its call cards say View on web instead of Open.
- Slack messages carry the buttons they talk about (#149). The response reminder has the role offers and I'll coordinate from your Your answer card, below In, Maybe, and Out; a tap edits the reminder, as an answer does. A guest's invitation gets the role offers too. The "you're counted out" message after a maybe has the I'm in (late) button it mentions, and goes out only when the call goes on to voting: when it ends for too few people, the on-your-own post covers it. A called-off call's message, and the message to whoever started an unposted call someone else called off, have Start dinner again (or lunch, or breakfast), for any member until the usual meal time plus two hours. The response and feedback reminders end with a link to your preferences, where you turn reminders off. Badge posts and the monthly recap link the Stats page.
- One name per link (#149). Every link to an event's page says View on web, including the role-vacated message's (was Pick someone) and the call-off and on-your-own posts' (was "Open the call on the web"). Links to the Schedule page say Schedule on the web (was Change the schedule and "See the schedule"), and to the Stats page Stats on the web. Home's badges no longer have their own "All badges on the web" link; the link row has Stats.
- An offer's buttons each do one thing (#149). The offer message in the channel shows Can't make it whenever the offer is open, not only once it's full, and Count me in only joins: tapping it again no longer drops you out. A new −1 guest takes back a guest you added with +1 guest, in the channel and on Home, as lowering the number does on the web. The four sit in a row of their own above the item links, View on web, and Call it off.
/dinnerbell cancelcalls off your offer too (#149). Without a slot, it finds today's only open call you may call off, or your own open offer; an admin names the slot to call off someone else's offer. With a slot that has no open call you may call off, it calls off the offer there, such as yours on a day whose call you can't call off. When you may call off more than one offer in a slot, it asks you to use Call it off on the one you mean. The command's hint in the Slack manifest listsschedule, and its description mentions offering and logging.- Skip a day is on the Schedule page, and the admin menu is named Admin (#149). Admins skip a day's call in a Skip a day section at the bottom of the Schedule page, beside the schedule it skips, instead of on the Ranking tab; it posts to the same address and writes the same audit row, and a bookmarked
/admin/schedule?notice=skippedgoes to the Schedule page. The navigation link to the admin pages says Admin instead of Members; its tabs are still Members, Ranking, and Badges. - Documentation only: spec section 11 no longer lists the time zone and backup status on the Admin page, which never had them (#149). The time zone is
DINNERBELL_TIMEZONE, read on first start, and the last backup's time is in/healthz. The setup and troubleshooting guides say Admin > Members where they said Members. could not advance calllogs at most once an hour per call. The scheduler logs a call's first failure at once, then once an hour while the step keeps failing, instead of every 30 seconds. Each line has the traceback, the event ID, the failingstep, andfailures, the number of failures since the previous line.- CI only: the
imagejob tags its local buildghcr.io/dsmorgan/dinnerbell:ciinstead ofdinnerbell:ci. Grype's alert fingerprint includes the image name, so a base-image finding had one Code scanning alert from the CI build and another from the published image; now each finding has one alert (#141). The image itself is unchanged, and nothing new is pushed. - Documentation only:
SECURITY.mdlinks straight to the private vulnerability report form and the latest release, and says what to include in a report (#141). - Documentation only: shorter, easier-to-scan user docs (#137).
docs/setup.mdkeeps the first install, going live, backups, upgrades, and the optional setup, at about a third of its length. Rarer material moved to new pages:docs/test-instance.md,docs/configuration.md(every setting, loading a catalog on first start, resource and log limits),docs/troubleshooting.md(problems and fixes,/healthz, the logs),docs/members.md(guests and joining from the channel),docs/switch-install.md(clone and bundle, building from source), anddocs/badge-internals.md(award states, backfills, and badge art, for maintainers). Copying a catalog between instances is indocs/catalog-format.md, and the no-secret-on-a-command-line check is indocs/hardening.md. Every old link intodocs/setup.mdstill works.deploy/dinnerbell-test --helplists what the script checks and refuses, and its messages, the test boot unit,.env.test.example, and the test manifest point to the new pages. The Schedule page's hint for admins names the Ranking tab instead of "Admin > Ranking", which the app had no menu for. - Documentation only: the README drops its milestone Status section, and the spec's roadmap lists milestones in build order: M7 feedback-informed ranking before 1.0, then M6 assistant, then M5 calendar hints. 1.0 ships once daily changes settle down (#19).
- Documentation only: the README's "How a dinner works" diagram is a simple top-to-bottom flow that follows a takeout night, instead of a sequence diagram, and the steps under it use plainer words (#155).
- Documentation only: the README opens with how a dinner works, with a plain-language diagram of a day: the 3:00 PM call, the vote, the decision, and the 6:30 PM dinner (#136).
Upgrade notes
- Feedback: revision
0020_one_ratingconverts the feedback members already gave, on the first start. It scores each old answer (loved it +2, fine 0, not again −2) and gives the meal a rating from that score; when someone rated both the food and the place, it uses the average. So food loved it becomes Loved it, food loved it with place fine becomes Liked it, and food fine with place not again becomes Didn't like it. Issue chips, thank-yous, and notes to the cook stay as they were. To go back to 0.10.0, restore the backup you took before the upgrade. - Ratings and ranking: revision
0021_feedback_rankingsets Feedback to 0 for your household on the first start, so ratings don't move anyone's score yet, and the household hints show at once. It also records when each member last set a score for each place, so a score set before the upgrade still wins over earlier ratings. When you're ready to let ratings move scores, set Feedback to 2 on the Ranking tab of Members. The loved counts on the catalog are gone; the hints replace them. - Fun mode: revision
0022_fun_modeadds the fun mode setting, on for every member and guest, and0023_fun_seen_awardrecords each member's newest badge so far, so the den doesn't backflip for badges earned before the upgrade. Both run on the first start. To go back to 0.10.0, restore the backup you took before the upgrade. /healthzhas a new key,stuck_calls: a number, ornullwhen the check failed or is more than 90 seconds old (the call tick hung while the heartbeat goes on). Eithernullcase also reportsdegraded. No database revision ships for this.- Monitoring: the documented monitors don't alert on
degraded, which keeps HTTP 200. To be alerted about stuck calls, and about Slack, the outbox, and backups, replace the"slack":"connected"keyword monitor with one for"status":"ok","version"(see "Monitor it" in docs/hardening.md). - Start at boot: nothing to do; an install without the unit runs as before.
- Coordinating: nothing to do. Calls already under way keep their coordinator, even one who isn't in; the new rule applies from their next change. An Adjust modal open across the upgrade still saves, without How.
- Slack (optional): the
/dinnerbellcommand's hint and description changed indeploy/slack-app-manifest.yaml(and the test manifest). Slack shows the old ones until you paste the new manifest into your app's App Manifest page; everything works either way. No new scopes or events. Offer and call messages already in the channel get their new buttons the next time they change. - History bookmarks: History's
?page=used to count 8-week windows from 0; it now counts 20-meal pages from 1. An old/history?page=Nbookmark opens a different set of meals, and?page=0opens the newest page.
Image
ghcr.io/dsmorgan/dinnerbell:0.11.0@sha256:a9e932acb04df07c3b72b5d2f9798c08ab51ce3aef8dfde4d64d69261ba32ea3
Install bundle
dinnerbell-0.11.0.tar.gz and its .sha256 are attached and attested. See docs/install.md.