Automattic offers more than just the source code of WP.
Anyone is still free to use the source, but the services they provide are not free.
> Imagine aws offers a hosted node application service. Then, because aws doesn't give anything back, npm blocks the aws ip range, and suddenly existing aws customers can't install modules or security updates.
It's a good analogy. AWS does it a lot, but it does so with open source projects that do not have much paid services. Reading from the article, Automattic provides many services (possibly paid, in some freemium model).
I'd welcome if some projects manage to get AWS to give back. They do way too little if you ask me.
> I get the "you should give back" ideal, but make no mistake, this is because wp engine is eating their lunch.
Yes. Giving back could be a deal that involves money.
I understand it would be ideal for business to give back with money to open source projects, but this issue is being handled in the worst possible way by Matt.
So WordPress code is FOSS, so you can theoretically change the code, except when you change the line that will keep revisions to cut your costs, if you do that he will yell at you.
WordPress' repository is free as in beer, you can download all you want without paying. Heck, even WP code is setup so it downloads from there by default. Except when you happen to host in a company that has a very specific set of issues (alleged trademark issues + profits over a particular threshold + not giving back to community; other companies who have only one of those issues but not all of them are fine), then he'll block you.
The main issue here is the lack of a clear contract of what you can or cannot do. Seems like he is just figuring out the rules along the way. This gives to external observers the impression that the whole thing is unreliable.
Open source makes absolutely zero distinction about how the source code is provided. You aren't required to keep a free-to-use service up to download your code. You only must produce it when requested.
Not too long ago you would pay for disks containing open source software.
Anyone is still free to use the source, but the services they provide are not free.
> Imagine aws offers a hosted node application service. Then, because aws doesn't give anything back, npm blocks the aws ip range, and suddenly existing aws customers can't install modules or security updates.
It's a good analogy. AWS does it a lot, but it does so with open source projects that do not have much paid services. Reading from the article, Automattic provides many services (possibly paid, in some freemium model).
I'd welcome if some projects manage to get AWS to give back. They do way too little if you ask me.
> I get the "you should give back" ideal, but make no mistake, this is because wp engine is eating their lunch.
Yes. Giving back could be a deal that involves money.