21

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.


20

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 ...


14

Yes.


11

I believe review-audits is a better tag name than audits. The main reason is what you say: it is less ambiguous. But there is another, minor reason. review-audits will be easier to find and, for users who are less familiar with meta, easier to apply. This is because its name contains both "review" and "audits". When askers are typing into ...


9

I have reversed the synonym. ati is now a synonym of amd-graphics. I left amd unsynonymised since it is also a CPU brand and we have intel and intel-graphics.


9

I vote that we make hdpi a synonym of hidpi, as the latter is easier to read and seems to be the "official" name, at least according to the Arch Wiki and regular Google search results. Note the related queries on Google Trends. From that data itself, we can easily say that "HDPI" refers to mobile displays while "HiDPI" is used for computers. As we aren't ...


9

We don't seem to have tags like that for other Ubuntu release numbers. No ubuntu-16.04, for example, just 16.04. Since there were only two questions tagged ubuntu-17.10, I've just retagged them to 17.10. The system will remove the tag after a while if it is not applied to any more questions. If it comes back and people start using it on multiple posts, I'd ...


9

Update: synonyms were added. Thanks to everyone who voted Considering that the tag multiple-monitors has 3096 questions tagged right now, we may want to make all of those synonyms of this tag. Back to the topic.Ubuntu Wiki articule and Arch Wiki article on this topic use "Multihead" and "multi-monitor" terminology. Gentoo Wiki as well. So these two are ...


9

I agree. Some even have both; seems overkill to me. And it is 767 :=)


8

And it's done. I renamed the only question with retina to retina-display.


8

Here are a my personal principles: I prefer a tag too much, rather than one too little. Better too much information, than too little. I am strongly against removing redundant tags from questions. Redundancy serves a purpose and hence I prefer to keep the command-line tag for past questions where it is relevant. Tags should be edited if they are wrong. That ...


8

It's not "bash" on Windows. You can get dash on Windows, or zsh on windows, or Xorg on Windows. The whole "bash on windows" was more evidence to one of the three problems all programmers have: off by one errors and a less-than-passable naming sense. Just saying "bash on Windows" opens a host of problems that we shouldn't have, like generic bash problems ...


8

I don't think either of those tags are useful. We want tags to be used consistently to define the subject of questions, IMHO. The usage guidance for record currently says: Questions about software for recording audio and video with Ubuntu. Of the 98 questions with this tag, only this one is not about recording audio, video or the desktop, or some user ...


8

There are commands that are unsafe (variations on chmod and rm come to mind) but not exactly insecure (they don't expose the system to an attacker). So perhaps not really a synonym. However, the tag is vague and could be used for all kinds of randomness. I can't think of a situation when it would help to define the subject of a question. I think we should ...


8

This seems like a reasonable request. If you were confused by this, presumably others might be as well. I've now created the soft-link as a synonym of symlink. If you now try to tag something with soft-link, it will be tagged with symbolic-link.


7

Why not delete both of them instead? Neither debug nor debugging give any useful information. In fact, they seem like prime examples of meta tags. For those who don't know, meta-tags are tags that Can’t work as the only tag on a question. Commonly mean different things to different people. If I see a question tagged with debugging, what do I know? That ...


7

I propose that we merge shell-scripts as well. shell-scripts by itself is not much more specific than the others. Most, if not all, scripts contain some amount of code run by another language: Awk, Perl, python, to name a common few. We should just additionally tag with the target shell, instead: bash. After all, if the user wants a csh script, they will tag ...


7

This is done. I have remapped scripting and shell-scripting to scripts.


7

These tags are getting too confusing and pedantic, we should: Rename snap-package to snap, easy to remember and covers everything from the snaps themselves to snapcraft, this allows the core team to subscribe to just one tag so they can answer questions. Alias snapcraft to snap. Leave snappy aliased to ubuntu-core, which is a pure snappy system.


7

I'm not in favour of this. The command names of cp and mv are sufficiently different from their actions (copy, move) that the -command suffix is not needed to make it unambiguous. But this is not true for cut, where an action has the same name as the command. This also holds for watch. I do a fair bit of retag edits and I have seen plenty of people just use ...


6

Done. Merged secure-delete into secure-erase and created a synonym between the two. updating post history, 12 rows affected (pipe delimited) updating posts, 11 rows affected (pipe delimited) updating PostTags associations, 10 rows affected updating Documentation tag proposal commitments, 0 rows affected removing/renaming old tag, 0 rows affected updating ...


6

vi and vim are two different applications that share the same name. By default, Ubuntu ships with vim-tiny, which does not have the same full feature set of true vim. The tags are similar, yes, but they are not synonyms. Questions about vi very much do apply to vim as well, but questions about vim do not apply to vi.


6

This answer from muru on another tag change/merge proposal posted around the same time is also relevant here, as the same reasoning is also applied to the watch tag in their answer/reasoning: I'm not in favour of this. The command names of cp and mv are sufficiently different from their actions (copy, move) that the -command suffix is not needed to make ...


5

I don't see any reason for moving a group of questions about a specific topic (software uninstallation) into a more general category (the uninstall tag). If your goal is to make a more fitting tag for those questions about the uninstallation of software, retag them as software-uninstall if they're tagged uninstall, if they all can't be merged.


5

Yes, that's a good spot. I have merged the gpg posts into gnupg.


5

Yes, php-5.4 should be a synonym of php5 which should be a synonym of php


5

Tada! updating post history, 31 rows affected (pipe delimited) updating posts, 24 rows affected (pipe delimited) updating PostTags associations, 23 rows affected updating Documentation tag proposal commitments, 0 rows affected removing/renaming old tag, 0 rows affected updating count for master tag, new count: 12944 tag remapping of [boot] and [bootup] ...


5

If any action is taken, .bashrc should be made a synonym of bashrc, not of bash. It's true that we don't need a separate tag .bashrc. That tag is hardly used (surely some question has at some point in its life had that tag, since that's how tags are created). But the reason we don't need it is that we have bashrc, which is extensively used. Currently it ...


5

I've merged squid3 into squid and created a squid3->squid synonym. Any new question tagged with squid3 will be tagged with squid instead.


5

I'm not really comfortable with the idea of merging top-bar with panel. Here's why: "Top bar" in the context of GNOME 3 means something specific (analogous to menu-bar in Unity), not exactly same as "panel" as in GNOME 2 or others DEs like MATE, KDE etc. Why are they different? Panels are mostly very easily customisable and can be handled intuitively, ...


Only top voted, non community-wiki answers of a minimum length are eligible