Repository navigation
0.13.0
·
161 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Added
- Away until: skip calls while you're gone (#196). Wherever a call takes answers (the call message, your Your answer card, the reminder, App Home, and the call's page), Away until… asks for the day you're back, and you're away from that call's day until then. Or set the first and last day ahead of time under Away on Preferences. Calls on those days answer you Out, marked "away until Oct 25" on the roster: the call post doesn't mention you, you get no reminder, nobody waits on you, and the call can still close early, as FR-56 says. An answer you gave already stays, and you can still tap In, or join late, on any call; that holds for that call only. Your card, Home, the call's page, and Preferences say "Away until Sun, Oct 25" with I'm back (or Clear, before it starts), which ends it and asks you again on calls still taking answers. An admin can set or clear a member's from Admin > Members > Preferences.
- Admins can see and change a member's preferences (#181). On Admin > Members, select Preferences on a member's row, or open the member and select their preferences. The page is the member's own Preferences page, with a banner that says whose it is: I can usually, reminders, dietary needs, fun mode, and every tag and item level. Each change is saved as the member's and audited with the admin as the actor and the member as the target:
member.preference_set(with the level before and after),member.settings_updated,member.needs_updated, andmember.fun_mode_set. A save of settings, dietary needs, or fun mode that changes nothing writes no audit row. The member isn't messaged, and their sign-in and sessions don't change. A member's own changes on Preferences stay unaudited, except dietary needs, which are audited asguest.needs_updated, as before. Guests have no Preferences page; an admin still changes a guest's dietary needs on their row in Guests. Preferences now says "Only you and the household's admins can see these." - Takeout gets an orderer and a pickup person (#178). A pickup meal now has two roles, Order and Pickup, and delivery keeps one, Order. By default they go to different people: the first person who offered to pick up picks it up, and the first other person with I'll order on for the call orders. Someone who usually orders but turned I'll order off isn't picked, though they would be for delivery. If nobody else has it on, the person picking up orders too, so someone who offered to pick up is still all a pickup needs. The coordinator or an admin can give one person every role. Someone who offers a pickup meal does both. The decision, App Home, role messages, and call-off messages name both roles, and Order online shows on a pickup too.
- Choose pickup or delivery during the vote (#178). While voting, the coordinator, a guest coordinator, or an admin can make a takeout proposal pickup or delivery when its place allows both: ⋯ beside it on the proposals message, or Pickup and Delivery on the call page. A proposal whose way was chosen says "(chosen)". Audited as
event.way_set. - The coordinator can move the decision time (#198). While voting, the coordinator, a guest coordinator too, can make voting close 15 or 30 minutes later, or 15 minutes earlier: Move the decision time on the call page, or in the ⋯ menu on the call message. It has the same limits as an admin's move, and the "Vote by" time updates everywhere. A time that has already passed closes voting at once, as Decide now does; a guest coordinator can't do that. An admin can use it in Slack too. Audited as
event.deadline_moved, as an admin's move is, with who moved it and as what. Neither can move a time that has already passed, before the scheduler closes it. - Reset the ranking to its defaults (#177). Admin > Ranking now has Reset to defaults below the form. Open it and select Reset ranking to put every setting on the page back to what a new household starts with: the weights, Randomness, Feedback, the number of proposals, the variety window, and the time to choose roles. Call times, skipped days, and badge counts stay as they are. A reset is audited as
household.ranking_reset. A household that upgraded to 0.11.0 has Feedback at 0 unless an admin changed it, so a reset turns ratings on. - History is more compact (#177). On a wide screen, each meal's buttons now sit in a column beside its details instead of below them. On a phone, they stay below the details but share a row where they fit, with Edit and Delete always side by side. A meal's cuisines share a line with its name, and History's buttons are now 44 pixels tall, so they're easier to tap.
- Dinnerbone's bowl and bell sit out on the floor (#177). In fun mode, the food bowl and the dinner bell over it now stand about a third of the way across the den, away from his bed of straw, instead of at the bed's edge. He still eats, nibbles, and waits at the bowl, the bell still rings over it, and he potters, and rests between laps, on the floor between the bowl and his wheel.
- Stats shows what's new, with dates (#177). On the Yours tab, Newly earned now lists the badges you earned in the last three days instead of the last two weeks. On the Household tab, Lately earned is now Newly earned, like the Yours tab, and each badge in it shows the day it was earned, in the household's time zone, beside who earned it.
Changed
- Checkboxes on Preferences are all the same size (#177). Under I can usually and Reminders, a long label no longer shrinks its checkbox, and each box lines up with the first line of its label. Fun mode is now a Show Dinnerbone's Den checkbox, like the page's other on and off settings, instead of On and Off buttons. The same checkbox fix applies wherever the app has a checkbox row, such as Schedule and the Catalog.
- Schedule sections are shorter (#177). On a screen 576 pixels wide or wider, such as a tablet or a computer, each meal's Time to answer, Time to vote, and Reminder before answers close now share one row, so a meal's section is about a quarter shorter. On a phone, they stay stacked one above the other.
- Your usual settings start your offers on (#180). Your usual offers turn on once per call, the first time you count as In, however that happens; after that the call's offers are yours. Tapping In, saving Details before you answer, claiming or being given coordinating, and joining late turn on I can cook, I can pick up, and I'll order to match Cook, Pick up, and Order on Preferences. Offering a role, or making an offer that joins the call as a pick, counts you in with only that role. Turn any offer off for that call, and it stays off: answering In again, coming back In after Out, and a refreshed card don't turn it back on. Maybe and Out turn nothing on, and an item's cook list still decides who can cook it. Preferences says so in place of "this doesn't volunteer you", and Order delivery is now Order, on Preferences and on Admin > Members.
- Today says what Start a call and Make an offer do (#177). Both stay folded, and each now has a line under its name: a call asks the household who's in and what to eat, then everyone votes on it; an offer says what you're already making or getting, so others can join. A form whose post fails opens on its error, as before. The Set up the household card at the bottom of Today is gone, because Admin and Schedule are in the menu.
- Voting picks a coordinator when nobody claimed it (#179). When answers close and the call goes on to voting with nobody coordinating, Dinnerbell picks one of the members who said In at random: never a guest, and never someone who was still a maybe. The call message and roster name them, and they get a direct message saying they were picked and what they can do: Lock this, break a tie, and shuffle the picks while voting, and once it's decided, change how you get it and who does it. They're a coordinator like any other. When the decision leaves the role unclear, they get the usual Assign roles message and the household's time to choose, 15 minutes by default and never past the meal time, before the first volunteer, if there is one, does it. They earn coordinating credit, and its badges, when the meal is done, as if they'd claimed it. They can hand it off like any coordinator, and someone can still claim it before voting starts. With no member in, nobody coordinates, as before. The pick is reproducible from the call and its run, happens once a run, and is audited as
event.coordinator_pickedand logged ascoordinator_picked. - Admins can break a tie, shuffle, and switch late joiners at any time (#179). While voting, any admin can now tap Break the tie, Shuffle proposals, or a late joiner's Taking part and Vote counts, alongside the coordinator. Before, an admin could only when nobody coordinated or a guest did. A guest coordinator still can't do these. The refusals now say "Only the coordinator or an admin can ...".
- Ordering counts on a pickup (#178). The person who orders a pickup meal now earns an Order Up count for it, apart from the pickup count. If the coordinator switches a pickup to delivery, whoever was picking up is dropped and gets no pickup count. Pickup meals done before the upgrade keep the counts they had. An admin's correction after the meal moves each role's count on its own (#162).
- The decision asks the coordinator about takeout (#178). When the winning proposal is takeout at a place that allows pickup and delivery and nobody chose its way (Dinnerbell drew it, and nobody set it during the vote), or when a role has no clear owner, the coordinator gets Assign roles right away, with the household's time to choose. For a pickup, ordering has no clear owner when more than one person besides the one picking up has I'll order on. A proposal someone added, or an offer, keeps the way they chose. If the coordinator doesn't choose in time, the proposal stays the way it is, and the first people who offered do the roles.
- Assign roles and Adjust choose who orders and who picks up (#178). In Slack and on the web, Who does it is now Who cooks or Who orders, and a place that allows pickup adds Who picks up. Switching between pickup and delivery keeps whoever orders. On the web, Change the time or who does what lists only the roles the meal's way has.
- Voting keeps its decision time when answers close early (#193). When everyone has answered, or the coordinator or an admin selects Start the vote now, voting opens at once as before, but it now closes at the call's usual decision time: the response deadline before the close plus the slot's Time to vote. Before, voting closed Time to vote after the early close, so the call decided sooner. Members can vote for several picks, so they get the whole time to look at them. Everyone voting doesn't end it either. Only the coordinator or an admin ends voting sooner, with Decide now, Lock this, or Break the tie, and an admin can still move the vote deadline. An admin's shorter answer deadline that lands in the past keeps the decision time too, while one still ahead moves the decision time as much. A late call too late to decide on its day at that time, because its meal would round up to midnight, gets Time to vote from the close, as before. The Start the vote now confirmation says voting still closes at the usual time.
- A maybe counts as an answer when two are in (#193). With two or more in, responses close early once every member has answered In, Maybe, or Out. Before, one Maybe kept them open until the deadline. Closing early turns maybes out, as the deadline does, and because they answered on time, a maybe who then joins late has a vote that counts, and the join-late prompts in Slack and on the web say so. With fewer than two in, a Maybe still keeps answers open until the deadline, because they might make it two: only outs end a call early. When everyone is out, the call ends on-your-own at once, and a lone In still gets 10 quiet minutes to add a guest.
Removed
- The Set up the household card on Today (#177). Its Manage members and Schedule buttons repeated the menu's Admin and Schedule links, which show at every screen width.
Fixed
- Upgrade and restart steps work with secrets in files (#193). Documentation only. The upgrade, rollback, and restart commands left out
-f compose.yaml -f compose.secrets.yaml, so an install that keeps its secrets in files started without them and restarted in a loop. The docs now say to pass both-foptions to every production compose command, and to add-f compose.override.yamllast if you have one, because compose stops reading it on its own once you pass-f. "Run compose with secret files" indocs/setup.mdexplains, and troubleshooting has a row for the restart loop. - A card's refresh keeps what you haven't saved (#193). A call or offer card refreshes every 45 seconds. When you ticked dietary needs in an offer's Count me in form and then waited, the refresh put the boxes back as they were, because it skipped a card only while you typed in one of its fields. Now a card also skips its refresh while a field in a form that's showing differs from what was saved: a ticked or cleared box, a changed number, or another choice in a list. Once you save, put the field back, or close the form, the card refreshes again, and a closed form's changes are discarded, as before. Cards also no longer bring back values you typed and didn't save when you go Back to the page.
- A refused tap clears "Not saved" (#193). When a tap on a card failed and the next tap on that card was refused because the call had moved on (a 409), the card showed its current state and the reason, but the page's "Not saved" banner stayed until that card next saved or refreshed. A card with nothing left to refresh, such as a finished call, kept it until a reload. A refused tap now clears it, as a saved one does.
- A card that can't refresh stops trying (#193). A page left open refreshed each open call's card every 45 seconds, even when the refresh failed. A card the server no longer shows you (a 403 or 404, such as a guest who was removed or a call that's gone) now stops refreshing until a tap swaps in a new one. When refreshing fails for another reason, such as no network, a slow answer, or a server error, the page waits twice as long before each next try, up to 10 minutes. It goes back to every 45 seconds, catching up at once if a refresh is overdue, as soon as a refresh or a tap saves, or the device reports it's back online. An expired session still sends the page to sign in.
- A call posted early is decided on its day (#193). When everyone answered a call posted before its day, such as tomorrow's lunch posted the evening before, voting opened and the call was decided that evening. Now voting still opens at once, and it closes at that day's decision time. On the call message, the picks message, and the event page, its vote deadline names the day, such as "Vote by 12:00 PM on Friday, Oct 23." A call with fewer than two in still ends at once.
- A badge taken back leaves its waiting post (#193). When an admin's correction after the meal takes back a badge that was already queued for the channel and not posted yet, the post now leaves it out, and a post with no badge left isn't sent. A monthly recap waiting to go out leaves it out too. Before, the post still announced it. A post Slack already has stays, as before.
- Two Slack replies show their links (#193).
/dinnerbell logwith an empty catalog, and Make member for a guest whose email Slack doesn't share, showed their link as text, such as<https://…|the catalog>. Both now show a link to the catalog or the Members page. Text that people typed is still escaped. - Guests without Slack no longer earn badges (#201). Since #102, an unregistered guest, one with no Slack account whom the inviting member answers for, earned badges for cooking, picking up, ordering, and coordinating, though they can't see or manage them. Now only members and registered guests earn badges. An unregistered guest's contributions still count toward the household's totals and the monthly recap, and no badge post, recap, or Newly earned list names them. When an admin links them to Slack or promotes them, they get the badges their contributions reach, quietly, as a catch-up does. Unlinking a guest from Slack takes no badge away.
- A retired feature flag no longer stops startup (#193). A flag is removed one release after it turns on, and Dinnerbell refused to start when
DINNERBELL_FEATURESstill named it. Now it starts, ignores the flag, and logs one warning that names it, so you can take it out of.env. A name that was never a flag still stops startup, so a typo fails as before. - Slack shutdown starts no badge art upload (#193). When Slack refused a badge file while Dinnerbell was shutting down, it could start uploading the badge art again after the shutdown had stopped the uploads, and that work outlived the shutdown. Now nothing starts once the Slack connection is stopping.
- Documentation only: The sign-in rate limit in
docs/configuration.mdexplains that, under rootless podman, every client behind your proxy shares one sign-in rate limit, 20 requests a minute to/auth/, and whyDINNERBELL_TRUSTED_PROXIEScan't safely fix that there (#193). Troubleshooting has a row for "Too many sign-in attempts". - CI only: the
publishjob now waits for thecomposejob too, so a brokencompose.yaml, install bundle, systemd unit, or configuration check stops a publish (#193). Before, a release tag could push itsX.Y.Zimage, which can't be replaced, while its bundle failed.release-bundleneeds onlypublishnow. - Tests only: the badge art tests stop each Slack connection and each picture still being made before the test's database closes (#193, #93).
Upgrade notes
- Secret files: if you keep secrets in files with
compose.secrets.yaml, name it in every compose command, including the upgrade:podman compose -f compose.yaml -f compose.secrets.yaml pullandup -d, with-f compose.override.yamllast if you have one. Without it, Dinnerbell starts without its secrets and restarts over and over. See "Upgrade" in docs/setup.md. - Calls voting during the upgrade with nobody coordinating: Dinnerbell picks a coordinator only when answers close, so such a call decides as a call with nobody coordinating did in 0.12.0. An admin can still assign someone who's in.
- Calls that close early vote longer: after the upgrade, a call whose answers close early, because everyone answered or someone selected Start the vote now, votes until its usual decision time instead of Time to vote from the close, and a Maybe no longer keeps answers open once two are in. A call that's already voting during the upgrade keeps the vote deadline it has. To end voting sooner, the coordinator or an admin selects Decide now.
- Calls posted early that are voting during the upgrade: a call posted the day before whose answers already closed early keeps the vote deadline it got, that evening, so it decides that evening. To have it decide on its day instead, an admin re-runs it: it opens again with that day's deadlines, and answers close early again only once everyone answers this run.
- Offers: revision
0025_usual_offers_doneadds a column to call answers on the first start, and marks every answer already saved as having had its usual offers, so no saved answer changes and none gains an offer later. Members who haven't answered an open call yet get their usual offers when they answer In. To go back to 0.12.0, restore the backup you made before upgrading. - Proposals: revision
0026_proposal_mode_chosenaddsproposal.mode_chosenon the first start: on for every proposal a member added or an offer made, off for every drawn one. A call that's voting during the upgrade and decides on a takeout place that allows pickup and delivery asks its coordinator to choose the way. - Away: revision
0027_awayaddsmember.away_first,member.away_last, andresponse.away_untilon the first start, all empty, so nobody is away and no saved answer changes. To go back, restore the backup you made before upgrading. - Badges of guests without Slack: revision
0028_unregistered_guest_badgesdeletes, on the first start, every badge awarded to a guest with no Slack account, with no post or message. This includes a guest unlinked from Slack, or linked to a member, before the upgrade. Their contributions stay, so household totals and recaps don't change, and a badge post or recap still waiting to go out leaves them out. To go back, restore the backup you made before upgrading: the downgrade can't bring the badges back. - Calls decided before the upgrade: a pickup decided before the upgrade has a pickup person and no orderer. The coordinator can add one with Adjust or on the web, and the meal counts as it is when it's done. A pickup whose roles were waiting for the coordinator gets both roles when the time runs out.
- Adjust modals open during the upgrade: saving one changes the meal time and the coordinator as before. Changing who does the role on a pickup asks you to open Adjust again.
Image
ghcr.io/dsmorgan/dinnerbell:0.13.0@sha256:b42c2421995e8d84c94a56bb29a4c136a6d64249e7e5fecb810b60b615a8892f