Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2262 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52716 invoked from network); 10 Jun 2003 09:21:27 -0000 Received: from unknown (HELO mail.bauer-kirch.de) (80.237.234.121) by pb1.pair.com with SMTP; 10 Jun 2003 09:21:27 -0000 Received: (qmail 12098 invoked from network); 10 Jun 2003 09:22:31 -0000 Received: from somewhere (IP somewhere) by mail.bauer-kirch.de with SMTP; 10 Jun 2003 09:22:31 -0000 Date: Tue, 10 Jun 2003 11:21:27 +0200 To: James Cox Cc: internals@lists.php.net Message-ID: <20030610092127.GA32202@martinjansen.com> References: <003601c32e91$b9d3d8b0$0200a8c0@23i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003601c32e91$b9d3d8b0$0200a8c0@23i.net> User-Agent: Mutt/1.5.3i Subject: Re: [PHP-DEV] Why Move to PECL? From: mj@php.net (Martin Jansen) On Mon Jun 09, 2003 at 03:1630PM +0100, James Cox wrote: > By moving PECL into the limelight. This week, I will be splitting PECL into > it's own cvs module, and (after discussion) I'd like to create a version of > pearweb for pecl.php.net, essentially seperating the PEAR and PECL projects. While I agree that it's a great idea to make more usage of PECL, I don't think that the plan to set up pecl.php.net as an independent site will help us much: It will result in having to maintain yet another site and fixing bugs in the codebase of pearweb and peclweb (which will be nearly identical) will eventually turn out to be a nightmare. Instead I suggest to make pecl.php.net an alias for pear.php.net and (optically) highlight the PECL packages there, so that interested users can more easily find them. (I offer to help you doing this.) This way PECL becomes more visible and we'll only have to maintain one site instead of two. -- - Martin Martin Jansen http://martinjansen.com/