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

Gender should be optional/allow other values #44

Closed
abeyer opened this issue Jun 6, 2017 · 10 comments · Fixed by #115
Closed

Gender should be optional/allow other values #44

abeyer opened this issue Jun 6, 2017 · 10 comments · Fixed by #115

Comments

@abeyer
Copy link

abeyer commented Jun 6, 2017

The gender field seems to be required on records wherever it is present, and only has male/female choices. This forces me to enter bad data where I don't know someone's gender or they identify as some other gender.

Ideally it would be nice to allow other values and 'unknown', but at a minimum making that field optional would at least avoid forcing the user to include known bad data.

(Given the subject matter, I really hope this doesn't become a flamewar...please feel free to lock/delete if it is in danger of doing so. And for the record, and perhaps in hope of averting that, I'll say that this is an actual issue that came up for me when trying the app with online contacts where I don't even know their gender for certain, and some friends who specifically identify as some non-binary option, not an "improve the world with social justice issue.")

@ocdtrekkie
Copy link

Related to #25 and #36 and now #43

@shockey
Copy link

shockey commented Jun 6, 2017

+1. I think we can avoid making this a political discussion - the fact is, I have friends with preferences re: their gender, and I'd like to have a place to document that.

@sergiotapia
Copy link

+1 - three options should be enough though.

  • Male
  • Female
  • Unknown (this can be a text field for people to just type in whatever they want)

@djaiss
Copy link
Member

djaiss commented Jun 7, 2017

I think that we should have 4 values actually

  • male
  • female
  • other/textfield
  • nothing (they can skip it entirely)

@sergiotapia
Copy link

So if they don't select anything they just have a nil value in the database. Having a separate input for "None" seems redundant.

@djaiss
Copy link
Member

djaiss commented Jun 7, 2017

@sergiotapia actually no, because these are radio buttons. If you choose one value by mistake, the only way out would be to use "other", and perhaps you don't even want "other" as being a gender?

@sergiotapia
Copy link

I think
Male (radio)
Female (radio)
Other (radio) on click shows a text input.

Why should there be another radio button called None?

@SuperDoxin
Copy link

@sergiotapia Because you can't unselect radiobuttons, so without one there is no way to select none. In any case it's entirely possible to know people without being aware of their gender, so having a none option would be nice.

@djaiss
Copy link
Member

djaiss commented Jun 7, 2017

I think we can do the simplest thing and do as follow:

  • Rather not say (by default)
  • Male
  • Female

I'm going to open a PR for this small change.

It's more complex to add an other field and this can be done later in the future.

djaiss added a commit that referenced this issue Jun 7, 2017
People have complained that they want to add more genders than Male/Female. It makes sense. The quick workaround for this is to add a rather not say choice everywhere we mention the gender for people, which would be selected by default. In the future we'll be able to add more genders if needed.

This change requires migration.

Fix #44
@github-actions
Copy link

This issue has been automatically locked since there
has not been any recent activity after it was closed.
Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants