Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12408 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47346 invoked by uid 1010); 27 Aug 2004 07:55:55 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41504 invoked from network); 27 Aug 2004 07:54:23 -0000 Received: from unknown (HELO mailgate.mysql.com) (213.136.52.47) by pb1.pair.com with SMTP; 27 Aug 2004 07:54:23 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate.mysql.com (8.12.10/8.12.10) with ESMTP id i7R7sLHk019185; Fri, 27 Aug 2004 09:54:21 +0200 Received: from mail.mysql.com ([10.222.1.99]) by localhost (mailgate.mysql.com [10.222.1.98]) (amavisd-new, port 10026) with LMTP id 02917-08; Fri, 27 Aug 2004 09:54:21 +0200 (CEST) Received: from [192.168.1.2] (mailsend.mysql.com [10.100.1.123]) (authenticated bits=0) by mail.mysql.com (8.12.10/8.12.10) with ESMTP id i7R7sA3u019493; Fri, 27 Aug 2004 09:54:11 +0200 Message-ID: <412EE991.1010304@php.net> Date: Fri, 27 Aug 2004 09:58:09 +0200 Reply-To: hartmut@php-groupies.de User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040817 X-Accept-Language: en, de MIME-Version: 1.0 To: Christian Stocker CC: Derick Rethans , Sebastian Bergmann , internals@lists.php.net References: <412EDE81.4040505@bitflux.ch> In-Reply-To: <412EDE81.4040505@bitflux.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailgate.mysql.com Subject: Re: [PHP-DEV] Learning from Python: PEPping the PHP Development Process From: hartmut@php.net (Hartmut Holzgraefe) Christian Stocker wrote: > Actually, other people i talk to are always impressed, how this > "chaotic", based-on-common-agreement developement process actually works > at all ;) Well, one reason might be no matter how fuzzy the process there are some very clear metrics for the result, like e.g. "compiles", "passes tests" or, a little more fuzzy but still rather fact-based, "works". And you can apply all these to different scales of changes. Combine this with the fact that the effort needed to implement changes does not include any noticable cost of creating a copy first and you'll find that creating software is very different to other forms of science, engineering and art. > 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 ;) oh yes, the only list that i'm subscribed to but have activated the "mark message as read" option in the filter ;) -- Hartmut Holzgraefe