Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#5591 closed defect (bug) (fixed)

Plugin Directory: Clarified some trademark issues and adding more things

Reported by: ipstenu's profile Ipstenu Owned by: ipstenu's profile Ipstenu
Milestone: Priority: normal
Component: Plugin Directory Keywords: has-patch


Talked to a couple trademark owners about things they'd like to see prevented going forward.

Attachments (1)

5591.diff (1.5 KB) - added by Ipstenu 3 years ago.

Download all attachments as: .zip

Change History (4)

3 years ago

#1 @Ipstenu
3 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 10633:

Plugin Directory: Trademarks

Adding in some more things to block based on use and trademarks.

Don't want to break large plugins, or small ones, if we can.

Fixes #5591

This ticket was mentioned in Slack in #meta by jjj. View the logs.

3 years ago

#3 @Ipstenu
3 years ago

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.

Note: See TracTickets for help on using tickets.