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*
- Not sure what you mean... as I understand it, Tim means that bug specific to one site should be reported on that site's Meta but if the bug is cross-network or affecting more than one site, it should be reported in MSE. What did I miss?user152859– user1528592013-12-19 15:58:55 +00:00Commented Dec 19, 2013 at 15:58
- 1I'm kinda wondering the same as @ShadowWizard - per site issues belong on per-site metas .. that didn't change. We'll still patrol all meta sites anyway, so if something doesn't go in the right bucket, we'll catch it quick enough.user50049– user500492013-12-19 16:00:39 +00:00Commented Dec 19, 2013 at 16:00
- 11Most people don't know what affects multiple sites.jcolebrand– jcolebrand2013-12-19 16:00:46 +00:00Commented Dec 19, 2013 at 16:00
- 5@jcolebrand That's fine, and they can ask on the child meta and mods can handle it like they normally would. My post was intended for this audience, who generally do know where to toss what when it comes to network related stuff.user50049– user500492013-12-19 16:01:36 +00:00Commented Dec 19, 2013 at 16:01
- 4I'm just saying, encourage people to go through the gatekeepers that ARE their local meta mods. Don't encourage them to go straight to MetaSE. I'm just saying don't encourage them to go straight to MetaSE. I don't encourage anyone to go straight to Meta. Ever.jcolebrand– jcolebrand2013-12-19 16:01:41 +00:00Commented Dec 19, 2013 at 16:01
- Well at that point @TinyTim if you have to tell this crowd what's the difference, they don't need that advice and should go to local meta anyways :pjcolebrand– jcolebrand2013-12-19 16:02:13 +00:00Commented Dec 19, 2013 at 16:02
- Let me put it this way: Mrozek would know where to put the issue, you don't need to tell him ;-)jcolebrand– jcolebrand2013-12-19 16:02:30 +00:00Commented Dec 19, 2013 at 16:02
- 6Now I'm completely lost.user50049– user500492013-12-19 16:02:34 +00:00Commented Dec 19, 2013 at 16:02
- 10+1 Allow me to quote the immortal rchern "Your community is here. It is not expected that you live on Meta Stack Overflow. Bug reports are absolutely valid here." and "Posting on a child meta is absolutely fine! ... I can't stand it when I see a post on a child meta and the first comment is "You should have posted this on MSO". ARGGGGGGGGG"Hod - Monica's Army– Hod - Monica's Army2013-12-19 16:24:49 +00:00Commented Dec 19, 2013 at 16:24
- 6I think what jcolebrand is meaning to say is that many bug reports will end up on Meta.SO because users experience the bug on a specific site, and may lack the knowledge to post it on the network Meta site. Not sure whether that's a problem though, mods will simply migrate as needed?Pekka– Pekka2013-12-19 16:24:52 +00:00Commented Dec 19, 2013 at 16:24
- 1I added a "if ever unsure" to the end of that, which I think takes care of it.user50049– user500492013-12-19 16:33:20 +00:00Commented Dec 19, 2013 at 16:33
- 1Actually, I took that back out, it's kind of old guidance. We should just handle it when things show up in the wrong place - and not worry so much about it.user50049– user500492013-12-19 16:53:01 +00:00Commented Dec 19, 2013 at 16:53
- 1@TRiGisTimothyRichardGreen Ah, yes. I'm pretty sure we're going to be setting up migration paths, but I'm not 100% positive of that. I'd rather wait and just see what happens, and do what feels to be the simplest thing if it becomes an issue (which might just be migration paths).user50049– user500492013-12-20 06:29:07 +00:00Commented Dec 20, 2013 at 6:29
- 2This sort of idea would make me sad; meta stack exchange becoming an inner sanctom that regular users weren't supposed to use without authorization from their home modsRichard Tingle– Richard Tingle2014-01-06 08:25:03 +00:00Commented Jan 6, 2014 at 8:25
- 1@jcolebrand I think you're greatly overestimating how hard it is to use 2 sites and see some common features.user154510– user1545102014-01-10 22:11:24 +00:00Commented Jan 10, 2014 at 22:11
| Show 8 more comments
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