Just want to seek clarification on how checkout should be used. As the way it is now, some are using it for payment while others are using it in a version control context. If there are more appropriate tags that should be used for either scenarios, feel free to suggest those as well.
1 Answer
Well, at the risk of sounding obvious, you could just leave it the way it is.
It's highly likely that questions having to do with version control will also have a tag that ties it to version control, like git or svn. You can find all of the git checkout questions using this search, for example.
Similarly, those questions that have to do with web development will have tags like magento, google and paypal In fact, this search, which excludes all of the major source control systems, will get most of those.
I don't think we need to change the tag at all. The concept is already so specific that separating them into different types of "checkout" will just make them too localized. and you'll have to ban checkout to keep people from using it (it's a naturally-occurring tag).
-
Is there a precedent for this? For now, I would still regard it as a workaround until there exist proper split candidates. Also (and fairly obvious as well), retagging is better done when there are only 400 entries– prusswanMar 1, 2012 at 6:31
-
1Only common sense. The tagging system has never required every tag to be absolutely unambiguous.– user102937Mar 1, 2012 at 6:31
-
2There are countless examples of this if you look around, @prusswan. Consider templates - this has a very specific meaning paired with C++, and a rather different meaning with, say, Django. Sure, it works better when there's a clear underlying commonality, as is the case with tags like regex - but even then, you gotta accept that another tag is probably necessary in order for you to know exactly what it's referring to.– Shog9Mar 1, 2012 at 6:50