Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12398 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90697 invoked by uid 1010); 27 Aug 2004 07:11:36 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 87710 invoked from network); 27 Aug 2004 07:10:58 -0000 Received: from unknown (HELO devel.bitflux.ch) (212.71.98.108) by pb1.pair.com with SMTP; 27 Aug 2004 07:10:58 -0000 Received: from localhost (localhost [127.0.0.1]) by devel.bitflux.ch (Postfix) with ESMTP id 34C5396911; Fri, 27 Aug 2004 09:10:58 +0200 (CEST) Received: from devel.bitflux.ch ([127.0.0.1]) by localhost (devel.bitflux.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29727-06-2; Fri, 27 Aug 2004 09:10:58 +0200 (CEST) Received: from [192.168.0.100] (bx-109.bitflux.ch [212.71.98.109]) by devel.bitflux.ch (Postfix) with ESMTP id 1008994032; Fri, 27 Aug 2004 09:10:58 +0200 (CEST) Message-ID: <412EDE81.4040505@bitflux.ch> Date: Fri, 27 Aug 2004 09:10:57 +0200 User-Agent: Mozilla Thunderbird 0.7.1 (Macintosh/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derick Rethans Cc: Sebastian Bergmann , internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at bitflux.ch Subject: Re: [PHP-DEV] Learning from Python: PEPping the PHP Development Process From: chregu@bitflux.ch (Christian Stocker) On 27.8.2004 8:59 Uhr, Derick Rethans wrote: > On Thu, 26 Aug 2004, Sebastian Bergmann wrote: > > >>At last weekend's EuroFoo [1] I attended Marc-Andre Lemburg's talk [2] >>on the Python development process. >> >>I really wish we had a process similar to Python's PEPs [3] [4] for >>PHP. >> >>Having guidelines for issues like adding a new module [5] or >>deprecating a module [6] not only makes the development consistent but >>also transparent to our users. > > > What is wrong with how we currently do it? Agreed. I don't like PEpr, I don't like the PEAR voting process and the PHP developement process works quite well how it is (I'm aware of the fact, the PHP wouldn't just take PEAR's model as-it-is, but nevertheless...). Actually, other people i talk to are always impressed, how this "chaotic", based-on-common-agreement developement process actually works at all ;) This doesn't stop us from having some PEP-like documents, which clearly define some common rules, but I fear we end up in heavy discussions on wording and details. See the PEAR mailinglists for an example ;) chregu -- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | chregu@bitflux.ch | gnupg-keyid 0x5CE1DECB