[wp-meta] [Making WordPress.org] #5591: Plugin Directory: Clarified some trademark issues and adding more things
Making WordPress.org
noreply at wordpress.org
Tue Aug 17 19:56:31 UTC 2021
#5591: Plugin Directory: Clarified some trademark issues and adding more things
------------------------------+----------------------
Reporter: Ipstenu | Owner: Ipstenu
Type: defect | Status: closed
Priority: normal | Milestone:
Component: Plugin Directory | Resolution: fixed
Keywords: has-patch |
------------------------------+----------------------
Comment (by Ipstenu):
Since people are asking about why "wp-" is blocked:
Using wp- at the beginning of plugin permalinks, yes. Due to how we built
this out, the display name is what gets checked and flagged. You can use
WPPluginName (no space) and Plugin Name for WP.
This stems from part of a longer conversation going on with the
Foundation, regarding handling the actual misuse of ‘WordPress’ in plugin
names (which, as we all know, is actually trademarked and as such should
not be used in your plugin name at all).
Because using WP Blah Blah as a name tends to lead to people changing it
after approval to “WordPress Blah Blah” we put a pause on it to try and
get a handle on how bad is this, what’s the depth of the problem (vs the
actual headache of WC -> WooCommerce in names) and so on.
There is also the reality that using 'WP' or 'Plugin' in a plugin
permalink is unnecessary and can be harmful to SEO due to repetitive
words.
No one is claiming WP is trademarked, we're just trying to minimize
confusion and prevent people from accidentally violating trademarks in the
future because they change WP to WordPress later on.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5591#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list