Your GPL 3.0 license is terrible and prevents legal usage!!! #5
Description
The Good News
I wanted to include your project in my popular phpexperts/rest-speaker project.
The Bad News
Your library is licensed under the GPL v3.
As a Open Source pioneer since I was 10 in the 1990s, I have already lived through The Age Of The GPL, and guess what? Only predatory capitalist megacorps still use it, by and large, with some legacy stuck entities, like Linux.
The world has moved on. I collect stats on all of Packagist.org and the GPL is dying.
license | count
-------------------+--------
MIT | 244987
No License | 36652
BSD-3-Clause | 17110
Apache-2.0 | 13350
proprietary | 9339
GPL-2.0-or-later | 6041
OSL-3.0 | 5737
GPL-3.0-or-later | 5241
GPL-3.0 | 4454
Just 2.2% of Packagist today, and a great many of those are legacy projects from before 2015 when people didn't really know better.
The Two Paths
There are two paths forward:
- Change your license very soon to something allows linking with MIT Licensed code without infecting it like the GPL, like Creative Commons.
- I'm going to implement my own project to directly compete against you.
Since I n eed the stuff now, I'm going to use your project locally only so I don't infect my other projects through linking and distribution. So you have some time.
Warning To Others
Requiring this, or any other GPL packagist package, into your project, whether it is open source or proprietary website, will infect your project with the GPL and then the maintainer of this project, or the FSF, or other activist GPL lawfirms can target your company and compel them to release the source code of your app at the time of inclusion or pay really hefty fines to this maintainer.
Watch this video for the dangers: https://youtu.be/3b2wp7j8jmU