> Our research team analyzed our database of over 3M open source components and 70M source files, covering 22 programming languages.
[0]: https://resources.whitesourcesoftware.com/blog-whitesource/t...
The mentioned choosealicense.com is not really helpful with choosing a license because it not really explains all the legal terms used, in my opinion. There are many blog articles out there but to this day I couldn't find a single overview that describes each of the major licenses in a regular-human way. And this overview is what I would need. Simple language, tailored to the most important questions: copyright, attribution, what can both non-commercial and commercial users do and what not, and what are my rights as the owner. If you have any resources on this please share it!
On the other hand, the big difference between licenses is how easy it is to incorporate contributions. That is why Linux thrived under GPL. It's why the formality of Apache's process is well suited for corporate contributions where participation will be vetted by the legal department...and why Apache is less suited for an ecosystem like Javascript.
That the author should do their homeworks and get the facts right. Redis is BSD licensed for 10 years now. Redis modules by Redis Labs, never a part of the Redis core, changed license.
Article flagged because I can excuse a casual commenter here but if you write an article about OSS licensing and are not able to show facts in the correct way, for me there is no place on the HN top positions.
Those "Redis" named products were open source and now are not.
