5 ms·

> [...] and stolen [...] I'm not happy with the mess and Matt's behaviour, but you can't steal free code.

xuki 2y ago
This is not about the code. WP is free to fork it with a new name. This is replacing the old plugin with all its reviews, download count.
- luuurker 2y ago
  The part of the comment I meant to reply to was this: "[...] and stolen what they had previously provided". You're right about the reviews, users, url, etc, but what was "previously provided" was code with a GPL license. You can't "steal" that. The list of things to criticise Matt for is long, but you can't accuse him of stealing open source code.
lolinder 2y ago
He's stolen the ACF permalink, reviews, download count, active installations (including the ability to push auto updates), etc. Sure, the code is free, but that's still a lot of theft. https://wordpress.org/plugins/advanced-custom-fields/ https://wordpress.org/plugins/advanced-custom-fields/
- esskay 2y ago
  To add to that he is now violating their trademark by still using their name, branding and logo, all of which are registered trademarks. The copy you download still has all of these in. Way to speed run wiping out trust in your product. Any Wordpress plugin developer who relies on it for their livelihood should be EXTREMELY worried.
  - pluc 2y ago
    Not only that, but he's taken over all their customers as well if the update source was wordpress.org.
- luuurker 2y ago
  I don't disagree with that, but the comment I've replied to said they were stealing "what they had previously provided". The stuff "provided" was code shared under a GPL license. Maybe it's a technicality, but the code is open source and you can do whatever you want it it, provided that you respect the GPL license. There's a lot to criticise Matt for here, but you can't accuse him of stealing GPL code. Like, that's one of the points of that license.
hooverd 2y ago
What Matt did is basically a supply chain attack.
- chx 2y ago
  Not the first one. Cutting WPEngine customers off the plugin repository was one, too.
- deleted 2y ago
  [deleted]
Brian_K_White 2y ago
Where in the world, how the hell did you get the idea that stealing free code isn't stealing?
- thih9 2y ago
  Stealing involves acquiring something in an illegal way. Free in the context of open source code usually means infinitely available under its license. These two are incompatible - unless some illegal license shenanigans are at play.
  - Brian_K_White 2y ago
    Stealing doesn't imply anything. It is taking someone else's posession. In the case of gpl software, copying, and posessing a copy, and redistributing a copy of the code itself is not theft. The license grants those actions explicitly. But the fact that the license grants those particular rights does not mean there is no license, and violating that license is exactly theft, which is what Mullenweg has done. For someone persuing this whole pogrom under the banner of championing open source and being a good community member and challenging others integrity, this is about as hipocrytical and low as you can go. It would be a joke if it wasn't a fact. I would not admit in public that you think that since a license does not require money, that means it has no owner or copyright and that it's impossible to steal it. Or that laws are the only thing that defines right and wrong and stealing. Money is just one of many terms in any agreement or contract or license.
- chipdart 2y ago
  > Where in the world, how the hell did you get the idea that stealing free code isn't stealing? What is your personal definition of "free code" and "stealing free code"? From your post, either you got one of them profoundly wrong, or both.
- luuurker 2y ago
  The code was shared under a GPL license. If the license allows you to reuse, fork, etc, then it makes no sense to accuse you of "stealing". Obviously there's more to it here as they've also taken over the plugin's reviews, users, etc, but the code is GPL.

xuki 2y ago

This is not about the code. WP is free to fork it with a new name. This is replacing the old plugin with all its reviews, download count.

luuurker 2y ago
The part of the comment I meant to reply to was this: "[...] and stolen what they had previously provided". You're right about the reviews, users, url, etc, but what was "previously provided" was code with a GPL license. You can't "steal" that. The list of things to criticise Matt for is long, but you can't accuse him of stealing open source code.

lolinder 2y ago

He's stolen the ACF permalink, reviews, download count, active installations (including the ability to push auto updates), etc. Sure, the code is free, but that's still a lot of theft. https://wordpress.org/plugins/advanced-custom-fields/ https://wordpress.org/plugins/advanced-custom-fields/

esskay 2y ago
To add to that he is now violating their trademark by still using their name, branding and logo, all of which are registered trademarks. The copy you download still has all of these in. Way to speed run wiping out trust in your product. Any Wordpress plugin developer who relies on it for their livelihood should be EXTREMELY worried.
- pluc 2y ago
  Not only that, but he's taken over all their customers as well if the update source was wordpress.org.
luuurker 2y ago
I don't disagree with that, but the comment I've replied to said they were stealing "what they had previously provided". The stuff "provided" was code shared under a GPL license. Maybe it's a technicality, but the code is open source and you can do whatever you want it it, provided that you respect the GPL license. There's a lot to criticise Matt for here, but you can't accuse him of stealing GPL code. Like, that's one of the points of that license.

hooverd 2y ago

What Matt did is basically a supply chain attack.

chx 2y ago
Not the first one. Cutting WPEngine customers off the plugin repository was one, too.
deleted 2y ago
[deleted]

Brian_K_White 2y ago

Where in the world, how the hell did you get the idea that stealing free code isn't stealing?

thih9 2y ago
Stealing involves acquiring something in an illegal way. Free in the context of open source code usually means infinitely available under its license. These two are incompatible - unless some illegal license shenanigans are at play.
- Brian_K_White 2y ago
  Stealing doesn't imply anything. It is taking someone else's posession. In the case of gpl software, copying, and posessing a copy, and redistributing a copy of the code itself is not theft. The license grants those actions explicitly. But the fact that the license grants those particular rights does not mean there is no license, and violating that license is exactly theft, which is what Mullenweg has done. For someone persuing this whole pogrom under the banner of championing open source and being a good community member and challenging others integrity, this is about as hipocrytical and low as you can go. It would be a joke if it wasn't a fact. I would not admit in public that you think that since a license does not require money, that means it has no owner or copyright and that it's impossible to steal it. Or that laws are the only thing that defines right and wrong and stealing. Money is just one of many terms in any agreement or contract or license.
chipdart 2y ago
> Where in the world, how the hell did you get the idea that stealing free code isn't stealing? What is your personal definition of "free code" and "stealing free code"? From your post, either you got one of them profoundly wrong, or both.
luuurker 2y ago
The code was shared under a GPL license. If the license allows you to reuse, fork, etc, then it makes no sense to accuse you of "stealing". Obviously there's more to it here as they've also taken over the plugin's reviews, users, etc, but the code is GPL.