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

6

FINALLY! An answer that makes sense. (Okay, I'm a bit slow to find this.) SE should be thought of as a "team" of distributed sites where a submission to one is really, eventually, a submission to all. As a former DBA, I get it now. Wish this answer got more love. I think it would greatly reduce the amount of cross-posting by folks (like me) that don't understand why it is both unnecessary and disruptive to maintaining a high quality database of information. Thank You @CuriousProgrammer !
– DocSalvager
Commented Feb 20, 2016 at 5:27
7

The first part of the answer has solid grounds on arguments aiming at "being useful for the community". Then it comes an argument - almost litany - with little orientation towards being useful. This looks to me, in short, as "The essence of two questions posted in different SE sites can be exactly the same, but they have to be differently worded to be admissible". That, for me, is like encouraging make-up on the wording so they do not look awkward... appearances above meaning. For me, this should be frowned upon.
– sancho.s ReinstateMonicaCellio
Commented Sep 25, 2018 at 7:56
4

This answer starts out really promising: "The SE Network was not designed for duplicate questions across sites" sounds like the key; but then it never explains what that statement is actually supposed to mean! Does Stack have a software limitation that prevents exact dupes? Is the "knowledge repository" of all Stacks supposed to be combined? If that's the case, why do we have overlapping site scopes? This answer does little more than state what is, just like the answers it faults in its opening line. Disappointed, adds little to the conversation.
– zcoop98
Commented Jun 8, 2021 at 13:57

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 »