9 Comments

  1. David McCan
    · Reply

    Another thing that raised eyebrows is that the code to check for the “wp-” prefix specifically allows Automattic to use it, so there was an exception added for Automattic.

    Report

  2. toto
    · Reply

    next step ?

    $table_prefix = ‘wp_’;

    Report

  3. Louis
    · Reply

    One more example of brains getting in the way of technical issues.

    The foundation, or Automattic or someone in the convoluted WordPress infrustructure should have the ability to code a check system for verifying whether or not a name change (that occurs after initial approval) is in compliance with the standards somebody making up the rules has established.

    Personally, I think zelouts need to be a little more objective in their rationale.

    Shall we have a WP Police Force to purge the internet of each occurance of a non-trademarked “WP” used in a post or page, given the possibility that someone might change it to “WordPress” and not give the TM attribute after it? Oh, wait. I’ve never seen a post with WordPress in it that gives that attribution. What about that?

    I mean, why border on ridiculous when it could be so much fun going all the way?

    Report

  4. Louis
    · Reply

    Sorry, that should be zealots. Have to be careful about those things. Someone might have trademarked the other spelling.

    Report

  5. jay c. mailen
    · Reply

    As someone potentially affected by this I can say it’s somewhat disheartening. Looking at it from a pragmatic standpoint I understand the desire to prevent “WP” from being mis-associated. In our particular case we’ve used WP at the beginning of many of our PlugIns to identify them as being available specifically to WordPress as opposed to some of our other projects that are not. With so many other PlugIns in the repository using “WP” as a prefix to their name and with no public information on it being grounds for rejection we put a lot (and I mean a lot) of effort into building our core PlugIns and add-ons around that naming convention. Thus far it hasn’t been stated as a reason for rejection, but we had to stall out after our initial submission because of a series of events. We’ll be resubmitting in the next week, maybe they won’t mention it.

    Report

  6. David Anderson
    · Reply

    Two further thoughts on top of the questions raised in the article:
    1) On what basis is the plugin’s internal slug being considered trademark-relevant territory? As I understood it, trademarks are to do with assertions being made usually in an advertising context, or anything that would reasonably and naturally be understood as one. It’s far from clear that plugin “slugs” legally fall in this area.
    2) The making of a real distinction between “WP X” and “X for WP” also seems either completely arbitrary, or represents a linguistic assertion which is (at least) very debatable relating to the parsing of “WP X”. In ordinary English usage, “The chicken house” and “the house for the chickens” are the same thing. So at least, “WP X” can mean the same as “X for WP”, and the assertion that it is necessarily implies something else is at the least very dubious.
    As the article says, these determinations need to be made fully in the open via a standard processed, and discussed, if the goal of people having confidence in the processes involved is important.

    Report

  7. ripul
    · Reply

    Clarification required, Hypothetically speaking, site like WP beginner has a plugin wp beginner or WPexplorer has plugin wpexplorer is this a violation and they now need to change the name ?

    Report

  8. Steven Gliebe
    · Reply

    Since we’re on the topic of confusion in the WordPress realm, here’s my wishlist:

    Rebrand WordPress.com as Jetpack or other
    Form an independent foundation that ecosystem members can support
    Stop bundling Akismet with WordPress
    An ownership disclosure on WP Tavern articles when relevant

    If that’s too much to ask, then fair enough (may our Benevolent Dictator live forever), just put it all under of Automattic, Inc. and say so. Total consolidation under Automattic (too late for that, I’d say) or total separation would go a long way to make things clear for users, developers and the media.

    PS. Why not just detect “WordPress” in names post-push, temporarily disable and automate an email with remediation instructions?

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: