# How does the Sandbox work? How do I use it?

I've noticed some people here talking about a "proposed question sandbox."

• Where is the sandbox?
• Why should I use the sandbox?
• How does the sandbox work?
• What should we do with abandoned proposals?
• How should I review proposals?
• What should the format of sandbox posts be (title, tags, body)?
• How long should I leave a question in the sandbox?

• I've edited the link to the sandbox to automatically show sandbox posts sorted by "active". I've then realised that although this does not affect sorting on the main site, it does change my meta default sort to "active" until next time I change it elsewhere. Should the link be reverted to prevent this? Aug 31 '14 at 14:27

# Where is the sandbox?

The sandbox is located on this meta post. Sandboxed challenges are posted as answers to this question.

# Why should I use the sandbox?

You might be thinking, perhaps, why would you stage questions on the sandbox instead of posting them directly?

To answer this, let's see what could happen if you post it directly:

• If your question is incomplete, it will probably be quickly closed and ruined.
• If your question has a hole in the specification, answers could exploit it, spoiling the fun of your question.
• If people think that some point of the question is unclear, they will complain about it in comments and downvote your question. If you are unlucky, your question might get closed.
• People might complain that your question is overly restrictive, overly open, or simply disagree with its rules or scoring system.
• If your question has some point that is unclear or vague, some people may misunderstand it and post some bad answers, leading to unnecessary arguments, downvotes and frustration.

The sandbox is intended to mitigate all those problems.

# How does the sandbox work?

1. You get an idea for a nice question for this site.
2. You post an answer to the sandbox. Your answer to the sandbox should contain the question that you are proposing. It is ok if your question is still incomplete.
3. After you post it there, people will give suggestions to improve your question and point out potential problems.
4. You fix the problems, improving your question.
5. When people agree that it is good, they will upvote it here in the sandbox; you should wait until a sufficient number of people seem to support your proposed challenge via voting and commenting before posting it on the main site.
6. Now that you know that most of the problems are worked out, you post it in the main site.

Furthermore, the sandbox allows you to suggest improvements for questions from other people too. Upvote other people's questions when you think that they are ready.

When you post your question on the main site, edit the sandbox post to include a link to the challenge, removing everything but the title and the link. This is to keep the sandbox more compact and reduce the scrolling needed to view other proposals. Furthermore, delete the post. (You should edit it anyway, because high-reputation users can still see deleted posts.)

# What should we do with abandoned proposals?

All content on Stack Exchange is licensed under CC BY-SA, so legally you are allowed to claim an abandoned idea yourself to make it ready for main and post it. However, doing so you should follow a few rules of courtesy. The following process has been agreed on:

• If a challenge proposal was not edited or commented on for a month, you can leave a comment that you would like to take over the challenge, get it ready for main and post it.
• If the OP does not reply within two weeks, telling you that they still intend to post the challenge themselves, you are free to proceed with the challenge as you see fit.
• Don't repost, just edit the existing post.

You can use the following standard comment to express your interest in a challenge:

This challenge proposal has been inactive for over a month. I would like to take ownership of the challenge and make it ready for posting. Please let me know within the next 14 days if you have any objections and would still like to finish and post this challenge yourself.

# How should I review proposals?

You can contribute to the community by reviewing proposals to help them get ready for posting. Here is some advice to make your reviewing more productive and more helpful:

• Sort the sandbox by active (even if it means switching back for other questions). The sandbox has grown very large over time, but when sorting by activity, only the first page or so will be relevant for reviewing. Everything else is posted and abandoned. So this allows you to get a quick overview over new or recently edited challenge ideas.
• For clearly incomplete challenges, the author will usually ask for feedback, so try to answer their questions and help them fill the missing gaps. If it is already clear at this stage that there are severe problems with the proposal, which are not likely to be fixed by completing the spec, inform the author so they can fix the problems before wasting effort on the challenge.
• For apparently complete challenges, here are a few points to check when reviewing proposals. You should basically go through the close-vote reasons for challenges, and make sure that the idea won't fall victim to them when posted in the current form:
• Is the challenge new? Otherwise, point the author to an existing question their idea is a duplicate of, so they can consider differentiating their proposal appropriately.
• Is the challenge reasonably scoped? If there are too many possible (valid) answers to a challenge, or the challenge would preclude many interesting (more narrowly) scoped challenges in the future, it is probably too broad.
• Does the challenge state objective criteria for validity of an answer as well as the score of an answer.
• Is the specification clear (about input, output, the problem, all edge cases) and free of contradictions?
• Does the challenge need more test cases?
• If there are no more problems with the challenge and it could be posted as it is, upvote the proposal. There are exceptions to this rule: some author might want to gather general interest in a problem before putting work into finalizing the spec or a necessary control program. If this is stated, you should use your votes accordingly.

# How long should I leave a question in the sandbox?

In general you should leave a question at least 72 hours to ensure that the people who check it fairly regularly will have a chance to see it and comment.

Typically, a net score of +3 or higher means that your post is ready to be posted over to main, but this isn't a hard and fast rule, merely a recommendation. The more downvotes your post has, even with a net score of +3, the less likely your challenge is to be ready.

• This would be a good place to add links to guides on with a good question, templates, etc.
– xnor
Aug 21 '14 at 2:34
• Should the FAQ include information for reviewers of sandbox questions? i.e. recommending to sort by active, what to look for when reviewing, etc. Aug 25 '14 at 18:21
• @chilemagic I think that's a great idea! Sep 1 '14 at 14:06
• What exactly is "a sufficient number of people" these days? I think it used to be 3, but I'm struggling to get enough people to notice my questions
– user16402
Sep 11 '14 at 18:53
• If I post my question on main, do I delete my Sandbox question or simply edit it as posted? Apr 7 '15 at 12:58
• Don't repost, just edit the existing post. Is it OK to repost if you don't have enough rep to edit (since there are no edit suggestions on Meta)? Sep 24 '15 at 14:10
• Do people actually agree with good Sandbox posts, or am I just terrible at creating questions?
– Neil
Aug 9 '16 at 9:04

## How long should I leave a question in the sandbox?

In general you should leave a question at least 72 hours to ensure that the people who check it fairly regularly will have a chance to see it and comment.

• This question should be in the list of the OP as well. It's exactly what I was looking for, but barely noticed it as I wasn't expecting answers to different questions below the accepted answer. Unfortunately I can't edit the OP yet. Nov 10 '15 at 9:22

# Template for Challenge Proposals

Every proposal should contain several fixed pieces of information, including a title, the tags you intend to use and body of the challenge as you intend to post it on main. For a more uniform look of the sandbox (and easier orientation of reviewers), it is recommended that you use the following markdown template:

# My Challenge Title
[tag:my-challenge-type-tag] [tag:my-descriptive-tags]

Here goes the body of your challenge, literally as you intend to post it on main.
Incomplete sections and notes intended only for the sandbox phase can be denoted
as follows: [**Sandbox note:** I still need to add test cases.]

## Sandbox Questions

In this section at the end you can put a few general sentences/questions aimed at
reviewers in the sandbox, e.g. to inform people what parts of the spec are still
subject to change or asking for specific feedback on parts of your challenge.
This is also the place to let people know if you are want to gauge the community's
interest in your problem before committing to finalizing the spec or writing a
verifier/controller for the challenge, so they will use their votes to indicate
interest in instead of completeness of the proposal.