Clarifying the list of checks

Hello David,

That slugs are commonly abused by developers and that’s why we have a block list. If you think that your plugin should contain that word, you can send an email to [email protected] and justify the reason. The team will review your request and allow you to upload if you have very good reasons.

Regards.

Hi,

Thank you for this information, which answers the question “why is there a list of banned slugs in this code”?

However, the question I was asking was something different: I’m asking why is the word “plugin” listed specifically in the code as a trademark? Is “plugin” a trademark, and if so, whose?

Or was it just thrown into a convenient place in the code as a banned word and isn’t actually considered a trademark?

David

It’s the second thing. We have made there because technically is easier. It’s a banned word.

Thanks for clarifying that, that’s helpful.

I’m slightly curious as to how “Plugin” can be banned, given that this plugin is called “Plugin Check”, but I’m not that curious, my real question was just about the trademark.

As I’ve already explained, It’s banned by default and allowed manually.

Of course; but that’s the technical process involved, rather than the underlying “why”.

It’d be helpful to developers to document what sort of reasons are deemed good enough so that they know what their manual explanation should contain to have a chance, and what would just be wasting time, given that it’s not the reason that the plugin currently emits.

The why is because is redundant. That’s the only reason.