What should we do? Nothing special.
Use xbmc for XMBC and kodi for Kodi.
People know what they're using (the branding has historically been quite strong)
It'll be a while before XBMC stops existing. It'll be in the Trusty repos until 2019.
The featureset of XBMC 12 and Kodi-latest will diversify as time rolls on. Keeping them separate helps us too.
This is the tag's wiki excerpt:
Questions about using the command-line interface (CLI).
And the only usage guideline from the tag's wiki is:
Questions using this tag might be related to Bash - the default command line shell in Ubuntu, Shell-Scripting and Programming.
That's not very restrictive, my take on it is that any question that is explicitly ...
While it smells an awful lot like a meta tag, I can certainly see the value:
It tells potential answerers what the user is looking for (a historical report).
It should be interesting for people to read through.
But like software-recommendations, it shouldn't be used alone; there should be other tags.
Anyway I'm looking forward to seeing what other people ...
glitch seems to be completely undescriptive as a tag.
We're limited to five tags per post. We should make them useful and descriptive so that people with expertise can find and answer those tagged questions. Nobody can be experienced in "glitch", so I'd say burn the tag.
No. Trash dev instead. It seems to be used as an abbreviation for two unrelated subjects:
devices (about 10)
development (about 5)
So, let's just trash the dev tag and retag the maybe even four real development questions. The use of dev for devices does not make sense to me. I do understand new users seeing /dev/sda and thinking 'dev' would be a nice tag......
You should absolutely remove irrelevant tags, wrong tags, add missing tags and anything else that makes the question better. Collaborative editing is a big part of the SE model and tags are not special.
So yes, please, correct any tagging issues you see!
Yes, the tag should be blacklisted.
I cannot see any useful use of the tag, so I propose that:
Community members go through the tag page and on relevant posts replace it with packages, package-management or debug, or other relevant tag.
After this is completed, all other uses of the bug tag are removed from posts where it is not relevant to use them.
We also have various windows tags as well as e.g. macosx, kali or debian although we do not support questions that are specific to those foreign operating systems.
Their main purpose are dual-boot questions where there are issues having both Ubuntu or one of its official flavours installed together, but other common use cases include questions about ...
We don't need these to be separate tags. setup should be made a synonym of installation.
installation does apply to things other than Ubuntu as a whole (I can install a program, which would be within the scope of that tag ...I can install more memory in my computer, which might not be within that scope.) But so can setup. I doubt we gain anything by having ...
I would definitely avoid adding a version tag just for the sake of having it.
Version tags can be dangerous if the community starts to believe that every question, no matter what, has to have a version tag.
Only version tag posts that provide at least some evidence they are in fact tied to a specific version of Ubuntu.
In addition to what Lekensteyn I use the following ideas myself:
If something changed a ton, like say unity, I tag those with the versions so that it's obvious which major release people are using, but I don't tag general stuff like apt, dpkg, or something like that.
Kernel/Hardware/Video stuff for sure since hardware detection is version specific there.
Besides what Oli said, the solution is to edit posts that use version tags incorrectly, adding other tags, and removing the version tags unless the question appears version-specific.
Many people will probably imitate the use of tags they see on the site. If we're good enough at editing questions to fix wrong use of version tags, we'll probably have fewer ...
Yes, and I believe version tags should be avoided as much as possible anyways. They make the question have a limited value.
I would even go as far as believing that removing versions from title and body is valid if those have nothing to do with the problem.
Only if it is apparent that the question is off topic (due to the version for instance) leave it ...
I would agree that the warning is pointless and while I don't follow specific tags personally I don't see warning as being useful to anyone. I support the idea of eliminating warning entirely and have managed to edit a few but ran out of time.
images is a poor tag name, not only because it does not define any specific task or software, but also because it has more than one distinct meaning, especially in our scope. A brief survey shows that this tag is being used for questions about images that are not pictures of stuff, for example
Mount single partition from image of entire disk (device)
This tag is in use and fully on topic, but remember your question should be specific and clear, see the software-recommendation tag info:
Questions asking for specific applications that perform a given task
or work with a given file format. Give details about the purpose
of the software you want and your minimum requirements for it.
You know what ...
Ahem, maybe not.
I don't think there's a lot we can do. They can be valuable tags to keep around but there's currently no feature which allows us to make sure somebody posts another tag. The best we can do is improve the short wiki text so that the description they see in the tag suggestion box tells them they shouldn't be using it on its ...
Well there is no doubt that both have a considerable overlap, both in meaning, and in usage. However taking them literally they are not really synonyms:
is a general purpose term which may include all, speakers, headphones, Bluetooth, sound system, pulseaudio, jacks, ... (long list).
should be restricted to the hardware, the chips that ...
While you raise a good point that version tags are massively overused on AU, there's nothing wrong with combining them with other tags.
If a question is about APT and the exact Ubuntu version doesn't matter, use only apt.
If a question is about APT and is only applicable to Ubuntu 14.04, use both apt and 14.04.
Generally speaking, use a version tag if and ...
No questions are linked to "unicorn".
So we can delete the tag wiki if required and then make it a synonym.
Seems like a perfect synonym for 14.10 - unlike "trusty" questions I would expect both "utopic" and "unicorn" questions popping up for obvious reasons.
For the moment I've unlinked the unicorn synonym. If you would like to make unicorn a synonym ...
I'll move my proposal from the comments to an answer so that people can vote on it.
I propose to rename it to desktop-files, because:
Having a leading dot makes sense only when referencing desktop files by their extension; since the tag has to change but the extension won't change, there's no reason to prepend a dot to whatever nomenclature we're gonna use,...
I'd say to reject the suggestion and to get rid of the tag.
Creating / editing a tag wiki excerpt for a tag that has no reason to exist puts the cart before the horse, and shouldn't be encouraged: much like useless edits it wastes reviewers' time for no benefit, since the tag is to be removed.
Let's blacklist the windows tag (prevent anyone from using it) because it's too ambiguous. Instead:
Use window-management for the 'GUI object' (instead of windows and window)
Use the already heavily used windows-xp, vista and windows-7 and don't let anyone tag with the generic "windows"