Re: priorities for PEAR project as a whole

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.

#2: add package groups for the website and for installer REST

Good idea, but this is the first I have heard of it.

#3: any other changes, political or technical

Some of these maybe able to wait, but some only get worse with time and addressing them now will help with other high priority items. The benefits of PEAR are quality and innovation. If you look at PEPr, you see a bunch of stagnant ideas that are half implemented. Revamping the QA team (a political change) can help to get PEPr cleaned up. This in turn improves the public perception and makes people want to contribute to #1 and #2. It's hard to organize a group of people to work together toward a common goal when there is no defined direction. In order for #1 and #2 to get done, someone needs to step up and say this is where PEAR is going and we need your help (like you just did). All I want is for someone or some group to make decisions, take actions and take responsibility for both. I think that will go a long way to make PEAR a better project. If we can do this loosely organized as we are at the moment, then that is wonderful, but I honestly feel that a little tighter control will help to get things going quickly and in the right direction. Scott