Open Source Licensing 101 From Concepts to Practical Implications

This book also has a practical orientation. After covering the concepts of open source licensing, we highlight real examples of good and bad licensing usage. As an open source user and software engineering researcher, I always have been amazed by open source licenses, in particular, because quickly things can go wrong.
Why is it important to study open source licenses in 2021? Some questions to think:
Do you know why Google banned the use of the AGPL license on any of its open source projects?
Do you know why GPL 2.0 license, one of the purest copyleft licenses, has more than halved in usage in the last 10 years?
Do you know why it took about a year to change a license in the Eclipse project?
Do you know that the core team of the Lerna project removed of its maintainers due to license misuses?
Do you know why you should run away from open source projects that don't have any license?
Software licensing is a complex subject, which often requires expertise from other areas far away from the software development arena. Indeed, most books regarding software licensing are also written by lawyers, which is not a problem itself, but the terms employed may hinder the understanding of the software development community (I had a hard time understanding some concepts on these books). Another problem is that developers may not always see any concrete implication of an eventual license misuse.
The goal of this book
The goal of this book is two-fold:
First, we intend to make this complex license stuff simpler.
Second, the book should highlight concrete examples of license problems (so developers could easily relate to their activities).