Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5

...and not always allowing gender-neutral language doesn't cause any problems. That's why this question and all the answers and comments don't exist and everyone is happy. Oh, wait
– Scott Hannen
Commented Nov 19, 2019 at 13:30
But who determines which gender-neutral language should be used and which is not acceptable? Shouldn't that be included in your proposed policy?
– JJJ
Commented Nov 22, 2019 at 21:24
@JJforTransparencyandMonica I don't see why any gender-neutral language should be considered unacceptable. If someone wants to use xe instead of singular they, that's fine.
– eyeballfrog
Commented Nov 22, 2019 at 22:54
@JJforTransparencyandMonica I'm still having trouble envisioning the problem you're suggesting. Offensive language is already disallowed.
– eyeballfrog
Commented Nov 23, 2019 at 1:40
1

@JJforTransparencyandMonica If it's so much of a problem, then singular they can be required as the gender neutral pronoun, but I don't think it will be. Honestly, this proposed policy still works with a vague "be reasonable" standard, because the default of singular they always exists to be used. That is what separates this from the current policy. In the current policy, you must call someone fae if that is what fae claims is faer pronoun, and that's what leaves it open to potential trolling (and the nasty false positives described in the OP).
– eyeballfrog
Commented Nov 23, 2019 at 1:50
@JJforTransparencyandMonica Well I don't disagree with that. But as long as we're going to have a policy about pronouns (and it seems that is foregone at this point), I would think we should have one that's clear and enforceable.
– eyeballfrog
Commented Nov 23, 2019 at 4:07

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »