Remove heteronormativity from coding style doc#436
Merged
adrianholovaty merged 1 commit intodjango:masterfrom Oct 15, 2012
ddbeck:patch-1
Merged
Remove heteronormativity from coding style doc#436adrianholovaty merged 1 commit intodjango:masterfrom ddbeck:patch-1
adrianholovaty merged 1 commit intodjango:masterfrom
ddbeck:patch-1
Conversation
adrianholovaty
added a commit
that referenced
this pull request
Oct 15, 2012
Removed heteronormativity from coding style doc
Member
|
Thanks, @ddbeck -- good call. |
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
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.
I'm proposing replacing the gender example with a non-gendered example in the Coding style doc. The example as written makes an exclusionary implication about gender identification which might be off-putting to potential contributors who do not identify as male or female. Moreover, choices in collecting gender data is often considerably more complicated than demonstrated. A trivial coding style example is probably more clear in this case, in that it demonstrates the style, rather than substance, of expected code.