5

Instead of removing all of the tags identified in my answer to this meta post, I'm considering putting in a tag burn and blacklist request to remove the following tags completely from our site:

These are the worst of the worst when it comes to tags. Every question could arguably be about a project management problem. It's why people come see us. Best practices are really what everyone strives for, and project manager and project are very "meta", as the site is about project management.

I plan to submit the blacklist request to Stack Exchange by next Wednesday, September 18th, so if anyone wants to go through these tags and edit any of the questions or retag them, this is a good opportunity to do so. When Stack Exchange blacklists a tag, the tag is removed from all questions, and questions where that was the only tag get a special tag, until someone retags the question.

3
  • I agree. However I have doubts about common-project-problems. It has many questions tagged under it (I know this is not a valid reason). Also, what tag(s) to use for posts like What are the biggest mistakes that new project managers make? Sep 13, 2013 at 13:36
  • 1
    @AzizShaikh - Your question is sort of why I wanted to go through all the questions. That particular example needs to be closed (not deleted, just closed). We don't want to compile a list of mistakes in one massive post; instead, we want thousands of laser-focused questions that each focus on a different problem because that's what draws experts. Biggest mistakes is sort of a place for the inexperienced or mildly curious to hang out. It's not an example of a good, on-topic question for our site.
    – jmort253
    Sep 13, 2013 at 13:50
  • 1
    And think about "common project problems". What is a common problem? How does one tell the difference between that and an uncommon problem? I've stared at this tag for a long time and still can't tell you what that tag is actually about. We can definitely do a better job retagging the 102 questions that currently hold that meta tag. Please see The Death of Meta Tags for more details. Hope this helps! :)
    – jmort253
    Sep 13, 2013 at 13:52

2 Answers 2

3

Okay. That .. took a hot second, but it's done. Those tags have been destroyed, and blacklisted along with their plurals. I've also added the intrinsic tag blacklist for , which was missing, but thankfully not problematic.

This resulted in more than a few untagged questions, some of which look pretty smelly, so please have a peek at them and re-tag what's valuable while disposing of what isn't.

Thanks for keeping the place clean!

2

I'm in favor of purging those tags as being "too meta." This morning, I took a stab at removing/replacing from a number of posts, but it's not a trivial exercise.

I have no objection to having the SE administrators simply purge the tags, but we also have the ability as a community to retag them as we go. The first is easier on us, obviously, but we still have a path forward if they say "no."

Please do submit the request, and let us know how it goes. In the meantime, I will continue to retag as time and energy permit.

2

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .
https://pm.meta.stackexchange.com/questions/620/planned-tag-blacklist-request
pm.meta.stackexchange.com
crawl=CC-MAIN-2022-21
118520
application/http; msgtype=response
sha1:SQ2ZYQ6653LFQZSTM57LEZUSCERRZK7E
<urn:uuid:0bb4b449-9cf7-400a-aeed-eb1c9ef19ddf>
2022-05-25T09:36:12Z
151.101.129.69
text/html
sha1:SGP6QY5CX4HGLQBMOMGHIZWQJ6WKKYMT
<urn:uuid:ff4ff0aa-1792-406e-9085-72eb349e04ef>
https://pm.meta.stackexchange.com/questions/620/planned-tag-blacklist-request
response
<urn:uuid:b2ac17d4-45d7-4560-a989-06728c906ed3>
isPartOf: CC-MAIN-2022-21
publisher: Common Crawl
description: Wide crawl of the web for May 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-141
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/