Earlier quoted context omitted.
If not for Microsoft I'd suggest calling it "Word" , no need for the Press.
What about "Press"?
I think PressWord sounds nice
WordPress.org's latest move involves taking control of a WP Engine plugin
101–110 of 222 posts
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#102Earlier quoted context omitted.
Yes, no one stopped the co-funder and it's unlikely he did the fork and the change of ownership only by himself. Other people at Automattic are responsible too.
Considering how many people stayed, it's clear that they've been brainwashed to think what he's doing is ok.
Or they didn't feel confident about quickly getting a new job in this market. Especially since Automattic is mostly/entirely WFH.
It's pretty unlikely the company will go completely broke any time soon so their jobs are probably fairly safe.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#103Even if they find a middle ground to this mess that Matt has created, I very much fear that the damage to the community is done and it's only a matter of time before the popularity of the once famous platform that almost everyone uses in one way or another collapses.
Depends how good their PR is. By all accounts, their current PR is not very good
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#104Well, I hope he's going to pay people to maintain that plugin now.
Because the original author (or team?) is probably motivated to move on to other endeavours instead.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#105Earlier quoted context omitted.
I think Matt would be quite happy with that. His issue is WP Engine not contributing to WordPress. If they decide to maintain a fork and infrastructure, they won't be freeloading anymore. Edit: That attracted a lot of downvotes. I was giving my option in response to the parent comment. In my option Automattic would be happy if they forked it.
Where is it in the license that you need to contribute to the project if you make big bucks? We have open source licenses for a reason, contributing back is never a requirement. If you believe that is his issue, I have a bridge to sell you.
Mullenweg literally said that this was his issue. That’s what kicked off the whole debacle.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#106Honestly I don't get the backlash Mullenweg is getting - a corp is trying to freeload on OSS community, GPL let's them have the code - but I'm all in favor of kicking then off of everything else.
Because I disagree with this definition of freeloading. They've offer a free, open source, very popular plugin for Wordpress, according to the Wordpress.org's plugin page, with 2+ million installs.
Wordpress forking and taking over the plugin seems like they've accepted the code/contribution.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#107So, ACF injected notices into everyone's dashboards to push their own legal agenda. It’s a move that reeks of self-interest more than community benefit. While everyone’s ready to grab their pitchforks at Matt, this actually sounds somewhat reasonable. Still, given its impact, this could easily be seen as a breach of trust. Definitely a move that's going to stir the pot.
Honestly, everyone involved in this situation seems terrible.
With my own experience of the WP "community", that isn't a surprise.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#108Earlier quoted context omitted.
Where is it in the license that you need to contribute to the project if you make big bucks? We have open source licenses for a reason, contributing back is never a requirement. If you believe that is his issue, I have a bridge to sell you.
Mullenweg literally said that this was his issue. That’s what kicked off the whole debacle.
Bill Clinton said he didn’t have relations with that woman.
At some point in life, people usually stop believing everything that others “literally said”.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#109Wordpress banned forks from the plugin directory a while ago, so they're doing what they ban everyone else from doing. https://make.wordpress.org/plugins/2021/02/16/reminder-forke...
That post seems to be about forking open source plugins which cost money. From what I can tell they did fork this plugin but are not offering its premium features for free.
Just to preempt people arguing with me, please note that this comment isn't meant to be an ethical defense of them one way or the other, but just a factual correction.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#110Earlier quoted context omitted.
Didn't this whole thing start because Automattic was complaining that WPEngine wasn't contributing much to the Wordpress development but competing with them for free?
That one of Matts claims. Personally I suspect the actual trigger was WPE removing Automattic's affiliate key from WooCommerce and costing them $m/y of revenue.
That's also one of Matt's claims. According to WPE's court filings, they claim it was an alternate/fork of WooCommerce's Stripe integration they provided with additional features, and makes them less than ~2000$/mo.
If that claim is false, that's perjury.