Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Every retag request (and re-request) takes another Q&A post which clutters up meta with a very short-lived and repetitive process.

Would it be better to create a generic retag request "question" and add a new answer for each specific request? Answer voting can take care of opinions and comments can take care of what little meta discussion might be needed for each request.

As the "retag question" becomes too long to effectively manage, it can be closed as "no longer relevant" and a new one created (monthly?, periodically?).


share|improve this question
It would be better, if we got that tag black list, so the mods do not need to do it again and again and again! (Why do I have the feeling that I've written something similar not long ago? After watching Matrix déjà vus frighten me...) – Ladybug Killer Dec 23 '09 at 15:12
Agree it would be better. My "suggestion" was in the context of the framework we have to work with today. – Robert Cartaino Dec 23 '09 at 15:32
up vote 7 down vote accepted

There used to be an old dog by the name of The Great Tagging Reorg. It would be one massive canine where each of the answers were requests.

But then, it was put down in order for other puppies to run and have their individual say:

Please add new requests as new items, tagged with the site, for example:

Reason being that it got so long in the tooth that it was becoming something of a right old mess keeping up and checking the status of retag requests.

Guess the individual retag requests were easier to pin down and class as [status-completed] while at the same time allowing for more actual scrutiny/discussion on the individual tags.

share|improve this answer
I can't tell from that post why it wasn't effective or why it was closed/locked. – Robert Cartaino Dec 23 '09 at 14:54
It got messy. That's pretty much it. – random Dec 23 '09 at 15:10
Fair enough. That was an attempt at massive re-org. But now that it's "done" and requests are a bit more routine, I was thinking a single thread might be a better mechanism. – Robert Cartaino Dec 23 '09 at 15:27
As requests are completed, the answer can be deleted to keep the content of the thread to outstanding requests only. – Robert Cartaino Dec 23 '09 at 15:28

To put more context on @random's random answer; indeed, it simply doesn't "work" (IMO) as a single discussion. With separate questions it can be discussed and tracked separately, and I can see the pending queue easily.

With the individual question, it quickly became impossible to see new posts, or even properly track requests that were known about.

They aren't high volume, so IMO it isn't worth trying to "fix" anything here.

share|improve this answer
The status-completed becomes status-we-need-another-retag in about a week. – alex Dec 25 '09 at 0:11
Sounds reasonable. – Robert Cartaino Dec 25 '09 at 17:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .