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.
-
111Exactly. It was just this sort of haste that caused the last, um, little hiccup.Andrew Leach– Andrew Leach2019-10-06 21:50:32 +00:00Commented Oct 6, 2019 at 21:50
-
3Presumably the implementation date will be somewhat after the 10th, and as the pseudo-MIT licensing fiasco showed, they can react quickly to objections by delaying the implementation.Mark– Mark2019-10-06 21:51:22 +00:00Commented Oct 6, 2019 at 21:51
-
2Indeed. The CoC was not the actual problem, the underlying issue has been afoot for years. Afaict, management ought to think about what they can do to make SO employees successful again.Uphill Luge– Uphill Luge2019-10-06 21:54:49 +00:00Commented Oct 6, 2019 at 21:54
-
93I don't understand the rush, either. Sara Chipps posted her infamous "apology" in the TL for the moderators there to see it ahead of time, but for some reason only waited 6 minutes before posting it for the public. If she'd waited a little longer for feedback maybe it wouldn't have been quite such a disaster.Null– Null2019-10-07 01:54:11 +00:00Commented Oct 7, 2019 at 1:54
-
58That was my immediate reaction as well. The timing suggests moderator input is a formality, not a genuine attempt to integrate feedback. And the fact that this is the only actual action in the post makes the whole post seem like appeasement rather than genuine apology.T.J. Crowder– T.J. Crowder2019-10-07 07:19:08 +00:00Commented Oct 7, 2019 at 7:19
-
TL;DR I'm stayingJean-François Fabre– Jean-François Fabre2019-10-07 12:32:05 +00:00Commented Oct 7, 2019 at 12:32
-
Sonic the PRHog Says: "Gotta post fast!"Justin Time - Reinstate Monica– Justin Time - Reinstate Monica2019-10-07 18:04:09 +00:00Commented Oct 7, 2019 at 18:04
-
14The obvious answer is that there will be no changes to the CoC. It will be posted to meta for people to feel involved but nobody will care about the responses. It's been made clear before that the contents of the CoC are not up for discussion in any way.sth– sth2019-10-07 18:35:15 +00:00Commented Oct 7, 2019 at 18:35
-
Agreed. Danger of too fast. And were the people from communities supposedly protected by these new CoCs who volunteered to work with SO (for example during the annual survey when asked if would help SO going forwards) engaged with? I haven't seen mention of this but haven't scanned all the traffic on this subject.user371773– user3717732019-10-07 20:23:55 +00:00Commented Oct 7, 2019 at 20:23
-
1@Null Fully agree, though the word disaster is a understatement - that poorly phrased 'apology' was rather a infernal cataclysm..iLuvLogix– iLuvLogix2019-10-08 12:28:49 +00:00Commented Oct 8, 2019 at 12:28
-
3Remember also that Yom Kippur lasts until midnight on the 9th. To highlight (to me at least) think of this like SE announcing major changes on Christmas Eve and will release their decision on Boxing day. Might sound like it makes so difference except the lady at the heart of this is a practicing Jew.gbjbaanb– gbjbaanb2019-10-08 17:42:30 +00:00Commented Oct 8, 2019 at 17:42
-
1if you know beforehand that you will not amend the CoC as a reaction of community feedback then yes, it is enough time. There is nothing in SEs past behaviour that makes me think that there is the slightest chance that they will listen to us this time.Michael– Michael2019-10-09 21:31:29 +00:00Commented Oct 9, 2019 at 21:31
-
@sth You've been proven right by today's series of events.March Ho– March Ho2019-10-11 02:41:35 +00:00Commented Oct 11, 2019 at 2:41
-
Thank you for the generous bounty you awarded an answer of mine yesterday and for acknowledging its small role during this era of conflicts. The bounty was totally unexpected.Mari-Lou A Слава Україні– Mari-Lou A Слава Україні2019-11-19 10:30:56 +00:00Commented Nov 19, 2019 at 10:30
Add a comment
|
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