The usual guidelines about tags suggest to use tags that:
don't say anything about the user who is asking the question
describe a specific area of expertise
For example, beginner is a tag that describes the user who asks the question, not the question itself. error doesn't describe a specific area of Drupal expertise. Differently, views describes a ...
I think that questions about using Twig in Drupal are different enough from general theming to warrant removing the tag synonym. Based on the Twig-related questions I have read, most were about "how can I do this Drupal thing in Twig (eg, absolute links)" and not "how do I iterate in Twig" or "how do I style this Twig output".
While Twig is most closely ...
No, I do not think we need explicit tags for database backends.
One, I think the current database tag is sufficient here. There really is very little in Drupal that is database specific, and internals questions (like the one you referenced) are more about the implementation of the Database API.
My biggest fear is that people will start using database tags ...
The moderators brought this question to my attention. While I don't think the action proposed in the question is productive, I do think it's worth talking about openly.
If I'm reading you correctly, you are concerned that the moderators are overriding the will of the people by ignoring the score on meta answers. As it happens, I had a similar concern ...
As much as I agreed with this in the beginning I disagree with it now. I changed my mind. I was blinded somehow by the maybe drastic wording that introduced the "changes".
Discouragement sounds like a drastic word, I think. "The use
of version tags is discouraged." Ay ay ay. But in the end - if I understand it right now - all this is about is that we are ...
My vote is to nuke it altogether.
http-headers would be more appropriate a tag for http-header specific questions, and the concept of headers in an HTML page (whether that's <head> or HTML5 <header> tags) is too abstract to warrant its own tag here.
If this gets support I'll nuke it later on.
Instead of making the two tags synonym, I have deleted them, since I agree with MPD.
I don't think we have users who answer questions about warning messages, and just to those questions. The fact then that some code is causing an warning message is not so relevant for answering to need its own tag.
Bootstrap framework is no longer associated with Twitter so tightly as it used to be, it's no longer called "Twitter Bootstrap" in their own documentation, so including twitter in tag seems pointless. On SO it is used only for consistency with twitter-bootstrap-2 tag.
For the need of the tag itself, I do not think it's needed:
Questions that are really ...
You are on the unanswered tab.
If you click on newest, you will see the count says 76.
Keep in mind that the tag tab you visit is remembered for every tag you visit. So, if you visit https://drupal.stackexchange.com/questions/tagged/7?sort=unanswered&pageSize=50 and then https://drupal.stackexchange.com/questions/tagged/views, you will still ...
Your original question isn't actually about HTML5 (or Drupal actually, it's about a relative path issue), you just happen to be using an element that wasn't available before that version.
I don't think adding a tag is a good idea since it doesn't apply to the question. If there are (let's say) half-a-dozen or more other questions that are clearly about ...
The rule on Stack Exchange is that tags say something about the question, not the user who ask the question; that is the reason why tags like beginner, newbye, or i-am-in-troubles are not acceptable.
The usual answer is that everything about a user should be reported in the profile; that is why a signature is not welcome on Stack Exchange: If you want to ...
Why does 'only tagging a question' always result in a 'rejected edit'?
AFAIK, there is no site rule that reviewers should always reject 'only tagging a question' edits. However, one of the preset grounds for rejection is that the edit is not "substantial" enough, and it may be that a number of reviewers feel that only adding a tag falls in that category.
I don't think we should create the tag. Essentially, because we actually have a specific close reason for that type of question
Questions on programming, PHP, SQL, etc. that do not relate directly to Drupal are off-topic here, but can be asked on Stack Overflow.
HTML would fit nicely into that list, as would HTML5. If a question really is about html 5, ...
From my point of view, this distinction is bad in itself.
Builders want to install a module to solve a problem
But if there isn't any, why should we limit answer to "cannot do", when thing is perfectly doable with some coding?
Developers can just build one
But really, why should they? It would be better use of their time to join efforts with ...
I don't think this tag is needed, or would be beneficial for the site.
A good question can have multiple correct answers. Very often, a question can be solved both by custom code (ie, using the Drupal API), and a well-worn contrib module. In these cases, both answers would benefit future readers.
When you mark an answer as accepted, it really doesn't ...
I strongly oppose community-based tags. Or any other way of making some group of users (or their content) stand out*.
I'm here to help Drupal community, and to get help from it. That's the only community I expect and want to see here. Introducing divisions will only make some people feel treated better or worse than others.
The grass is always greener on ...
That is how Stack Exchange works: When the question is older than X months, you keep the reputation you gained from your answer's votes, when the question is deleted. (The same is true for the question that still gives reputation to the OP even when the question is deleted and it X months old.)
That is not true for the tag score, though.
For brevity's sake, I think all tags should read for tag X:
This tag is for questions regarding Drupal X specifically. Version
tags should be used only when strictly necessary, for questions that
apply to Drupal X only, and not to merely say "I am using Drupal X in
The wording for the D8 is confusing (2x negative) & superfluous (we ...
Since the tag was used for two different purposes, I went ahead and removed it from the question using it.
Probably the same thing should be done for footer. Even though the tag is used with a single purpose, probably it should be replaced with regions or removed altogether. If the tag was used to mean hook_footer(), better tags would be hooks and hook-...
Some questions can be version independent. Well, most questions that does not depend on actual api should be version independent. And if question have different answers for different versions, nothing prevents posting them all.
Mechanism detecting phrases like "Drupal 7" in body or title and suggesting appropriate tags would be nice, but I think we may do ...
I have fixed the tags. Now there are two tags:
Upgrading a module/site is different than updating it; the first is generally a more complex operation, and often the more problematic one.
Users who answer updates questions could not be prepared to answer upgrades questions; users who are checking if somebody had their same upgrading problem ...
People don't put that much thought into tagging and this SE site isn't big enough to utilize tagging like SO (e.g. filtering new questions that I only have interest/knowledge in). Further, Drupal is filled with many overloaded, abstract terms (e.g. node, view) that are destined to be mis-tagged. I say a good rule of thumb is to glance at a project's ...
Just remove the tag from the question. The tag itself will be deleted in 24 hours, if there aren't any questions using it. If the tag is used from a question, it will be deleted in a month (if I recall correctly).
If you find more questions using the tag you created, just remove it, or replace it with the correct tag.
In How do we want to handle questions with radically different answers for Drupal 7 (and lower) and Drupal 8 (and higher)?, we solicited thoughts on how we as a community want to handle the fact that some questions here can have radically different approaches depending on the version of Drupal being used, especially in Drupal 8.
Voting results for the ...
As with other privilege to create something Stack Exchange has, the create new tags privilege doesn't mean users can create any tags they want, in the same way the privilege of asking new questions doesn't mean users can ask any questions they want; in fact, there are closing reasons for questions that are not desirable in a site.
The privilege name is ...