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.

2

If I'm reading you correctly, the concerns you have are more easily addressed by redirecting posters from local Metas to MSE, when they're reporting bugs or requesting features that are likely to have a network-wide impact — that would ensure _ community discussion_ happens in a broader stage, rather than a staff announcement.
– JNat StaffMod
Commented Jul 3 at 12:38
3

Part of the challenge of the sprint is its short nature, which is somewhat at odds with doing a lot of pre-comms, and back and forth (doesn't mean "ship and forget" of course) — see Slate's comment here for a note on how we tried to pick issues that were relatively uncontroversial in terms of solutions, because they'd already been discussed and had seemingly reached a community consensus.
– JNat StaffMod
Commented Jul 3 at 12:38
Thanks, @JNat, that makes a lot of sense.
– Joachim
Commented Jul 3 at 16:59

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 »