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.
Required fields*
-
31This decision is yours alone to make, of course, but I'm having a really hard time seeing anything substantial they've done to address the core concerns since this thing erupted.Pekka– Pekka2019-10-12 18:45:57 +00:00Commented Oct 12, 2019 at 18:45
-
2@Pëkka I don't disagree that some things aren't good, but my main concerns have been addressed. All of the milestones in David Fullerton's post were met, SE has made a significantly improved effort to get feedback from moderators on changes as well as incorporating that feedback into future revisions, and is actively answering questions that we have. I hope to see continued engagement with not only mods, but the broader community over the next few months and into 2020.Thomas Owens– Thomas Owens2019-10-12 19:50:50 +00:00Commented Oct 12, 2019 at 19:50
-
2May I ask, what is the "stuff that I've seen on site has given me hope that SE is at least going to try more"? Can you link to it (or some examples) please? It's very hard to follow what (if anything) they've actually done in response to any of this.user56reinstatemonica8– user56reinstatemonica82019-10-13 14:10:08 +00:00Commented Oct 13, 2019 at 14:10
-
1@user568458 Most of it is moderator-only, so I can't get into details of what has been shared. The important thing is that every milestone in David Fullerton's post was hit and SE has started to reach out and collaborate with moderators on a couple of things. I'm hopeful that this collaboration will continue to strengthen and that there's an improved relationship with the broader community.Thomas Owens– Thomas Owens2019-10-13 14:13:41 +00:00Commented Oct 13, 2019 at 14:13
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