5

I don't see any harm in doing so. Hopefully users will think twice when adding the tag. +1


4

I agree with the action being taken; however, I do not believe that the meta discussion constituted a mandate for that action. 99% of the discussion (and answer up-votes) related to the question of scope. While one question (with 2 net upvotes, compared to 10, 9, 8, and 3 net upvotes for the other more highly-voted questions) indicated support for the "...


4

I spend bugger-all time on this site, and when I do, I go looking for questions that the experts can't/won't answer because they're outside their specific domains of expertise -- such as Gravity Forms, WooCommerce, and WP e-Commerce -- or because they have a bias against them due to poor treatment from the vendors of those plugins. Right now, I can't easily ...


4

I'd suggest it should be very dependent on the nature of the tag and of the questions within. Simply throwing together all the plugin-related tags are going to make questions less browseable. As mentioned by @toscho, plugin-related questions will still be asked. Why not keep the system we already have to keep questions organized (more or less)? If there are ...


3

Less is better. I like your first idea with just two tags. Most are not sure what tag to use, no matter what we try. Having less tags makes that easier. I can do that, but it'll be quite some work that needs to be handled very carefully. And more important, it needs the support of the active community members, so please raise your concerns now, or show ...


3

Upon further reflection, I think this tag synonym should be reverted, for two reasons: 1) It prevents the use of the WPSE ignore feature, since ignoring the woocommerce tag forces ignoring of the synonym tag, plugins 2) It is inconsistent. Other Plugins retain their tags, e.g.: plugin-gravity-forms, advanced-custom-fields, and similarly, genesis-theme-...


2

For me, out of the list of terms given, the ones that should not be there are translation, language, l10n, po and mo. translation is the process of producing text in different language which wordpress has nothing to do with, the rest are just not meaningful. textdomain is a technical term used as part of localization so it should stay, localization ...


2

I like the idea of two tags only, but I would opt for textdomain in stead of translation. The reason for this is that more serious developers, whom I see as our core users, will use textdomain to describe the development issue they are addressing. translation is a colloquial synonym, but not the correct WP term.


1

I have renamed the tag to wordpress.com-hosting. I think it would be good to revisit this in a few months to see if this has had the desired effect of changing behaviour. If not I believe the dual tag approach suggested in the comments is a good avenue to explore for follow ups


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