by mobilio on 10/2/24, 8:41 AM with 102 comments
by proxysna on 10/2/24, 9:40 AM
>That is not true. Automattic asked for a verbal agreement that WP Engine would give some percentage of their revenue back into WordPress, either in the form of a trademark agreement or employee hours spent on core WordPress.
Tomato-Tomato. Comedy gold.
by markx2 on 10/2/24, 9:33 AM
"2. Fee. In exchange for the License Grant, WP Engine shall do one of the following:
(a) Pay Automattic a royalty fee equal to 8% of its Gross Revenue on a monthly basis, within fifteen days of the end of each month. "Gross Revenue" means all revenue generated by WP Engine from the sale of its services, calculated without deductions for taxes, refunds, or other costs. WP Engine will also provide Automattic a detailed monthly report of its Gross Revenue within fifteen days of the close of each calendar month, including a product line breakdown of all revenues generated. Automattic will have full audit rights.
(b) Commit 8% of its revenue in the form of salaries of WP Engine employees working on WordPress core features and functionality to be directed by WordPress.org. WP Engine will provide Automattic a detailed monthly report demonstrating its fulfillment of this commitment. WordPress.org and Automattic will have full audit rights, including access to employee records and time-tracking.
(c) Some combination of the above two options'
by misnome on 10/2/24, 9:33 AM
So, it is true.
by mjburgess on 10/2/24, 9:38 AM
I cannot imagine "Automattic" has thought this through. There is no ransom agreement in open source, and the very basis of wordpress' success is the absence of such a thing.
What company now, looking at this technology, would touch it with a 100ft pole?
by GavinAnderegg on 10/2/24, 10:06 AM
by bbx on 10/2/24, 1:32 PM
However, two aspects of WP that were always pain points were: local development and hosting. That's where WP Engine provided solutions.
While being more expensive than other platforms, hosting a WP website with them is a great experience, whether in terms of installing, managing, or reliability.
And recently, I had to update an old WP instance for a client. Having no local install available, I looked into new tools to setup one. Turns out WP Engine's tool called "Local" is what Automattic should have provided 10 years ago. It's a fantastic piece of software that "just works"!
It seems like Automattic feels jealous that another company managed to build upon their own open source product to provide a better experience in every aspect (development, managing, hosting) and are making bank. Good for WP Engine.
by misnome on 10/2/24, 9:36 AM
by maxloh on 10/2/24, 9:38 AM
That's a really bad look, WordPress Foundation.
by thanksgiving on 10/2/24, 10:01 AM
I’m leaving the conversation thinking the relation between automattic and Wordpress dot org is one of tax avoidance. What am I missing?
by gortok on 10/2/24, 9:32 AM
If I wanted to say “I made them an offer” but wanted to be sure they wouldn’t take me up on the offer, this is the sort of term sheet I’d use.
by benjaminwootton on 10/2/24, 9:52 AM
by pknerd on 10/2/24, 9:56 AM
by markx2 on 10/2/24, 10:55 AM
by asmor on 10/2/24, 9:37 AM
by InsomniacL on 10/2/24, 10:00 AM
by jefozabuss on 10/2/24, 9:42 AM
by gman83 on 10/2/24, 6:44 PM
by bradfa on 10/2/24, 10:10 AM
by e40 on 10/2/24, 9:31 AM
by martin_a on 10/2/24, 10:01 AM
Automattic does not like the competition, so they pick one actor in the WP ecosystem _randomly_ and try to force this on to them.
For anybody who is running a service that uses WP this is a threat. You can't be sure that if you build on that ecosystem that one day Matt Mullenweg does not like you and will try to extort money from you, too.
by akaike on 10/2/24, 10:08 AM