17 Responses

  1. Wesley
    Wesley Published |

    The problem is, you have to add your plugin to the wordpress repository if you want to enjoy automatic updates.

    (Yes, you could build that into your plugin yourself, but it’s quite difficult and not standard)

    If wordpress.org could somehow find a way to allow automatic updates for plugins that aren’t in the repository, I’m sure alot of people would be satisfied.

  2. Darren Hoyt
    Darren Hoyt Published |

    I am part of the WordPress community and will back that community and any rules implemented on WordPress.org.

    Curious – to what extent are you saying you will back “any” rules implemented there? I’m not sure there’s an organization/entity in the world I could say that about.

  3. tim
    tim Published |

    “Do all plugins at WordPress.org have to be GPL compatible?”

    …talking about double-standards:


  4. King Rat
    King Rat Published |

    My blog’s reach was ZERO before two days ago. I decided to consolidate much of the crap I have on various other hosted blogs into a nice self-hosted thing where I have no restrictions. Last night I imported one batch of posts from one of those sites, which is the only reason there are archives.

    Anyway, thank you for the defense. I appreciate it. (I have a thick skin, so I can take all the insults thrown my way.)

  5. Marcel
    Marcel Published |

    Thanks for defending ‘King Rat’!

  6. Thaya Kareeson
    Thaya Kareeson Published |

    If you checkout your WordPress plugins from SVN, you can automatically update your plugins using the comment “svn up”. I actually like it better than the WordPress automatic update feature because it is a lot more stable and it persists your local changes (if you made any).

    I agree that if you can’t say something in a nice way then don’t say it at all. It is quite shocking how people behave differently just because they are not posting on their own blog. I’ve had my own fare share of people who visit my Anti-AdBlock plugin page, skim through the description, then bash the plugin without even knowing what the plugin does. This post is a nice reminder to treat other people’s blogs the same way you would treat your own blog.

    @King Rat
    I like GPL, but I certainly feel that not all plugins should be licensed under it. Hats off to you for being one of the first to openly make a stance.

  7. King Rat
    King Rat Published |

    I’m not a huge GPL proponent actually. I think the license is confusing and I’m not a big fan of the terms that allow someone to redistribute. I do like the idea though that if I have a legal copy of the software, I get the right to modify to suit my own purposes.

    It’s irritating to me though when someone wants to play in a GPL software technology sandbox (such as Wordpress) but not the GPL software licensing sandbox.

    I don’t even have a problem with the guy’s link mongering. Put it in. Don’t tell me how to remove it if you want. As long as I have the right and ability to remove it, I’m fine with that. But I didn’t have that right according to him, and (at the time) he didn’t want to play by the rules established by Automattic, but wanted the benefits.

  8. Elliot
    Elliot Published |

    I agree with you Justin and you King Rat. I mean, let’s keep it simple, you want your plugin hosted on WordPress.org? follow the rules. I love cforms and I use it on my site without removing the linklove credit ’cause I think there’s a huge effort put in it. However, I don’t truly believe cforms is 100% GPL given what Oliver wrote on his forum on 7:49 am – January 26, 2009:
    “(…)See the link-love note that comes with cforms (____LINK_LOVE_CREDITS.txt) Even when you simply remove the link love without adding a key, you can still use 100% of the plugin’s functionality in nonAjax mode. Still a good deal, I think.”
    I think that 100% GPL would be either:
    1) allow removal of linklove (I still wouldn’t remove it for my own sites, but certainly for customers’) and still retain ajax functionality, or,
    2) remove linklove and ajax functionality
    Again, I’ve no issue with the linklove thing (you can check my site and see it’s there) but we’re talking here about full GPL or not. I’m still using it even it’s not GPL ’cause I think it’s an awesome plugin.

  9. Ryan
    Ryan Published |

    Nice to see someone defending this King Rat guy. The comments in that post are indeed appalling. What Oliver did was just plain wrong and I don’t think anyone who knows the facts could argue otherwise. As you pointed out, it is difficult (near impossible) to not know that a plugin must be GPL to be in the repository before uploading it.

  10. Jen Units
    Jen Units Published |

    I’ve had my own fare share of people who visit my Anti-AdBlock plugin page, skim through the description, then bash the plugin without even knowing what the plugin does. This post is a nice reminder to treat other people’s blogs the same way you would treat your own blog.

  11. nick
    nick Published |

    Just a quick follow-up/observation:

    Not the above mentioned GPL issue has driven me away from using cforms, but the rather aggressive update intervals of new releases. I simply couldn’t keep up.

    Now more recently I’ve changed my horse again (after moving on the contact form 7) and gave “gravity forms” a shot, only to find out that it also doesn’t comply with GPL rules (someone mentioned it the forums). I then started googling for GPL / plugin issues, which brought me here.

    Now I’m concerned, can I continue to use gravity forms or am I risking violating GPL rules when deploying it for customers?

  12. nick
    nick Published |

    Thanks for the reply!

    Right, they say they’re GPL, but they’re not. The fact that a license key >>is required<< (against a payment) to fully run the plugin breaks GPL right there, it's 100% crystal clear in the GPL text. Weird.

    I guess it doesn't matter what they claim or b/c WP demands it, they're simply not GPL because they don't comply with GPL rules.

Comments are closed.