Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12397 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54462 invoked by uid 1010); 27 Aug 2004 07:00:14 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 49815 invoked from network); 27 Aug 2004 06:59:16 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 27 Aug 2004 06:59:16 -0000 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.11/8.12.11) with ESMTP id i7R6xGBX016690 for ; Fri, 27 Aug 2004 08:59:16 +0200 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.11/8.12.11) with ESMTP id i7R6xAjL016663; Fri, 27 Aug 2004 08:59:11 +0200 Date: Fri, 27 Aug 2004 08:59:10 +0200 (CEST) X-X-Sender: derick@localhost To: Sebastian Bergmann cc: internals@lists.php.net In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdimedia.nl Subject: Re: [PHP-DEV] Learning from Python: PEPping the PHP Development Process From: derick@php.net (Derick Rethans) 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? regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org