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.

Rev

2

Isn't it pretty much a universal thing in the corporate world that "good faith efforts" don't mean squat unless you have proper communication along with them? A good share of the blame for increasing tensions also go to the piss-poor communication strategy used by SE (i.e., no strategy at all)
– muru
Commented Jul 1 at 16:30
29

@muru In this case, the strategy they've tried is: "Here's a list of things that you've asked for that we were able to get to recently", with links to the reports on MSO/MSE. How exactly is that "no strategy at all"? Seems rather effective to me, and that's in addition to the responses and tags on the individual items as well. Do you have a more constructive suggestion for how you'd like communication of bug fixes to be different? Or, if SE remains a corporate entity, is it not possible for them to communicate to your standards?
– Bryan Krause
Commented Jul 1 at 16:40
2

@BryanKrause as the mentioned complaints state, most of these changes happened network-wide, and the first staff-authored Meta SE post announcing many of them was ... this one. The rest of the network outside of SO was just blindsided by these changes. If that's effective to you then we fundamentally disagree on how communication should work.
– muru
Commented Jul 1 at 16:44
27

@muru Not every change is worth a full press release. Would you rather staff spend their time fixing bugs or communicating with you every time they move? Gold tag badges are now applied to synonymized tags, and you found out about it today...are you sure "blindsided" is an appropriate way to communicate how this change has impacted you by not learning about it ahead of time?
– Bryan Krause
Commented Jul 1 at 16:51
24

@muru - The company is required to give advance notice for changes that "...substansively impact the user experience". I wouldn't classify any of the changes made here as meeting that definition. Most of the changes were also made known by changes to status tags as the changes were made. I don't think there's a problem with how it was done. It would have been nice to know about the overall effort ahead of time, but that shouldn't get in the way of recognizing the positives.
– Mithical
Commented Jul 1 at 16:55
3

While I refrained from negative comments, I did share my pessimism in chat, and I sadly stand behind it. There is nothing assuring us the company will keep this going. On the contrary: all past attempts started with bells and whistles, giving lots of hope and.... vanished into thin air, usually when the involved staff found themself outside of Stack Exchange. I do hope to be wrong, and to see SE actually listening to the users and keeping those Sprints going, but I just can't cling to such a faint hope. A tiger does not become a lamb just like that.
– Shadow Wizard
Commented Jul 1 at 17:14
12

@ShadowWizard The long-term outlook is that everything we've ever done will be gone and forgotten. It's okay to appreciate good things, not only the second derivative of goodness.
– wizzwizz4
Commented Jul 1 at 17:26
1

@wizzwizz4 what muru said in the first comment also holds true. There's still no proper communication, they pick random requests and do them. Yes, I do appreciate the effort, and I never had anything against the developers or CMs themselves. The direction in which Stack Exchange is going is still wrong, the core problems are still there, unattended to. One might ask "OK. Shadow, so what do you want? What will satisfy you?" and the answer is, and I say it with sadness, is: nothing. I lost trust in the company already, and it's shattered beyond repair.
– Shadow Wizard
Commented Jul 1 at 18:00
20

@ShadowWizard If it's beyond repair, why are you still here commenting? I wouldn't assume that the requests that were addressed were "random", and I also don't want them wasting time creating too detailed of a priority list. It seems like they've set aside some time to just crunch through the stuff that's been lingering. That's a good thing.
– Bryan Krause
Commented Jul 1 at 20:13
8

To answer your question, @Mithical: maybe it got lost in translation, but when I said "public-facing developer teams" in the initial paragraph of the "Introducing the Community Asks Sprints" section, I meant the teams that currently work on the public side of things — which is to say, Teams developers, for instance, didn't take part in this. The effort does, however, encompass folks who normally work on things related to ads, brand awareness projects, collectives, etc.
– JNat StaffMod
Commented Jul 2 at 14:54

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 »