Matt Mullenweg deactivates WordPress contributor accounts over alleged fork plans | TechCrunch
techcrunch.com
Matt Mullenweg has deactivated the accounts of several WordPress community members, including two with plans to fork WordPress.
  • kalleboo@lemmy.worldEnglish
    48·
    11 months ago

    They weren’t even planning to create a fork.

    Basically Matt interpreted their “we’re going to take over work within Wordpress since Matt abandoned it” as “we’re taking over Wordpress from Matt” and is telling them through some tortured rhetoric “you aren’t Wordpress, I’m Wordpress, you go do it in a fork instead”

  • irotsoma@lemmy.worldEnglish
    17·
    11 months ago

    I don’t get the logic of cutting off contributions of any kind unless they were actively sabotaging the projector something. Seems like that just makes the fork basically a guarantee. And in open source, a fork that discourages community is always going to be at a disadvantage.

    • rtxn@lemmy.worldEnglish
      181·
      11 months ago

      The original creator of Wordpress and the owner of a Wordpress hosting site. He’s been having a meltdown for months because Wordpress is being used by WP Engine, a for-profit competitor hosting company, in compliance with the license. Since then, he has:

      • Changed the trademark license and retroactively sued WP Engine,
      • Disparaged WP Engine every time he had the chance,
      • Added a potentially legally binding checkbox to wordpress.com where the user must declare their disassociation with WP Engine (which also locked out actual employees),
      • Forcibly taken control of several community-made plugins,
      • Acted like an absolute fucking buffoon the innocent little lamb who’s been set upon by the wolves.
      • merc@sh.itjust.worksEnglish
        2·
        11 months ago

        The sad thing is that at the beginning he had a little tiny bit of justification for not liking what WP Engine was doing.

        What WP Engine was doing was completely legal. They were completely following the requirements of the WordPress license. But, it was true that they could have done more to benefit the WordPress community. Instead, they were building a huge, quarter-billion dollar business based on WordPress without either helping pay for its development or contributing meaningful code themselves.

        A competent project leader could have used the goodwill they’d amassed over decades to mount a subtle pressure campaign to get WP Engine to do more. But, instead, his approach has somehow made a private equity backed for-profit company to almost appear to be the “good guy” in this fight.