ACF isn’t a premium plugin (linked post only concerns those).
The linked post also might not reflect the current policies. This update was a security update and was done due to the unique circumstances around the original publisher.
The correct information is that your employer created the security problem as part of their shakedown attempt. They then banned the WP Engine developers from Wordpress so that they couldn't update the plugin. Now they've forked the plugin, removed the commercial upgrade, and renamed it.
I'm not sure where values come into it. I'd be ashamed to work there.
"It is difficult to get a man to understand something, when his salary depends upon his not understanding it." -- Upton Sinclair (probably, may be apocryphal)
For sure dude, the guy who came here to defend the values of his own and his megalomaniac employer on a weekend evening is probably much too busy to name one. That tracks.
It still uses trademarks from ACF, those are obviously not "open source", which also has been Matt's & wordpress.org's stance since forever: the _code_ is GPL, but the assets are not.
If you "fork" the assets, you're not covered by GPL.
Obviously it's nonsense to discriminate between the free version of a freemium plugin and a commercial plugin and this is simply a stupid way to lash out.
