Skip to content

Instantly share code, notes, and snippets.

@rschrieken
Last active September 16, 2015 18:22
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save rschrieken/9e6a49e5dde6d1010944 to your computer and use it in GitHub Desktop.
Save rschrieken/9e6a49e5dde6d1010944 to your computer and use it in GitHub Desktop.
Tags in need of constant attention

The main problem is that users, especially new users, doesn't seem to read or at least have the habit to dismiss any blocking dialog you put in their face to keep them from achieving what they're up to.

I don't like the idea of secondary tags (or any kind of tag hierarchy for that matter) because it rules out any other use of such tags.

I do like the feature of tag assistants and maybe one feature request could be to show one when a tag is added if the tag excerpt starts with DO NOT USE.

One other option might be to throw posts that contain do not use tags in the triage/first posts queue no matter what, with an indicator on it about the suspicous tag. The outcome of the review will either be a better tag (due to retagging) or extra close votes/flags.

I noticed that some of the excerpts are very clear about the wrong use of the tag. For example [tag:windows]:

Windows is a family of client, server, and mobile operating systems developed by Microsoft. Use this tag only if your question relates to using Windows APIs or Windows-specific behavior. Questions relating to using or troubleshooting Windows are off-topic.

why not:

Do not use this tag for questions about using or troubleshooting Windows, those are off-topic. Windows is a family of client, server, and mobile operating systems developed by Microsoft. Use this tag only if your question relates to using Windows APIs or Windows-specific programming behavior.

These kind of measures will help in fixing the pr0blam up-front.

Leaves us with a bunch of question in low-traffic tags that gather low-quality off-topic stuff over time.

Apart from attracting more users to regularly [close/down] vote in that tag we could have a specific Close Vote Event. A name for these events can be CV support-hungry tags but not everybody is convinced yet that this should be a regular event. But I'm open to give it a test run if my fellow room owners agree.

If have this query that can be used as a tag feed for those events but none of the tags mentioned by you seem to come forward. Otherwise we call the tags out individually.

@durron597
Copy link

  1. specially is not a word, I think you mean especially.
  2. Except from... should be:
    • Apart from attracting more users to regularly [close/down] vote in that tag**,** I propose
  3. I vehemently support the idea of automatically triaging questions with bad tags.
  4. I sort of feel like having events for these high crappiness volume tags would detract from our burnination efforts and would probably kill the original Closey concept, given that we already take a lot of votes away from these tags for burnination efforts.
  5. If you have doubts about that query, can you explain what they are?

@gunr2171
Copy link

I'm going to have to super update Closey to deal with that ramp-up of activity.

Having a weekly close event is great (what we currently do), but it might be a problem with >10 people. Coordinating that many people will be a bit of a challenge (flood the chat room) and I'm afraid that the percentage of "leave open" votes will drop to 0.

I do like the ideas about the "do not use" tags in paragraphs 3 and 4.

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