Re: Contributing code

> > IMO, we should ban GPL'd products. Why ? Because a GPL'd class could take > > the place of another non-GPL'd class that would do the same job and be more > > flexible when it will be used in a commercial product. > > As I mentioned in my other mail, I'm against banning GPL code. It would > be a very very bad sign to the Open Source Community if PEAR says "GPL > code is not allowed in here" (I can already hear the outcry, even if most > (99.9% :) ) of the packages will not be GPL or be changed to LGPL if we > ask the author gently). > > About non-gpl packages competing with gpl packages: First, we can replace > the gpl package, if/when there is a non-gpl package arround. Or we just > have two, one gpl and one not, if both are equal well. > > But I really think, most of the contributers to PEAR will not have a > problem with changing the license to something less problematic (for > libraries) than GPL. Personally I'm not strongly for or against banning GPL, however I don't think it's unreasonable to expect a project that is tightly knitted to the main PHP project to insist on using PHP-esque licenses, or licenses with similar restrictive natures. -- Richard Heyes V-webmail - http://www.v-webmail.co.uk