Re: something I noticed re:licenses.

> Actually what I said was that everything in PEAR should have the same > license. I don't really care which license that is. I would prefer an > Apache-style license like the PHP one. If each PEAR component had a > different license it would be very difficult for someone to figure out > what they could use and what they couldn't. We don't want that. > So yes, as far as I am concerned, a prerequisite of being part of PEAR is > to put the contribution under whatever unified license is chosen for PEAR. hi rasmus, re: license, that's actually fine with me. the pear-ized php license looks totally fine. my question was specifically regarding copyright and how you intend to handle it with pear. it is: -every file that I have seen in pear so far is copyrighted by the PHP Group, despite the fact that many of the authors are not members of the PHP Group. So, do I have to sign over copyright to the PHP Group for everything I contribute to PEAR? That question is extremely important to me. -alex