Forums

WP Tavern › Forums › Articles › Automattic Publishes WP Engine Term Sheet Amidst Controversy

Automattic Publishes WP Engine Term Sheet Amidst Controversy

  • Author
    Posts
    • #163247
      Peter ShawPeter Shaw
      October 2, 2024 at 10:47 PM

      How can A8 ask for provisions to not fork their software when the license most of it under open source licenses?

      Seems weird and concerning?

    • #163246
      DrewDrew
      October 2, 2024 at 10:47 PM

      WordPress (.org) needs to be rescued from Mullenweg’s greedy mitts and planet-sized ego.

    • #163283
      R. Lee RottmanR. Lee Rottman
      October 3, 2024 at 2:17 PM

      Since the WordPress Foundation owns the “WordPress” trademark, why would WP Engine need to sign a licensing deal with Automattic, its competitor, for continued use of the trademark?

      Additionally, in an interview I watched on YouTube Matt said that other hosting companies have paid for a licensing agreement. Are these agreements with the WordPress Foundation or with Automattic?

      • #166795
        BexBex
        January 2, 2025 at 10:32 PM

        “the WordPress Foundation owns the “WordPress” trademark”

        Commercial rights to the trademark (i.e. licensing) were granted to Automattic the same day the WordPress Foundation took ownership of the trademark.

    • #163281
      Steven GliebeSteven Gliebe
      October 3, 2024 at 2:17 PM

      Can’t these matters be dealt with behind closed doors? It’s ugly. And it tarnishes the appeal of WordPress. I don’t know all the details and don’t really care but all these headlines about war between WP Engine and Automattic popping up in my WordPress dashboards seem excessive. That’s my observation, not taking sides here. Peace and love, etc.

    • #163340
      kartikkartik
      October 4, 2024 at 11:58 AM

      Interesting move by Automattic! Publishing the WP Engine term sheet during a controversy seems like a bold step, and it definitely raises some eyebrows. I’m curious to see how this plays out, especially with the potential ripple effects on both companies and the broader WordPress community. I guess transparency is key, but it feels like this might stir the pot even more. What do you think—will it settle things down or just fuel the fire?

    • #163241
      Plugin VulnerabilitiesPlugin Vulnerabilities
      January 2, 2025 at 10:30 PM

      The term sheet says that if WP Engine provided employee hours, it would be to “work on core WordPress features under the direction of WordPress.org.” The open source project is usually just referred to as WordPress, as can be seen on the About page of WordPress and the WordPress Foundation website. In some contexts, WordPress.org refers to just Matt Mullenweg. It would be great to get a clarification as to who or what would be directing the hours in that scenario, and if their interests are separate from those of Automattic/Matt Mullenweg.

    • #163330
      SadSad
      January 2, 2025 at 10:31 PM

      WordPress just doesn’t feel friendly anymore.

      That’s really the crux of the issue. I ran the plugin check https://wordpress.org/plugins/plugin-check/ on a bunch of plugins that I have been using for me and my customers and I see the warnings on all plugins that says they are violating trademarks because they have the word WooCommerce in it. Plugins that have been around for years since the very beginning of WooCommerce. Does that mean that all the plugins now have to pay or will be removed from WordPress.org? I think it does eventually probably.
      Will I get up tomorrow and see the free plugin that I have been using for years, disappear!

      Every day there is a new hostile action

  • Author
    Posts
  • You must be logged in to reply to this topic.

These comments are powered by bbPress which uses Akismet to reduce spam. Learn how your comment data is handled.

Recent Replies

Recent Topics