4 ms·
The entire saga started due to WP Engine "forking" WordPress.
by minimaxir 1mo ago
The entire saga started due to WP Engine "forking" WordPress.
- 0xDEADBEEFCAFE 1mo agoSo problem solved? My only criticism is that 1) Mr. Mullenweg should have held tighter controls over the IP and 2) the direction to the community that they are encouraged to use "WP" as a prefix for their business names and products was ultimately a bad one leading to this mess..
- nixosbestos 1mo agoMatt, ... just log out and take a break.
- garbagepatch 1mo agoMatt, you shouldn't have picked a FLOSS license if you didn't intend for the software to be FLOSS in the first place.
- sehansen 1mo agoIf they'd done those two things Wordpress would probably have been far less successful. Which certainly is a way of making WP Engine not even want to do what they did. Heck, they would probably not even exist.
- kmeisthax 1mo agoWP Engine's "forking" consisted of disabling the revisions feature by default. As someone who's personally been bitten by this particular WP Engine misfeature, describing this as a "fork" is disingenuous at best. The average Linux distro ships way more out-of-tree changes than WP Engine ever did.
- deleted 1mo ago[deleted]
- deleted 1mo ago[deleted]