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.
  • Snot Flickerman@lemmy.blahaj.zoneEnglish
    1·
    6 days ago

    This is what happens when you feel ownership over a community.

    He thinks “I built this community” and to an extent he’s correct, but as with the nature of communities, it doesn’t matter if he helped build it, the community is by definition made up of the people of the community… not just the guy who spearheaded things way back in the day. Especially something like an open source project, if he wanted this level of control he should have kept it closed source.

    If you think you own your community, you’re in for a bad time.

    • nixcamic@lemmy.worldEnglish
      1·
      6 days ago

      When you want to build a cult of personality and accidentally build a flourishing diverse community lol

  • kalleboo@lemmy.worldEnglish
    0·
    6 days 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”

    • wizardbeard@lemmy.dbzer0.comEnglish
      0·
      5 days ago

      Holy shit, the amount of pure seethe in the jkpress post could power a small city.

      The more of Mullenweg’s posts and such that I read, the more he comes across as someone that took some professional/business writing classes and thinks that just because he’s using business speak conventions it means that he’s not coming across as a massive petulant child.

      It’s a shame, because he does have some valid points it seems: that the proper existing process wasn’t followed for offering to take the lead, and questioning security and sanity controls in a distributed theme/plugin system.

      But it’s buried so deep in barely concealed shitslinging that it’s nearly impossible to take seriously.

  • adarza@lemmy.caEnglish
    0·
    6 days ago

    just filing this away…

    … t… u… v… w… x… woops. back up.

    w.

    there we go.

    right before xfree86 in the file of forgotten projects that fucked-up big, and lost.

    • Sturgist@lemmy.caEnglish
      1·
      4 days ago

      xfree86

      I’m about to look this up, I better not be disappointed with how they bombed their own project …

      Edit: that did not disappoint

  • wizardbeard@lemmy.dbzer0.comEnglish
    0·
    6 days ago

    Man, this meltdown just keeps fucking going, doesn’t it. Every time I think Mullenweg has finally settled down, he does something else incredibly dumb.

    Sad part is that he’s likely to get away with this pne since it’s not effecting a company with enough money to make it a legal battle.

    • taladar@sh.itjust.worksEnglish
      1·
      6 days ago

      This will not kill Wordpress outright but it might very well significantly factor into the decision of every future person deciding if they should write a plugin to support Wordpress or some alternative CMS or if they should host a Wordpress instance or something else, especially companies offering commercial hosting.

      It might even lead to a project or two that will eventually replace Wordpress in its dominant position.