Re: priorities for PEAR project as a whole

Scott Mattocks wrote: > Greg Beaver wrote: > >> >> Summary: >> #1: make the PEAR website PEAR-installable, instead of syncing from CVS > > > Good idea, but this is the first I have heard of it. A quick search of beeblex reveals that I have not mentioned this publicly, but the idea is not new to IRC. So, now you've heard of it. Basically, any time I want to implement some fantastic new change in pearweb, I don't, because I don't have the proper facility to be certain it will work, especially since there is an hour delay between a change and when it goes live. As such, only incremental changes (and hacks) get done, which stalls anything truly useful like 1) making pearweb scalable 2) making pearweb PHP 5.1+ and taking advantage of APC These require the ability to test, and way more than 1 active developer, which means it must be easy to get pearweb running on your local machine. >> #2: add package groups for the website and for installer REST > > > Good idea, but this is the first I have heard of it. From Nov. 28, 2005: http://beeblex.com/lists/index.php/php.pear.core/4346?s=package+groups Greg