Does Wordpress "give back" to PHP and Linux?
It did pledge, and the follow-up on that pledge was minimal.
Is this not the standard expectation? Does one typically add a gratuity when contributing to OSS?
> It did pledge, and the follow-up on that pledge was minimal.
So they kept the promise?
I heard at the time that a WP Engine employee had told someone that his/her pledged "full time assignment" had shrunk to a small number of hours per week after a while. That's hearsay, I heard it from someone who doesn't work at either of the two companies and it must be third-hand. But if that were the case, and if the pledge didn't say how long the full-time assignment would be kept up, some people would say that the promise was kept. Those people probably also would say that you shouldn't trust a handshake agreement, and please have a lawyer check the written agreement, and if you run an open source project, copy the policies Oracle has for JDK.
What I say is that there's a conflict waiting to happen, if one of the parties expects the pledge to be kept up for a significant period of time and the other expects to tiptoe away shortly later.
It doesn't help that the word "Wordpress" is used for all sorts of different, but overlapping things: wordpress.com for his private WordPress commercial host competing with WPEngine, wordpress.org for the WordPress Foundation he also controls, WordPress describing the open source GPL licensed project.
Google makes things much simpler to avoid misusing their trademarks by splitting Chrome for their commercial product and Chromium for the open source project.
I like the comparison to Chrome and Chromium. I don't know the timeline of the whole wordpress IP. At this most it has arguably undergone genericization. That's why I think it's complicated enough that there is merit to arguments on either side.
No, WP Engine has been highlighting WordPress and using the word in a way that it did make a lot of non-technical people believe that WP Engine was 'WordPress'. In that, Mullenweg has a point.