Skip to content

Make the speaker demographic questions a per-event setting - #1304

Merged
amatsuda merged 2 commits into
rubycentral:mainfrom
amatsuda:optional_demographics
Nov 19, 2026
Merged

amatsuda merged 2 commits into
rubycentral:mainfrom
amatsuda:optional_demographics

Conversation

@amatsuda

Copy link
Copy Markdown
Collaborator

Summary

The optional age, pronouns, ethnicity and first-time speaker questions on the proposal form were asked for every event. Forks that do not want to collect such information (RubyKaigi carries two revert commits for this) can now switch them off per event instead.

  • New Event#speaker_demographics boolean, toggled by a "Speaker demographics" checkbox on the event form next to "Blind review", and shown on the event Info page.
  • When off, the questions are left off the proposal form, the answers are dropped from the permitted params, and previously stored answers are hidden on the speaker's proposal page and the staff speaker page.
  • Migration backfills existing events to on, so deployed events are unchanged. New events start with it off, as blind review does.
  • Also removes leftovers of the long-gone user-level demographic columns: the gender/ethnicity/country permits in the profile and admin user controllers, and the orphan ethnicities factory.

Test plan

  • New specs: model flag, admin create with the box checked/unchecked, organizer turning it off, proposal form and page in both modes, request spec confirming answers are ignored when off, staff speaker page in both modes
  • Full suite green locally

🤖 Generated with Claude Code

amatsuda and others added 2 commits November 19, 2026 16:05
The optional age, pronouns, ethnicity and first-time speaker questions on
the proposal form used to be asked for every event, and forks that do not
want to collect such information had to carry revert commits removing the
feature. Event#speaker_demographics now switches them on or off from the
event form, next to blind review.

When the flag is off the questions disappear from the proposal form, the
answers are dropped from the permitted params, and nothing stored earlier
is shown on the speaker's proposal page or the staff speaker page.

Existing events keep asking the questions; new events start with them off.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
The users table lost its gender, ethnicity and country columns long ago,
yet the profile and admin user controllers still permitted them, and a
factory remained for an Ethnicity model that no longer exists.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@amatsuda
amatsuda merged commit 5ebd687 into rubycentral:main Nov 19, 2026
2 checks passed
@amatsuda
amatsuda deleted the optional_demographics branch November 19, 2026 07:22
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.

1 participant