10
\$\begingroup\$

Recently some others and I began to clean up a bit. This started with retagging a number of question with . Then we hit a wall. All of the questions that should have been retagged were, but we were left with 18 14 questions that didn't seem to have a better tag than the extremely generic "Google". Several questions can be cleaned up by replacing it with , but there are a number of questions that still just don't fit in any of our other 6 google tags (not including ).

As you can see by looking at the wiki, our Google tag is very broad and i can't imagine that it's very useful as it is. It's only real use is a catch all for something related to google in some general way. It's not very well defined. I think it should go, but we're then left with the question of what do we use to tag these questions. As I stated here, I think we have a couple of options.

  1. Leave alone. It's fine how it is. Retag what can be retagged and move on.
  2. Replace it with a more specific, but still kind of catch all, tag. This would give the benefit of specifically stating that this is code using one of Google's APIs and is not to be used for questions which are related to Google through it's second cousin's ex-college roommate and burn . This would leave some google related questions without a tag saying so.
  3. Burn and introduce more specific tags where applicable, as they are needed. Tags such as and .

I tend to lean toward a combination of options 2 and 3, but I'm putting it to the community. Let's clean this up before it gets more out of hand than it already is.

Updates:

\$\endgroup\$
6
\$\begingroup\$

Option 3: Burn and introduce more specific tags where applicable, as they are needed. Tags such as and .

\$\endgroup\$
  • \$\begingroup\$ After further review of the remaining google questions, I'm not sure we will need to introduce more than one or two new tags at this time. \$\endgroup\$ – RubberDuck Jul 26 '14 at 13:24
2
\$\begingroup\$

Option 2: Replace it with a more specific, but still kind of catch-all, tag and burn . This would give the benefit of specifically stating that this is code using one of Google's APIs and is not to be used for questions which are related to Google through its second cousin's ex-college roommate. This would leave some Google related questions without a tag saying so.

\$\endgroup\$
  • 2
    \$\begingroup\$ -1, Google has so many APIs that this would essentially be meaningless. If a generic tag like that is wanted, option 4 would probably be better (Google's APIs have nothing more in common with each other than APIs from other vendors). Option 3 sounds like the best approach to me. \$\endgroup\$ – Dagg Jul 25 '14 at 17:55
1
\$\begingroup\$

Option 4: Give no special treatment to Google. Introduce a generic tag such as , which could apply equally well to Twitter, Amazon, Vimeo — any well known service that provides a web API. That would remove the need for [google-drive-api] and [youtube-api] tags, for example.

For more interesting integrations, such as Google Chrome extensions, we could still have a tag.

\$\endgroup\$
  • 2
    \$\begingroup\$ I like this, but I question how useful it would be in practice. Someone may want to follow questions about Twitter, but not Amazon. \$\endgroup\$ – RubberDuck Jul 25 '14 at 5:04
-5
\$\begingroup\$

Option 1: Leave alone. It's fine how it is. Retag what can be retagged and move on.

\$\endgroup\$
  • 5
    \$\begingroup\$ The problem will only get worse, as it's only a matter of time before Google becomes synonymous with all computing. \$\endgroup\$ – 200_success Jul 25 '14 at 3:18

You must log in to answer this question.

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