Re: updated channels rfc
| From: | Lukas Smith | Date: | Wed, 03 Mar 2004 16:19:51 +0000 |
| Subject: | Re: updated channels rfc | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-166@lists.php.net to get a copy of this message | ||
Pierre-Alain Joye wrote:
On Wed, 3 Mar 2004 17:13:02 +0100 mj@php.net (Martin Jansen) wrote:I agree that pearweb needs to be modular (note I dont know the pearweb code). Basically we frequently have people willing to add this or that feature. Be that PEPr, improvements to the search, a wiki, comments/votes for packages etc. This requires that development rights can be handed to people easily without having to fear the entire site breaking down, because that developer wasnt aware what implications a change makes. It also lets us take things step by step in regard to trusting new developers. So whatever pearweb is/will become it needs to be possible to delegate developments rights to as finely grainable subsection as possible. Both from the actual code and the CVS structure. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07To me this implies that we should find an alternative that can be realized more easily. Refactoring the PEAR website just because of an addition to the PEAR installer sounds like breaking a butterfly on a wheel.Except if the butterfly bitches my back since months. We really need have to split the "toys" from the installer. And use a common sources in pecl and pear for the installer. Splitting pearweb will help _a lot_ external projects to setup either (full) mirrors or their own repository.