I propose that there be two (maybe three) levels of specificity. For instance:
blender-1 vs blender-2 (likely will rarely be used, if at all)
blender-2.4 vs blender-2.6 (huge changes in interface, inner structure, etc)
blender-2.66 vs blender-2.67 (new features present in one version and not earlier versions)
I would say that when tagging a question, the ...
There are currently questions here that use python but aren't directly related to scripting and there are sure to be more in the future.
Example: How to make Blender use Python2.x?
Also see my answer to a similar question
You can't directly delete a tag. The process to remove one (not having it appear as a suggestion) is that you untag it from any question(s) that it was attached to and the system will remove it after a while.
IIRC.. the tag script runs daily so any orphaned tags (those not attached to a question) will automatically be removed provided no one uses it in that ...
I agree it is misleading to an extent. blender-render is a good rename/synonym since that's what it is labelled inside Blender. I went ahead and merged these and also added internal-render as a synonym as well. This should no doubt prevent any future accidental use.
We definitively need these tags, the more exact a search result can be narrowed down, the better. Some would argue that all of those tags could be ignored and simply tagged Modeling.
from the basic description of all tags
A tag is a keyword or label that categorizes your question with other, similar questions. Using the right tags makes it easier for ...
No. Tags describe the question. Just because you use X in your answer does not mean the question is about X, nor should it be tagged X.
Should we retag questions with topics proposed in the answers?
Take your example question for instance. Say you added the animation-nodes tag, now I come along (knowing almost nothing about AN) thus I skip over that ...
NO, no, no and no. It is a useless categorization for BSE. A of donut tells us nothing about the question, except that the OP is probably following Price's tutorial - not really helpful for us. Each tag should be able to tell us what the question is about, (examples: modifiers, rendering, animation) not how the OP got to the point of asking that question.
I agree with you, lets do it.
The main arguments I'm aware of against having a version tags are:
It's messy. Almost every question on the site is eligible for one of these tags.
Yes, perhaps having the same tag on nearly every question from now until 2.9 releases sometime in 2 or 4 years seems silly, but I think the improved search-ability is worth it. ...
The tool tag has been removed from the questions they were assigned. Tags with no questions are soon removed completely. If you see them pop up again, flag one of the questions for moderator attention. This becomes less of a problem after the private beta, when the rep requirements to create new tags is increased: https://blender.stackexchange.com/faq#...
More than likely, for tags like these there already exists another with which it can correlate to bring across its meaning or the scope of the question.
For example, mirror as you used it could have modifiers, materials or modeling to go along with it. In a worst case scenario we could have a question that entails all 3 (or more) like;
Q: Why does the ...
I'm always in favor of more specific tags. So if the question base is there to warrant a new tag, then by all means add it. I do wonder if it is realy needed at this point (I'm the one, nearly a year ago now, that removed the yafaray tag), Luxrender only has 8 questions, Yafaray has 4, etc.
There are other question groups, with many more questions that are ...
Whether something is off-topic or not will be filtered naturally through voting habits. I suppose we will see soon enough how many degrees of separation will be considered appropriate by the community.
There will be instances where it is useful to include a platform tag, because platforms can have different behaviours. Think of keyboard shortcuts, path ...
This sounds good to me, as long as we decide what these should be beforehand.
We've already had a good number of these kinds of questions:
Resource for Blender addons?
non-video blender resources?
Blender resources for architects?
Any good free materials libraries online?
Where are some places to get reference images for modeling?
I'm not quite sure about ...
See Should 'scripting' and 'Python' be made tag synonyms?
In addition, here is my interpretation of the differences:
scripting is for questions involving automation of tasks via scripts.
These could be shell scripts calling blender with various options, or python scripts running within blender.
I've also seen this tag used for osl when ...
Speaking just about the linked question, yes you absolutely could of edited out the cycles tag (I went and did it). That question has noting to do with any rendering, it is a modeling question.
Now when a question is closed as a dup, even when it was gold tag closed, you editing the question will not change that. (Except in some cases it will go through the ...
Look at the google quick answer box for both "caustics" and "prism."
While they both are about rendering light based effects, that is where the similarity ends.
No I would not include prisms in the caustics tag, nor synonymize them.
If you feel we need a tag for prismatic effects, then I'd normally say just create a new prism tag (even though I think that ...
It might be useful for initial questions, if someone is really new to UV they might be looking for terminology rather than complete answers. Usually once someone learns terminology that opens up a new world of search terms. I say keep it as it can always be retagged to be more specific.
Hover over the tag and read its description.
Discussion questions are the heart of your community. For example:
Should a certain question be allowed on the site? For what reason did
a moderator lock a certain question? Are said actions setting a
precedent? Be sure to present your entire case and background
information/data so the subject can be ...
The only times these won't be accepted is if they are directly copied from the wiki. There is a reject reason for these type of edits that says:
This edit plagiarizes content from an external source without proper attribution.
So, it is perfectly fine to copy and or modify these provided that you link to the original source and cite as you think ...
If you can produce higher quality content that's great. If not quoting is fine as long as you remember to include a link to the source. Forking is stongly discouraged. Improvements should be made to the Blender wiki before quoting.