Checklist for migration to Code Review
Is the question off-topic on the originating site?
Are you sure? Do not migrate if there is doubt.
Is the question on-topic for Code Review?
The question must contain working code. Code Review is not a
debugging service. Reviewers may discover bugs in the course of
answering, but the code should be generally ...
Well it seems like a bug! Thanks to @SimonAndréForsberg that verified other beta sites. It seems like all the beta sites are graduated (YEAH!). See this post for the progress of the bug Did all sites just graduate?
We require that the asker posts code that they have written themselves. In that case it can be assumed that the asker owns the copyright for that code and can license that code to Code Review under CC-BY-SA. For this it is irrelevant whether that code was already published elsewhere under a different license; one creative work can be dual-licensed under ...
As already mentioned by @Jamal in the comments, StackExchange provides a Contact Form, as well as an Inbox shared by the community managers.
That being said, namecalling is not really liked in such cases. If you wish to raise a complaint against moderators (who are the trusted authority in the whole network), please consider carefully whether you might be ...
Stack Overflow is for concrete problems; if it's somehow not working as intended.
Code Review is for code that works as intended, but could use improvements - to performance, to maintainability, or other goals.
Software Engineering is for the conceptual questions.
(I recall there's a diagram about that, but have been unable to find it back).
Since you ...
Normally, code blocks are formatted using four spaces of indentation:
var string = 'string';
In a list, code blocks require eight spaces:
var string = 'string';
After a list, a code block can be made using four spaces of indentation, but it needs to be after an intervening <!-- comment -->.
var string = 'string';
In any case, you will always give up the amount of reputation
specified in the bounty, so if you start a bounty, be sure to follow
up and award your bounty to the best answer!
When a bounty is not awarded to anyone, they do not return to the awarder, they are simply lost. There is no conservation of reputation.
Looks like this is by design.
If you go to the very last page of all-time voters on the site, you'll see that anyone with less than 11 votes isn't showing up.
You need to vote some more. And then some.
Simple as that! ;)
Voting generates reputation on the site.
For the beta site CR is, voting is like breathing. If we stop voting, the site dies.
Every graduated Stack Exchange site has their own.
Our story is here on the design announcement meta - basically the badge icons are part of the customizable things each site gets to pick as their design is being finalized - we settled on curly braces because, well, they're more code-like than the originally-suggested design:
Moderators lock questions when they need to cool things down. There's nothing an ordinary user can do about it.
This time we just needed some time to figure out what was going on. Since neither 200_success or myself (who were the present moderators at the time) has 10k reputation on Stack Overflow, we were not 100% sure about who was the original poster of ...
The help center has the following note about bounties:
To avoid overly promotional bounties, if you are offering a bounty on
a question that you have already posted an answer to, your minimum
spend is 100 reputation (not 50).
I don't know whether it is by design, or if it is a bug, that your deleted post is being counted as a posted answer. I can see ...
(the bulk of this answer is plagiarized borrowed from: What is migration and how does it work? - I have taken that and adapted it to focus on Code Review specific concerns)
Migrating to Code Review:
Migration allows a question that is off-topic on one ...
You could flag your own question, but… is it really a duplicate? The Stack Overflow answer may solve your main concern, but maybe there are other aspects about your code that could be improved.
I suggest that you use the Stack Overflow information to write an answer to your own question instead.
You're absolutely right; that header doesn't make sense. This does indeed only apply to questions without answers, which can be edited freely without violating this policy. I'll make this change to that header in the Help Center.
Bearing this in mind, feel free to edit your question until it does get an answer.
The creation of stackapp has been accepted shortly after
On Stack Exchange anyone with sufficient reputation can create a tag. There is nothing for anyone to approve or accept with that. Both stackapp and flair were created by you on your question, and then both tags were removed from your question through an edit by another user.
I will not answer your ...
Someone flagged your post for "should be closed" -> "off-topic" -> "Authorship of code" which caused it to be put into the close vote review queue where 5 users voted to close and 1 voted to leave open.
Possible lessons hopefully to be learned:
Close voters can help out by asking clarifying questions - "Is this code yours?" "Where did you find this code?"
In addition to 200_success's answer here. I would like to add that, in addition to your post being about an error, it also:
contains no code to review (just an error message)
the code that is failing is not your code
even if all the code was included, and a short way to illustrate the fail, the question would not be on-topic on any other Stack Exchange site....
You can ask any question on Meta. If the community deems it to be an important question, then a moderator will add an faq tag on it.
Recently, we have also been starting to promote the most important information from Meta into Help Center.
These are very short solutions to the same problem. Just ask one question with a comparative-review tag, containing the description of the exercise, followed by three separate code blocks. Please also mention what you think are the pros and cons of each of your solutions.
This is known as a post notice, and I was the one who posted this one.
While I could've easily posted a comment to that user, I've decided to use a post notice to make the message more visible for others. I do not know if that particular answer was migrated from SO, though. If it was, that would be understandable. But it seemed out of place on CR as we ...
We rely on external scripts for everything. Seriously - if you block all 3rd-party scripts, just about every page on the site will error out and you'll be stuck using the script-free fallbacks, at least where they exist.
I'm not gonna judge you if you want to block 3rd-party scripts. That's a personal decision, and if you're satisfied you have good reason ...
Java is my standard language, but, for formatting code to put here, this is typically what I do, depending on where I am...
For example, someone posts a question to Stack Overflow, and the indenting/formatting is horrible....
First, I edit the post, then select the code that needs indenting/fixing.
Type CtrlX to cut it, then:
AltTab to ...
To create a tag, you edit an existing question that you think could use the tag and add the tag to the taglist at the bottom, or add the tag when creating a new question.
It is not possible to create a tag without attaching it to a question.
For more information see Privileges - Create Tags.
Note that only users with at least 150 reputation can do this.
Please read the close reason on the question. Broken code is off-topic for Code Review. Since the question was almost certainly unsalvageable, it was deleted.
The links in the close reason will guide you towards other possible resources for help.
You should feel discouraged from posting code that should not be 'in the wild'. If you do not have the rights to post the code, then don't post it.
Code Review requires that the code is 'real code', and not example code. Many times it is possible to post the code you want reviewed 'as is', and it's fine. If your code has sensitive information in it (...
There are two questions in your post. First, the title (keyword highlighting mine):
Are specific troubleshooting questions on topic?
Absolutely not. If you've identified a bug in your code and/or it's not working as intended and you're hoping to submit your code for peer review for us to say "well here's your bug!", your question will be closed.
If you ...