6

I was approving edits in the Suggested Edits queue while I came across this:

https://opensource.stackexchange.com/review/suggested-edits/268

I approved it due to the description, we have a new tag. However, with a significant lack of tag wikis (For those of you who contribute, I applaud you), it's hard to tell the rationale for the tag creation, as well as what we should do with the tags.

So Meta! What's the difference and why should we use each one?

4
  • For everyone else's reference, I had no idea if the others should be removed, but I knew that license-compatibility was in existence and would be good.
    – HDE 226868
    Commented Jun 26, 2015 at 1:04
  • 4
    Yeah, I would prefer license-compatibility over compatibility. It's much more clear.
    – Zizouz212
    Commented Jun 26, 2015 at 1:04
  • 1
    If a tag basically requires another tag it's generally better to hyphenate them. In this case I think it's better to have license-compatiblity than license and compatibility. Commented Jun 26, 2015 at 1:05
  • Oh no! I forgot the pun. Someone! Think of one quickly!
    – Zizouz212
    Commented Jun 26, 2015 at 1:15

1 Answer 1

6

We should only use

Out of the currently 4 questions tagged with one or both of these tags, none of them is about anything other than license compatibility. Out of the two tags, reflects this better/more clearly. There is likely no use-case for , and if there were, it would be confusing to have these questions under the same tag as license compatibility questions.

I would suggest burninating .

3
  • I agree with re-tagging questions. However, I think we should take compatibility and see if there are other instances or categories to place it within, as we attempt to test the limits of the site's scope.
    – Zizouz212
    Commented Jun 26, 2015 at 1:14
  • @Zizouz212 if the necessity arises, it can be recreated.
    – overactor
    Commented Jun 26, 2015 at 1:15
  • 2
    Some people may not think to type "license-compatibility", but this does not matter since anyone typing "compatibility" as a tag will see "license-compatibility" as a suggestion. So there is no need to have "compatibility" as a back up tag. Commented Jun 26, 2015 at 10:19

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .