How to deal with tags the are related to a extension developing companies?
I'd only agree with M2E tags because this is a very unique extension that is widely used.
My take on these is:
I agree with @fabian answer. Along with that, I would love to mention my view on this.
I think we should not allow questions which are related to non-open source extensions. This is because the source code is not available to the community and most of the cases, the question is going to remain unanswered. There can be exception for this if the extension is widely popular among the community and the OP provided sufficient codes to look into the specific issue.
In the case of open source extension, my opinion is we should allow such questions here. But it would be better if we can keep them inside a general tags such as m2-3rd-party-extension instead of creating separate tags for each extensions. This is because the list may grow widely after some time. If we are keeping separate tags, then we should provide the source code link in the description of the tag.
My opinion on this is formed by asking, how is this beneficial?
If we look at tags, then we see that it has three main benefits:
Another one is that you could earn tag-badges.
Am I right?
Now, having a specific tag for a specific third party module, is that going to help any user on the above? One conclusion that comes back on these discussions about tags is that tags shouldn't be too specific.
As example, if we look at iwd-onepage-checkout this is not really helpful. I would suggest to see if there are broader more generic topics that can be described as tag: onepage-checkout in general or checkout
Every third party module implements a certain functionality, so let's have those as a tag instead of the vendor name or the module name.