[Backend] Feed an RSVP of "no" into the session at-risk evaluation #525
Loading…
Reference in a new issue
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?
Follow-up from #370 (v4.3.0 phase 4), deliberately left out of that change because it alters when the at-risk Discord pings fire.
availability_service.evaluate_session_at_riskcounts explicit time-slot votes only. With web RSVP in place, a confirmed session now carriessession_attendance.rsvp_status(yes | maybe | no, NULL = no answer) for every member, which is a better attendance signal than a slot vote cast weeks earlier: a party where three of five have answered "no" is at risk even if the slot vote was unanimous.Proposal: treat
rsvp_status = "no"as a declared absence and"maybe"as half-weight (or as unanswered; decide and document), so the at-risk warning reflects what people said most recently. Keep the existing threshold semantics and the campaign'sreminder_offsets_minutes; add tests for a session that is at risk only because of RSVPs and one that stops being at risk once RSVPs come in.