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.
-
3SE is not a social network, you shouldn't try to get to know anyone imo because that generally generates a lot of noise not related to the Q&A (except perhaps in chat).– Erik ACommented Oct 11, 2019 at 10:45
-
1@eric_a fair call you are totally right, but you get my point– undefinedCommented Oct 11, 2019 at 10:49
-
5@ErikA "SE is not a social network" You have some good (basic) point here. I'd recommend to add: "Don't take critiques about your posted content personal, but concentrate about improving the content,"– πάντα ῥεῖCommented Oct 11, 2019 at 10:49
-
@πάνταῥεῖ that capture the sentiment as colloquially as possible?– undefinedCommented Oct 11, 2019 at 11:01
-
@LukeMcGregor Yeah, at least adding that point was a good idea.– πάντα ῥεῖCommented Oct 11, 2019 at 11:03
-
This does not answer the question "why are the code of conduct changes received so negatively".– RaedwaldCommented Oct 11, 2019 at 11:03
-
totally agree, its one of the common offences– undefinedCommented Oct 11, 2019 at 11:03
-
2@Raedwald this is what I was answering: What are the (main) reasons that the current changes are received so negatively? And how could/should Stack Exchange improve to make sure such major changes are received better in the future– undefinedCommented Oct 11, 2019 at 11:05
-
2@Raedwald - I think this answers the question well. The gist of the answer is, "Because we would have preferred a lighter, more flexible CoC instead of one that seems so agenda-driven."– J.R. means 'Just Reinstate'Commented Oct 11, 2019 at 11:06
-
2I guess overall what im trying to say is I want a CoC that's going to do a couple of things, put people at ease. Set them on the right footing for conflict, and tell them we expect respect. I remember way back this was how it was, and I think it fostered a much healthier community.– undefinedCommented Oct 11, 2019 at 11:08
-
2I think lighthearted is really important too, you don't want a heavy handed CoC that turns common sense into a list of taboos– undefinedCommented Oct 11, 2019 at 11:10
-
5This doesn't even mention bigotry, but does manage to state that "other ideas" / "offensive things" should be tolerated multiple times. It's pretty clear that such a CoC would open the doors for antisemitic, racist, sexist, trans- and homophobic commentary if it is just phrased nicely enough / not "deliberate". At non-technical sites we already have enough problems handling the bigotry without a CoC that explicitly says that it should be tolerated.– timCommented Oct 11, 2019 at 13:02
-
2@Tim If we are going to get on we all need to accept that sometimes that's going to mean letting it go when what we believe conflicts with what someone else does. What we need to avoid is people deliberately trying to hurt each other or do damage to people who are different. We cannot prevent people getting offended in a diverse community (and we shouldn't try). Preventing offence is synonymous with reducing diversity.– undefinedCommented Oct 11, 2019 at 13:20
-
4@LukeMcGregor That's not my experience. I've seen plenty of disparaging comments about eg Jews or black people at eg politics.SE, and even with the CoC as-is, handling of them has at times been less than ideal. If we reduce the CoC to not being "unpleasant to each other", it gives us even less power to have negative comments about groups of people removed (because it can be countered with 'it's not mean to a specific user and according to the CoC you should just tolerate my ideas/values').– timCommented Oct 11, 2019 at 13:51
-
1It's excessive to require people to be compassionate. It's great if they are, but you can't require it - especially from those people who have to deal with the flood of close-worthy newbie questions. So -1.– einpoklumCommented Oct 11, 2019 at 14:10
|
Show 3 more comments
How to Edit
- 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
How to Format
-
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>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you