"meta-tags" would cause too much confusion with the Metatags module. – MPD♦
meta-tags is over a year old. If it's really confusing, it should be renamed, probably with an alias left under its original name.
"meta-tags" would cause too much confusion with the Metatags module. – MPD♦
meta-tags is over a year old. If it's really confusing, it should be renamed, probably with an alias left under its original name.
Meta tags is the term that is usually used for those tags. The fact it is common for Drupal modules to adopt as name usual common doesn't mean the common term in Drupal mean the module. If all, a new tag should be used for the questions that are specific for the module, if necessity will be raised.
So far, we don't have nodes for questions about nodes, and node.module for the setting pages used by the Node module; in the same way, we don't have views and views.module, or feeds and feeds.module.
In Drupal there is always a module to handle an entity. Using nodes and node.module would require to analyze the question and see if the question is about the setting pages provided by the module, or about the entity implemented by the module. (I am giving to entity a more generic meaning, not specific to Drupal.) It seems an arbitrary distinction, since a question about views is always a question about the Views module, and a question about nodes is always a question related to the Node module.
Having a tag for the module and a tag for the entity handled by the module would probably increase the confusion to users, who would not understand why there are two tags. I would also consider users already used to Stack Overflow's tags, where there isn't a tag for the Views module and a tag for views.