Anyone could have forked WordPress at any time or spun up their own multi tenant instances if they were truly concerned, this just seems personal. It’s a bad day for founders IMO.
Anyone could have forked WordPress at any time or spun up their own multi tenant instances if they were truly concerned, this just seems personal. It’s a bad day for founders IMO.
it's personal only in the sense that Matt had been doing an absolutely awful job leading the company for several years, and the board had fiduciary obligations to intervene
this is not a bad day for founders; it's Matt having gotten to the end point of his value as a leader
Don't get me wrong: getting to a point where you have 2,000 employees and a 7 billion dollar valuation is a massive accomplishment. He was clearly very effective at various parts of the company's history. But it scaled beyond the point where his skillset and personality could continue to credibly steer the ship
The entire saga started due to WP Engine "forking" WordPress.
So 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..
Matt, you shouldn't have picked a FLOSS license if you didn't intend for the software to be FLOSS in the first place.
Matt, ... just log out and take a break.
WP 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.