Re: priorities for PEAR project as a whole
| From: | Arnaud Limbourg | Date: | Thu, 28 Sep 2006 05:11:53 +0000 |
| Subject: | Re: priorities for PEAR project as a whole | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44140@lists.php.net to get a copy of this message | ||
Scott Mattocks wrote:
Greg Beaver wrote:I'd like to add that we lack tools on the website to do that kind of things so it goes toward #1. Arnaud.Summary: #1: make the PEAR website PEAR-installable, instead of syncing from CVSGood idea, but this is the first I have heard of it.#2: add package groups for the website and for installer RESTGood idea, but this is the first I have heard of it.#3: any other changes, political or technicalSome 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.