5

How to deal with tags the are related to a extension developing companies?

Some used ...

I'd only agree with M2E tags because this is a very unique extension that is widely used.

| |
  • 2
    I think as we are not allow to do marketing via this tags, then we should delete this tags – Murtuza Zabuawala Mar 5 '18 at 5:51
8

My take on these is:

  • if they are used as synonym for one extension (e.g. for their onepage checkout, rename the tag accordingly, like . In the past, moderator decision was to not allow extension tags at all (see: Do We Really Need Third Party Extension Related Tags?), so if this still holds true it means delete the tag. But at that time we were more strict about third party extension questions, so maybe this could be re-evaluated.
  • if the company is equal to the product or is a third party service that can be integrated in Magento (algolia, m2e, sagepay), it's clear, so no renaming is necessary. Again, if the tags should be allowed at all, that's a different question. I would allow them because I don't consider questions about these topics automatically off topic.
  • I can't think of on topic questions about an extension company that are not about a specific extension and would deserve an own tag for the company (e.g. would be a tag I'd just delete)
| |
5

I agree with @fabian answer. Along with that, I would love to mention my view on this.

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

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

| |
  • We already have the tag "extensions" (also "third-party-module" but that one did not receive much popularity), IMHO this should be enough, the tag landscape here is already too fragmented. I don't see benefit in "m2" specific tags as the Magento version is almost always already in the tags. Before introducing a new tag, the question should be, if anybody will likely look actively for questions of this tag. – Fabian Schmengler Mar 7 '18 at 12:09
  • Great, if extensions available, then we can use it. I put the other tag name here only to tell the tag name should be generic. – Rajeev K Tomy Mar 7 '18 at 12:12
3

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:

  1. it can be used in search, combining tags and keywords
  2. users that are interested in these topics can set the tags as favorite
  3. related questions get properly linked

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 this is not really helpful. I would suggest to see if there are broader more generic topics that can be described as tag: in general or

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.

| |
  • Functionality name is okay with tag, I think problem with just vendor name – Murtuza Zabuawala Mar 15 '18 at 15:19
  • 1
    Yes, so I am suggesting to not use vendor names, but only the functionality topic ;) – 7ochem Mar 16 '18 at 9:59
  • 1
    agree with you :) – Murtuza Zabuawala Mar 16 '18 at 10:49

You must log in to answer this question.

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