There is also a greater cost to companies that wish to evaluate every FOSS license for software packages that they use.
Rather, the issue stems from the tendency for organizations to write new licenses in order to address real or perceived needs for their software releases.
Therefore, some consider compatibility with the widely used GNU General Public License (GPL) an important characteristic, for instance David A. Wheeler[2][3] as also the Free Software Foundation (FSF), who maintains a list of the licenses that are compatible with the GPL.
[9] The 2007 released GPLv3 was criticized by several authors for adding another incompatible license in the FOSS ecosystem.
[18] In July 2013, GitHub started a license selection wizard called choosealicense.
[30] Generally the FSF Europe consistently recommends the use of the GNU GPL as much as possible, and when that is not possible, to use GPL-compatible licenses.
[32] A 2009 paper from the University of Washington School of Law titled Open Source License Proliferation: Helpful Diversity or Hopeless Confusion?