Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Comments on Category migration and the sandbox

Parent

Category migration and the sandbox

+2
−0

This has probably been discussed before but I couldn't find any posts about it.

I think we should re-make the sandbox category in the following way:

  • Votes in the sandbox category should not count towards user reputation. If users get intimidated to post sandbox proposals fearing down-votes, then that is bad for creativity. There should be no negative consequences for posting an on-topic post in the sandbox.

  • It would be nice if there was some means for the author of the question (and them alone) to migrate a post from the Sandbox category to the main Challenges category. Migration needs to discard all comments but otherwise the post should be copied as-is.

  • During "category migration" votes should probably be reset. If someone is posting an interesting proposal and then later publish it as a challenge, they do deserve the up-votes gained from the proposal. But in order to get rid of any down-votes, the easiest and fairest way would be to just reset the vote score. Hopefully those who up-voted the proposal will also visit and up-vote the live challenge.

A way for users to move posts between certain categories without moderator assistance seems like something that could be useful for other sites in the network too. There is for example a Worldbuilding site proposal which would benefit from having the very same sandbox mechanism as described here.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

article -> question, too (1 comment)
Separate answers for voting (1 comment)
Post
+5
−0

Sandbox votes should give no reputation

I believe this is already the case, but for completeness:

I agree that neither upvotes nor downvotes on Sandbox posts should affect reputation.

Although I would encourage everyone to sandbox every challenge idea, I think the benefits of rewarding sandbox posts with reputation increases are outweighed by the disincentive to sandbox if reputation can decrease.

I also think that downvoting in the sandbox is important feedback that can avoid the final challenge being downvoted. Some people may be less inclined to downvote sandbox posts if this decreases reputation for the well meaning author, so the useful feedback is lost.

I wouldn't want to see only upvotes count towards reputation in the sandbox. In addition to being potentially confusing, this would be a one-way valve on reputation, allowing someone to post large numbers of sandbox posts knowing that they can only increase reputation, with no intention of ever posting them as final challenges.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Correct, votes in the sandbox do not affect reputation in either direction, as currently configured. (1 comment)
Correct, votes in the sandbox do not affect reputation in either direction, as currently configured.
Monica Cellio‭ wrote about 2 months ago

Correct, votes in the sandbox do not affect reputation in either direction, as currently configured.