License FAQ

Folks, Richard Stallman has requested that we change the license FAQ to suggest to people that they choose a license that is accepted by both the OSI and the FSF. At first I though he meant it had to be a license from the GPL-compatible list, but it doesn't. Just from the list of free software licenses found here: http://www.gnu.org/licenses/license-list.html He had some stuff on that page about not using PHP 4 but instead forking PHP 3, but he removed this after I showed him the current PHP 4 license. Here is an overview of what this means. I have listed the OSI approved licenses, the FSF-approved licenses and then finally the ones that both groups have approved. I think the main license we lose by stating that it has to be accepted by both groups is the Apple Public Source license. Personally that doesn't bother me and since nothing in PEAR that I can find is under this Apple license, this seems like an acceptable compromise to get RMS and the FSF to say good things about PEAR. OSI Academic Free License Apple Public Source License Attribution Assurance Licenses Eiffel Forum License CVW license Motosoto License Nethack General Public License Nokia Open Source License Open Group Test Suite License Ricoh Source Code Public License NCSA Open Source license Vovida Software License v. 1.0 X.Net License FSF --- Arphic Public License Guile license Ada license Freetype Standard ML of New Jersey Copyright License. Public Domain The Cryptix General License The Netizen Open Source License OpenLdap license xinetd license Phorum license Latex license NPL OSI/FSF ------- Apache License Artistic license BSD license Common Public License GPL IBM Public License Intel Open Source License Jabber Open Source License LGPL MIT license Mozilla Public License PHP License Python license Python Software Foundation License QPL Sleepycat License Sun Industry Standards Source License (SISSL) Sun Public License W3C license zlib/libpng license Zope Public license Unless someone has some reasonable objection, I will make the change to the license FAQ soon. -Rasmus