Repository navigation
docs(admin): explain RSVP close-time and waiting-list behaviour - #3011
Merged
Merged
Conversation
The RSVP Timing hint still said "Leave blank to handle manually", which was only true before RSVPs started closing on their own 3.5 hours before a workshop (codebar#2901). Organisers now read what actually happens behind two collapsed sections on the workshop form: what stops at the close time, what still moves between close and the 3.5-hour freeze, and how dates pre-fill when the start time changes. The admin invitation management page gets a note that removing an attendee offers their seat to the top waiting-list member until the workshop starts, and that the close times do not limit the page.
mroderick
force-pushed
the
docs/rsvp-cutoff-behaviour
branch
from
October 12, 2026 12:10
17d6a7e to
955bba0
Compare
mroderick
marked this pull request as ready for review
October 12, 2026 12:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation of the RSVP behaviours, so organisers will know what to expect. 1st iteration, we an improve on this later.
Summary
Organiser-facing explanation of the RSVP cut-off behaviour introduced by #2901, #2997, #3003 and #3010, placed where the decisions are made. The old hint still said "Leave blank to handle manually", which the default close time made untrue.
The workshop form's RSVP Timing card keeps a one-line version and adds two collapsed sections: what stops at the close time (new RSVPs, waiting-list joins and leaves) and what still moves between the close time and the 3.5-hour freeze (member cancellations, waiting-list promotions, declined members parked on the security list), plus a section on how the date and time fields pre-fill when the start time changes.
The admin invitation-management page gains a note that removing an attendee offers their seat to the top waiting-list member for the same role while the workshop has not started, and that the RSVP close times do not limit the page.
Text-only: two HAML view files and locale strings. Member-facing pages are unchanged.
Review notes
rsvp_freezes_at(start minus 3.5 hours), waiting-list joins and leaves stop at the earlier ofrsvp_closes_atand the freeze (waitlist_closes_at), andpromote_nextskips declined and accepted invitations.