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

Post History

71%
+3 −0
Meta Category migration and the sandbox

Start afresh but keep history When migrating to the Challenges category, there are several aspects of the post that could be included or discarded: Comments Edit history Votes Comments Th...

posted 2mo ago by trichoplax‭  ·  edited 2mo ago by trichoplax‭

Answer
#3: Post edited by user avatar trichoplax‭ · 2024-10-20T12:48:54Z (about 2 months ago)
Improve sentence flow
  • ## Start afresh but keep history
  • When migrating to the Challenges category, there are several aspects of the post that could be included or discarded:
  • - Comments
  • - Edit history
  • - Votes
  • ### Comments
  • The comments during sandbox development are not relevant to the final challenge, and would be a distraction from the conversations that happen after posting the final challenge. Leaving these old conversations displayed below the challenge might also invite further discussion of how the challenge should be designed, which is likely to be too late to change by this point.
  • However, it may sometimes be useful to go back and view the discussion that occurred in the Sandbox. This could be out of interest, for people interested in the history of the particular challenge, or interested in learning about how challenges in general develop over time. This would also be useful if someone questions the design of a live challenge - rather than have a discussion someone can simply link to the relevant comment thread that already reached consensus with detailed reasons why.
  • For this reason, I would like the comments to be preserved, but to not be present on the final challenge.
  • ### Edit history
  • Similarly to comments, I think that the history of the Sandbox post is not relevant to the final challenge. In many cases the challenge design may have changed drastically during development. I would like to see only changes that happened since the point that the final challenge was posted, because these are the ones that are relevant to whether a change has unfairly invalidated an existing answer.
  • However, I would still like the history of the Sandbox post to be preserved. Similarly to comments, it can be both interesting and practically useful to be able to refer back to how things changed.
  • For this reason, I would like the edit history to be preserved, but to not be present on the final challenge.
  • ### Votes
  • Similarly to comments and edit history, I would like every new challenge to start with no votes (up or down), but to still have the votes preserved in the sandbox. This can be useful for anyone interested in how various challenges were initially received in the Sandbox. It is also an easy way to verify that a challenge idea was well received, and not posted as a final challenge too soon.
  • ## Copy rather than migrate
  • My thoughts on comments, edit history, and votes all point towards keeping the sandbox post around as a record. I like the idea of being able to post a new challenge from a Sandbox draft at the touch of a button, but this doesn't need to destroy the Sandbox draft.
  • I propose that we have a method for creating a new challenge from a Sandbox post, that leaves the Sandbox post intact as a record. As suggested in the question, this should only be available to the author, unlike migrations which might be available to several groups, such as curators and moderators.
  • The new challenge would include the following:
  • - Body
  • - Title
  • - Tags
  • - Licence
  • The new challenge would not include the following:
  • - Comments
  • - Edit history
  • - Votes
  • Some additional features that would be nice to have:
  • - Link to the new challenge automatically added to the Sandbox post (either at the top of the body or in a new comment thread with a title like "Now posted").
  • - Link to the Sandbox post automatically added to the new challenge (probably as a comment to avoid distracting from the body of the challenge, although possibly using some more general future feature for links to related posts).
  • - Archive the Sandbox post, so it is easily available to people looking for drafts of challenges that have since been posted, but does not distract people browsing the Sandbox to give feedback. This might be future work if a more general archiving feature is implemented for other communities. This would reduce the risk of an author accidentally creating a new challenge twice from the same Sandbox draft.
  • ## Start afresh but keep history
  • When migrating to the Challenges category, there are several aspects of the post that could be included or discarded:
  • - Comments
  • - Edit history
  • - Votes
  • ### Comments
  • The comments during sandbox development are not relevant to the final challenge, and would be a distraction from the conversations that happen after posting the final challenge. Leaving these old conversations displayed below the challenge might also invite further discussion of how the challenge should be designed, which is likely to be too late to change by this point.
  • However, it may sometimes be useful to go back and view the discussion that occurred in the Sandbox. This could be out of interest, for people interested in the history of the particular challenge, or interested in learning about how challenges in general develop over time. This would also be useful if someone questions the design of a live challenge - rather than have a discussion someone can simply link to the relevant comment thread that already reached consensus with detailed reasons why.
  • For this reason, I would like the comments to be preserved, but to not be present on the final challenge.
  • ### Edit history
  • Similarly to comments, I think that the history of the Sandbox post is not relevant to the final challenge. In many cases the challenge design may have changed drastically during development. I would like to see only changes that happened since the point that the final challenge was posted, because these are the ones that are relevant to whether a change has unfairly invalidated an existing answer.
  • However, I would still like the history of the Sandbox post to be preserved. Similarly to comments, it can be both interesting and practically useful to be able to refer back to how things changed.
  • For this reason, I would like the edit history to be preserved, but to not be present on the final challenge.
  • ### Votes
  • Similarly to comments and edit history, I would like every new challenge to start with no votes (up or down), but to still have the votes preserved in the sandbox. This can be useful for anyone interested in how various challenges were initially received in the Sandbox. It is also an easy way to verify that a challenge idea was well received, and not posted as a final challenge too soon.
  • ## Copy rather than migrate
  • My thoughts on comments, edit history, and votes all point towards keeping the sandbox post around as a record. I like the idea of being able to post a new challenge from a Sandbox draft at the touch of a button, but this doesn't need to destroy the Sandbox draft.
  • I propose that we have a method for creating a new challenge from a Sandbox post, that leaves the Sandbox post intact as a record. As suggested in the question, this should only be available to the author, unlike migrations which might be available to several groups, such as curators and moderators.
  • The new challenge would include the following:
  • - Body
  • - Title
  • - Tags
  • - Licence
  • The new challenge would not include the following:
  • - Comments
  • - Edit history
  • - Votes
  • Some additional features that would be nice to have:
  • - A link to the new challenge automatically added to the Sandbox post (either at the top of the body or in a new comment thread with a title like "Now posted").
  • - A link to the Sandbox post automatically added to the new challenge (probably as a comment to avoid distracting from the body of the challenge, although possibly using some more general future feature for links to related posts).
  • - The Sandbox post automatically archived, so it is easily available to people looking for drafts of challenges that have since been posted, but does not distract people browsing the Sandbox to give feedback. This might be future work if a more general archiving feature is implemented for other communities. This would reduce the risk of an author accidentally creating a new challenge twice from the same Sandbox draft.
#2: Post edited by user avatar trichoplax‭ · 2024-10-18T17:50:35Z (about 2 months ago)
Add extra detail
  • ## Start afresh but keep history
  • When migrating to the Challenges category, there are several aspects of the post that could be included or discarded:
  • - Comments
  • - Edit history
  • - Votes
  • ### Comments
  • The comments during sandbox development are not relevant to the final challenge, and would be a distraction from the conversations that happen after posting the final challenge. Leaving these old conversations displayed below the challenge might also invite further discussion of how the challenge should be designed, which is likely to be too late to change by this point.
  • However, it may sometimes be useful to go back and view the discussion that occurred in the Sandbox. This could be out of interest, for people interested in the history of the particular challenge, or interested in learning about how challenges in general develop over time. This would also be useful if someone questions the design of a live challenge - rather than have a discussion someone can simply link to the relevant comment thread that already reached consensus with detailed reasons why.
  • For this reason, I would like the comments to be preserved, but to not be present on the final challenge.
  • ### Edit history
  • Similarly to comments, I think that the history of the Sandbox post is not relevant to the final challenge. In many cases the challenge design may have changed drastically during development. I would like to see only changes that happened since the point that the final challenge was posted, because these are the ones that are relevant to whether a change has unfairly invalidated an existing answer.
  • However, I would still like the history of the Sandbox post to be preserved. Similarly to comments, it can be both interesting and practically useful to be able to refer back to how things changed.
  • For this reason, I would like the edit history to be preserved, but to not be present on the final challenge.
  • ### Votes
  • Similarly to comments and edit history, I would like every new challenge to start with no votes (up or down), but to still have the votes preserved in the sandbox. This can be useful for anyone interested in how various challenges were initially received in the Sandbox. It is also an easy way to verify that a challenge idea was well received, and not posted as a final challenge too soon.
  • ## Copy rather than migrate
  • My thoughts on comments, edit history, and votes all point towards keeping the sandbox post around as a record. I like the idea of being able to post a new challenge from a Sandbox draft at the touch of a button, but this doesn't need to destroy the Sandbox draft.
  • I propose that we have a method for creating a new challenge from a Sandbox post, that leaves the Sandbox post intact as a record.
  • The new challenge would include the following:
  • - Body
  • - Title
  • - Tags
  • - Licence
  • The new challenge would not include the following:
  • - Comments
  • - Edit history
  • - Votes
  • Some additional features that would be nice to have:
  • - Link to the new challenge automatically added to the Sandbox post (either at the top of the body or in a new comment thread with a title like "Now posted").
  • - Link to the Sandbox post automatically added to the new challenge (probably as a comment to avoid distracting from the body of the challenge, although possibly using some more general future feature for links to related posts).
  • - Archive the Sandbox post, so it is easily available to people looking for drafts of challenges that have since been posted, but does not distract people browsing the Sandbox to give feedback. This might be future work if a more general archiving feature is implemented for other communities.
  • ## Start afresh but keep history
  • When migrating to the Challenges category, there are several aspects of the post that could be included or discarded:
  • - Comments
  • - Edit history
  • - Votes
  • ### Comments
  • The comments during sandbox development are not relevant to the final challenge, and would be a distraction from the conversations that happen after posting the final challenge. Leaving these old conversations displayed below the challenge might also invite further discussion of how the challenge should be designed, which is likely to be too late to change by this point.
  • However, it may sometimes be useful to go back and view the discussion that occurred in the Sandbox. This could be out of interest, for people interested in the history of the particular challenge, or interested in learning about how challenges in general develop over time. This would also be useful if someone questions the design of a live challenge - rather than have a discussion someone can simply link to the relevant comment thread that already reached consensus with detailed reasons why.
  • For this reason, I would like the comments to be preserved, but to not be present on the final challenge.
  • ### Edit history
  • Similarly to comments, I think that the history of the Sandbox post is not relevant to the final challenge. In many cases the challenge design may have changed drastically during development. I would like to see only changes that happened since the point that the final challenge was posted, because these are the ones that are relevant to whether a change has unfairly invalidated an existing answer.
  • However, I would still like the history of the Sandbox post to be preserved. Similarly to comments, it can be both interesting and practically useful to be able to refer back to how things changed.
  • For this reason, I would like the edit history to be preserved, but to not be present on the final challenge.
  • ### Votes
  • Similarly to comments and edit history, I would like every new challenge to start with no votes (up or down), but to still have the votes preserved in the sandbox. This can be useful for anyone interested in how various challenges were initially received in the Sandbox. It is also an easy way to verify that a challenge idea was well received, and not posted as a final challenge too soon.
  • ## Copy rather than migrate
  • My thoughts on comments, edit history, and votes all point towards keeping the sandbox post around as a record. I like the idea of being able to post a new challenge from a Sandbox draft at the touch of a button, but this doesn't need to destroy the Sandbox draft.
  • I propose that we have a method for creating a new challenge from a Sandbox post, that leaves the Sandbox post intact as a record. As suggested in the question, this should only be available to the author, unlike migrations which might be available to several groups, such as curators and moderators.
  • The new challenge would include the following:
  • - Body
  • - Title
  • - Tags
  • - Licence
  • The new challenge would not include the following:
  • - Comments
  • - Edit history
  • - Votes
  • Some additional features that would be nice to have:
  • - Link to the new challenge automatically added to the Sandbox post (either at the top of the body or in a new comment thread with a title like "Now posted").
  • - Link to the Sandbox post automatically added to the new challenge (probably as a comment to avoid distracting from the body of the challenge, although possibly using some more general future feature for links to related posts).
  • - Archive the Sandbox post, so it is easily available to people looking for drafts of challenges that have since been posted, but does not distract people browsing the Sandbox to give feedback. This might be future work if a more general archiving feature is implemented for other communities. This would reduce the risk of an author accidentally creating a new challenge twice from the same Sandbox draft.
#1: Initial revision by user avatar trichoplax‭ · 2024-10-18T17:43:53Z (about 2 months ago)
## Start afresh but keep history
When migrating to the Challenges category, there are several aspects of the post that could be included or discarded:

- Comments
- Edit history
- Votes

### Comments
The comments during sandbox development are not relevant to the final challenge, and would be a distraction from the conversations that happen after posting the final challenge. Leaving these old conversations displayed below the challenge might also invite further discussion of how the challenge should be designed, which is likely to be too late to change by this point.

However, it may sometimes be useful to go back and view the discussion that occurred in the Sandbox. This could be out of interest, for people interested in the history of the particular challenge, or interested in learning about how challenges in general develop over time. This would also be useful if someone questions the design of a live challenge - rather than have a discussion someone can simply link to the relevant comment thread that already reached consensus with detailed reasons why.

For this reason, I would like the comments to be preserved, but to not be present on the final challenge.

### Edit history
Similarly to comments, I think that the history of the Sandbox post is not relevant to the final challenge. In many cases the challenge design may have changed drastically during development. I would like to see only changes that happened since the point that the final challenge was posted, because these are the ones that are relevant to whether a change has unfairly invalidated an existing answer.

However, I would still like the history of the Sandbox post to be preserved. Similarly to comments, it can be both interesting and practically useful to be able to refer back to how things changed.

For this reason, I would like the edit history to be preserved, but to not be present on the final challenge.

### Votes
Similarly to comments and edit history, I would like every new challenge to start with no votes (up or down), but to still have the votes preserved in the sandbox. This can be useful for anyone interested in how various challenges were initially received in the Sandbox. It is also an easy way to verify that a challenge idea was well received, and not posted as a final challenge too soon.

## Copy rather than migrate
My thoughts on comments, edit history, and votes all point towards keeping the sandbox post around as a record. I like the idea of being able to post a new challenge from a Sandbox draft at the touch of a button, but this doesn't need to destroy the Sandbox draft.

I propose that we have a method for creating a new challenge from a Sandbox post, that leaves the Sandbox post intact as a record.

The new challenge would include the following:
- Body
- Title
- Tags
- Licence

The new challenge would not include the following:
- Comments
- Edit history
- Votes

Some additional features that would be nice to have:
- Link to the new challenge automatically added to the Sandbox post (either at the top of the body or in a new comment thread with a title like "Now posted").
- Link to the Sandbox post automatically added to the new challenge (probably as a comment to avoid distracting from the body of the challenge, although possibly using some more general future feature for links to related posts).
- Archive the Sandbox post, so it is easily available to people looking for drafts of challenges that have since been posted, but does not distract people browsing the Sandbox to give feedback. This might be future work if a more general archiving feature is implemented for other communities.