In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
I'd like to expand on the "collaborative, community-orientated" aspect, because it's the cornerstone of my counter-proposal below. Most SE sites involve some sort of personal question the OP has (that other people potentially share). So questions on those sites are more personal. On this site, coding challenges have nothing to do with personal questions; they don't help the OP personally. To that end, the more community refinement a challenge gets, the higher the quality, in general.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.
In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
I'd like to expand on the "collaborative, community-orientated" aspect, because it's the cornerstone of my counter-proposal below. Most SE sites involve some sort of personal question the OP has (that other people potentially share). So questions on those sites are more personal. On this site, coding challenges have nothing to do with personal questions; they don't help the OP personally. To that end, the more community refinement a challenge gets, the higher the quality, in general.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.
In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
I'd like to expand on the "collaborative, community-orientated" aspect, because it's the cornerstone of my counter-proposal below. Most SE sites involve some sort of personal question the OP has (that other people potentially share). So questions on those sites are more personal. On this site, coding challenges have nothing to do with personal questions; they don't help the OP personally. To that end, the more community refinement a challenge gets, the higher the quality, in general.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.
- 5k
- 25
- 42
In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
I'd like to expand on the "collaborative, community-orientated" aspect, because it's the cornerstone of my counter-proposal below. Most SE sites involve some sort of personal question the OP has (that other people potentially share). So questions on those sites are more personal. On this site, coding challenges have nothing to do with personal questions; they don't help the OP personally. To that end, the more community refinement a challenge gets, the higher the quality, in general.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.
In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.
In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
I'd like to expand on the "collaborative, community-orientated" aspect, because it's the cornerstone of my counter-proposal below. Most SE sites involve some sort of personal question the OP has (that other people potentially share). So questions on those sites are more personal. On this site, coding challenges have nothing to do with personal questions; they don't help the OP personally. To that end, the more community refinement a challenge gets, the higher the quality, in general.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.
In this post, I'm speaking as a user, not a moderator.
Your proposal could be workable, if we are willing to weed out questions (and answers) as aggressively as is being done on the Software Recommendations site (and if we have enough high-rep users who can nuke inappropriate questions and answers quickly). That doesn't seem to be the current trend, though.
Currently, the sandbox is a buffer against duplicate, poorly-specified, uninteresting, or just generally inviable challenges. It makes the task of framing challenges a collaborative, community-orientated effort. I am in favour of this latter aspect, and would like to retain it even if we switch to a sandbox-less model.
Personally, I don't consider the sandbox concept problematic per se, but that the frustrations we encounter are simply the result of the limitations in its current place on Meta.
What we need, in my view, is a way to make all the sandbox questions readily accessible and sensibly indexed (without requiring manual work), along with a way to expire submissions that are either clearly unsuitable or else generally have only lacklustre support. This can be achieved with a dedicated sandbox Stack Exchange instance (e.g., sandbox.codegolf.stackexchange.com), where each proposed post is simply a question, with appropriate tagging for ease of indexing. Posts can then be comment-on, edited, closed, and/or deleted independently of others.
Additionally, moderators (and hopefully high-rep users too) would be empowered to quickly migrate posts off the main site to the sandbox should they fail to meet the site standards.