Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the profile creation page to be more inclusive and welcoming #8428

Open
Samuel-Baird opened this issue Oct 18, 2023 · 2 comments
Open
Labels
could-be-quick META: good first issue Small/easy change which is a good introduction to working in the WCA repo TECH: ruby Requires knowledge of Ruby

Comments

@Samuel-Baird
Copy link

Update the information on the profile creation page to make it clear that competitors do not need to use legal names and that they can use nicknames/aliases/preffered names instead.

Related to this dicsussion on making it clear to competitors that they are welcome to use nicknames/aliases/preffered names and not just their legal names.

@sarahstrong314 probably has some great input :)

image

@dunkOnIT dunkOnIT added META: good first issue Small/easy change which is a good introduction to working in the WCA repo TECH: ruby Requires knowledge of Ruby STATUS: blocked Progress cannot continue - reason for block should be specified in comments labels Oct 19, 2023
@dunkOnIT
Copy link
Contributor

dunkOnIT commented Oct 19, 2023

Strongly agree in principle; blocked until the discussion in Update 2c+ is finalized, as there is a lot of important nuance there for people to think through.

@ixyvx
Copy link

ixyvx commented Oct 19, 2023

personally i think that the process of changing name/gender on wca should be similar to changing profile picture, as in you can request a name change by going on your profile, and having the name/gender boxes not grayed out (and being able to edit it) and then having that request sent over to the results team. for first timers i’d say putting something on that page that says “preferred names or nicknames are welcome”, and not saying that they need to use a legal name.

@dunkOnIT dunkOnIT added could-be-quick and removed STATUS: blocked Progress cannot continue - reason for block should be specified in comments labels Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
could-be-quick META: good first issue Small/easy change which is a good introduction to working in the WCA repo TECH: ruby Requires knowledge of Ruby
Projects
Status: No status
Status: No status
Development

No branches or pull requests

3 participants