Skip to content

Instantly share code, notes, and snippets.

What would you like to do?

In the last couple of months, the SOCVR room implemented the proposed burnination process from Shog9. As a room owner, I took the liberty to fork that process on GitHub so we could adapt and adjust quickly without risking the hate/love of Meta for every bump of a meta post.

To be clear: approval from Shog9 was obtained here and moderator support from Madara Uchiha was also obtained here.

This question is meant as an evaluation of the process as executed for the first 5 tags by the SOCVR room, as well as our handling of new burnination requests.

The slightly adapted process

Note that 1. wasn't executed during the test. We implemented a less invasive option by leaving a comment. We still feel the re-tag is needed for new requests.

  1. When a burninate-request is posted, it will be marked [meta-tag:status-review] until/unless it scores at least 20. If it never achieves this score, then it should not be acted on; don't interpret apathy as a sign of support.

  2. After reaching the threshold score, the request will be [meta-tag:featured] for one day, exposing it to as much attention on Stack Overflow as possible.

  • Any punny titles will be replaced with, "Should we burninate [name of tag]?"
  • The top of the post the following hidden warning and public notice will be added:
     Please don't edit post title while it has featured tag.
     If you ignore this note, it will be considered as abuse and handled accordingly.
 *This tag is in phase 2 of the burnination process described [here]( 
 The question and comments have been cleaned to allow for on-topic discussion on this tag, 
 please keep it that way. If you want to discuss the process itself, visit the
 [SOCVR]( room.*
  • The question will get a post notice: Featured Burninate Request

This will be a chance for folks to show their support and a chance for folks who thought it was too silly to be worth talking about to step up and explain why the request should be denied.

  1. After its day in the spotlight, a moderator, or someone else on the Community Team will review the request and any arguments against it. There are four criteria for burnination - if the tag doesn't meet any of them, or if it is clear that removing it will do more harm than good, the request will be declined. I'd have preferred to run this process purely on voting, but... That would inevitably lead to trouble. Your distaste for a frustrating game shouldn't result in the destruction of otherwise-valid tags. A high influx of down votes or fresh comments during it's featured phase is a signal to hold back on burnination.

  2. If the tag can be cleanly removed at this point, the moderator skips directly to step #6. If it requires further disambiguation, the request will be tagged [meta-tag:status-planned] signalling that it is time for widespread review and revision of the questions in the tag. This is the time to clean up the edges. During this time, the tag will be blacklisted with a message that links back to the request meta post.. The SOCVR room will be heading the effort.

  3. When Step #4 is completed, whoever is spearheading this request will flag it for moderator attention and the moderator proceed to step #6.

  4. A moderator will ping a CM to delete any closed, downvoted questions in the tag and remove it from the system entirely. This assumes the tag wasn't already removed during review in Step #4.

Tags that were burninated under this process

Some recent questions which we left comments on

Next steps

After carefully judging the feedback, I'll create a [meta-tag:faq-proposed] meta post so that the process can be maintained on Meta. That implements the request made earlier by Martin Smith

Possible concerns to be addressed by the community, moderators and SO staff

SOCVR is an activistic room that makes an impact in moderation on main.

  • Is its effect regarding burnination noticed, appreciated and warranted?
  • Should chat rooms be involved in burnination requests?
  • Should burnination requests be orchestrated at all?
  • Is the moderator team equipped to handle any extra workload caused by burninating?
  • Is the CM team still OK with this process, its implications and goals?

On behalf of the SOCVR RO team and regulars, I'm looking forward to your valuable feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment