-5

As far as I can see, there is just two tags containing "drupal." , and .

For the same reason has been blocked, which is to avoid users who don't know the tags to use start typing "dru" and the system autocompletes it with (which then takes questions to be tagged with when non necessary), also tags like , , and should be blocked.
The first tag doesn't follow the schema used for module tags, for which it has been used the short project name of the module (for Views is "views", and for Content Construction Kit is "cck"); the second tag is not necessary, as it is not being used for more questions than the ones that already use it.

5

You can probably afford to be reactionary here. If you see [drupal-waffles] being used on all sorts of questions that don't involve waffles, then fine - ask for a blacklist. But otherwise, trust that your users will have at least enough sense to recognize that their question, while most certainly about drupal, is only tangentially waffle-related.

Though obviously, don't go out of your way to prefix tags with drupal- if that isn't actually the proper name of the [library|concept|food] being asked about.

  • To that end, the proper name of the module in question is indeed Drupal Commerce, not Commerce. – user7 May 28 '11 at 7:18
2

It seems to me that you have the whole Version tags considered harmful discussion mixed up pretty well.

Jeff proposed

  • Eliminating the version tags on existing questions. We can do this in one click globally.
  • Treating version tags as the exception not the rule on new questions -- if you have a strong case to make that the question you are asking is ONLY relevant to one version and can NEVER EVER be relevant to any other version, then -- and only then -- add the version tag.
  • If you encounter an old question that is truly specific to a version, and cannot be edited to be version-agnostic, retag it with a version tag.

What he was basically saying was, it's a bad idea to have the most used tags contain "drupal" because people will use them and only them, instead of thinking what the question was about. He didn't want to ban the tag but limit it's use.

Now this ended up with the tag being renamed to numbers only, to avoid having them showing up in auto complete, which was pretty clever. However the point wasn't to disallow the phrase "drupal" in a tag.

The problem with drupal-version tags was that they were easy to put on any question, would be the most used tags. That combo would have the side effect that users wouldn't think about what their question was about but simply put and be done, instead of enriching the question with more and better meta data. or is not likely to have that effect.

  • They wont be the most used tag on the site
  • They have a specific meaning that doesn't apply to almost any question.
  • They describe the content very accurately.

Like I explained in the Why was the drupal-commerce tag nerfed question, commerce and drupal commerce are two complete separate things, which both have meaning in this site.

  • is something you should use if you ask a question about anything related to commerce
  • is something you should use for questions about the module.

In some cases you could tag questions with both, but in most cases you cant. The majority of drupal commerce questions is about the commerce API, a few listed below:

If you view these questions, it's pretty clear that these questions are not really about commerce, but how to do something with the module. To merge and tags would obfuscate it's meaning. If I want to see questions about commerce, I get all these API questions that I don't want to see and vice versa.

We used to have a tag called . This is a good example where drupal is redundant and should be removed. When talking about behaviors in a drupal context, people should know that it is related to the JS API.

So in sort, there is really no reason to go hay-wire over tags containing the name drupal, when that is the most sensible thing to call it. There are a few tags that fit this, and this is okay, since the alternative will bring a mess to the tag system.

  • See this answer by Robert Cartaino. @Jeff Atwood also reports that: "Version tags are redundant. The site is already called 'drupal.' We don't need to know that it's drupal-6, drupal-7, drupal-8, drupal-9 in every single tag on every single question. It's redundant." Both are saying that part of the problem with that tags is that they start with "drupal." Out of two existing tags, you can find a justification for a tag; what is about all the tags coming from Stack Overflow that contain "drupal-"? – kiamlaluno May 27 '11 at 17:21
  • 2
    @kia If I were to comment, I would only repeat myself. Try reading my post again, you are clearly missing something. – googletorp May 27 '11 at 17:46
  • You said "It seems to me that you have the whole Version tags considered harmful discussion mixed up pretty well," which is not true. The "redundant part" to which @Jeff Atwood is referring is having "drupal" in a tag for a Q&A site dedicated to Drupal; @Robert Cartaino then explains why having a tag starting with "drupal" was a bad idea. So, if "drupal-6" was a bad name for a tag (which is now simply "6"), why should "drupal-commerce" be any better? Why didn't @Jeff Atwood decide to keep "drupal-6" instead of blocking "drupal-6" and allowing "6" as tag? – kiamlaluno May 27 '11 at 17:53
  • 2
    @kia To keep it short: drupal-6 is a version tag. @Robert wrote ... whenever they started typing D-R-U-P… It pops up in the text completion so users say "oh, I must need a version tag!"... Because Drupal-6/7 is a version tag they will automatically be applied to any question. If the user starts typing D-R-U-P and they see drupal-commerce, drupal.org etc they wont think, WOOT a drupal-something tag I want to use that NOW!!!! version tags are special and needs to be treated differently. – googletorp May 27 '11 at 19:02
  • 1
    Actually, Jeff said explicitly (meta.drupal.stackexchange.com/questions/270/…) to use commerce instead of drupal-commerce. However in this case, as Mark Trapp mentioned, the project is actually called "Drupal Commerce", so the tag imho makes sense in this case. If it turns out to be a problem (questions are tagged incorrectly, we could use "commerce-module" or something like that. – Berdir May 29 '11 at 14:43

You must log in to answer this question.

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