Timeline for answer to An apology to our community, and next steps by user245382
Current License: CC BY-SA 4.0
Post Revisions
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2019 at 10:30 | comment | added | Mari-Lou A Слава Україні | 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. | |
| Oct 11, 2019 at 2:41 | comment | added | March Ho | @sth You've been proven right by today's series of events. | |
| Oct 9, 2019 at 21:31 | comment | added | Michael | if 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. | |
| Oct 8, 2019 at 17:42 | comment | added | gbjbaanb | Remember 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. | |
| Oct 8, 2019 at 12:28 | comment | added | iLuvLogix | @Null Fully agree, though the word disaster is a understatement - that poorly phrased 'apology' was rather a infernal cataclysm.. | |
| Oct 7, 2019 at 20:23 | comment | added | user371773 | 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. | |
| Oct 7, 2019 at 18:35 | comment | added | sth | The 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. | |
| Oct 7, 2019 at 18:04 | comment | added | Justin Time - Reinstate Monica | Sonic the PRHog Says: "Gotta post fast!" | |
| Oct 7, 2019 at 12:32 | comment | added | Jean-François Fabre | TL;DR I'm staying | |
| Oct 7, 2019 at 7:19 | comment | added | T.J. Crowder | That 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. | |
| Oct 7, 2019 at 1:54 | comment | added | Null | I 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. | |
| Oct 6, 2019 at 21:54 | comment | added | Uphill Luge | Indeed. 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. | |
| Oct 6, 2019 at 21:51 | comment | added | Mark | Presumably 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. | |
| Oct 6, 2019 at 21:50 | comment | added | Andrew Leach | Exactly. It was just this sort of haste that caused the last, um, little hiccup. | |
| Oct 6, 2019 at 21:45 | history | answered | user245382 | CC BY-SA 4.0 |