Skip to content

Add dietary requirements + buildup/teardown registration to the volunteer system#1821

Merged
lukegb merged 3 commits intomainfrom
buildup-teardown-reg
Apr 5, 2026
Merged

Add dietary requirements + buildup/teardown registration to the volunteer system#1821
lukegb merged 3 commits intomainfrom
buildup-teardown-reg

Conversation

@lukegb
Copy link
Copy Markdown
Contributor

@lukegb lukegb commented Aug 19, 2025

Dietary requirements

This is bare-minimum - just a plain-text field in the volunteer profile. There's no export yet. @paullessing probably has some requirements here that might be useful for more structured data?

Buildup/teardown registration

There are three entrypoints:

  • /volunteers/buildup/register/ - requires the token, allows populating normal volunteer profile information + special buildup registration info (arrival/departure date, and emergency contact). The 'team name' field from the token is copied onto the buildup registration. Buildup volunteers are required to say they're >=18.
  • /volunteers/buildup - once a buildup registration is made, this allows the volunteer to freely amend their information
  • /volunteers/buildup/arrived/ - this is for an on-site QR code - it registers the volunteer as 'arrived on site', shows them a link to a Signal groupchat (or something else), and reiterates the safety briefing

All of these show the Safety on Site text. Maybe we could put this somewhere else for all except the "arrived on site" page.

@lukegb lukegb force-pushed the buildup-teardown-reg branch 2 times, most recently from 1b76485 to 7925d21 Compare August 19, 2025 10:16
@paullessing
Copy link
Copy Markdown
Contributor

paullessing commented Aug 19, 2025

No specific requirements. I'd hope that the list of people with nonempty requirements is short enough that we can manually process it; adding specific requirements is likely to cause trouble.

The one thing we could do is split dietaries and allergies, and make it clear what we consider the difference to be:

  • Allergies (will cause health issues if ingested): [free text field]
  • Dietary Preferences
    • Vegetarian
    • Vegan
    • Other: [text field]

Let me take this to the team, we have a meeting next week.

@russss
Copy link
Copy Markdown
Member

russss commented Aug 19, 2025

I think we should at least split out vegetarian/vegan options.

Ref #1797, #1746

@paullessing
Copy link
Copy Markdown
Contributor

Discussed with the team. Proposed form:

Allergies (will cause health issues if ingested):

  • Molluscs
  • Eggs
  • Fish
  • ... (total 14 allergens)
  • Other: [free text field]

Dietary Restrictions:

  • Vegan (plant based)
  • Vegetarian (no meat or fish)
  • Other: [free text field]

@lukegb lukegb force-pushed the buildup-teardown-reg branch from 7925d21 to a7d0620 Compare September 8, 2025 22:49
Comment thread apps/volunteer/buildup.py Fixed
@lukegb lukegb force-pushed the buildup-teardown-reg branch 3 times, most recently from 980f77b to 42e8a4d Compare December 17, 2025 01:06
@lukegb lukegb force-pushed the buildup-teardown-reg branch 7 times, most recently from 64213fb to 4114ec5 Compare March 29, 2026 01:35
Copy link
Copy Markdown
Member

@russss russss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll get this merged and then we can build on it

@russss russss enabled auto-merge April 5, 2026 12:38
@lukegb lukegb disabled auto-merge April 5, 2026 14:35
lukegb added 2 commits April 5, 2026 15:44
There's no admin UI for this yet to actually export the aggregate stats
for the kitchen.

Closes #1746.
The general expected flow is this:

* Someone generates a team token in volunteering admin
* URLs make their way into people's hands
* Users sign up - this can be with or without an account via a ticket
* Users enter the information required for a volunteering account, as
  well as their expected arrival/departure date/time, and an emergency
  contact, and ack the Safety on Site briefing
* Once they arrive, they scan a QR code that takes them to the "I'm
  arrived" site - this records their arrival timestamp and gives them a
  link to the Signal group chat and shows them the Safety on Site
  briefing again

Note that, at present:

* There's no way to un-volunteer. You can set your arrival/departure
  dates to just be "normal" times, though, I suppose, and/or never
  actually show up.
* We don't show the team that you're associated with anywhere except
  the admin page, and it's set based on the link you used to register.
* There's no export of this data yet.

Closes #1797.
@lukegb lukegb force-pushed the buildup-teardown-reg branch from 0a82812 to 38ff66c Compare April 5, 2026 14:44
@lukegb lukegb enabled auto-merge April 5, 2026 14:57
@lukegb lukegb added this pull request to the merge queue Apr 5, 2026
Merged via the queue into main with commit 2c9965b Apr 5, 2026
4 checks passed
@lukegb lukegb deleted the buildup-teardown-reg branch April 5, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants