Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12369 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95121 invoked by uid 1010); 26 Aug 2004 17:51:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 90285 invoked from network); 26 Aug 2004 17:49:32 -0000 Received: from unknown (HELO colo.lerdorf.com) (66.198.51.121) by pb1.pair.com with SMTP; 26 Aug 2004 17:49:32 -0000 Received: from rasmus2.corp.yahoo.com (rasmus2.corp.yahoo.com [207.126.233.18]) by colo.lerdorf.com (8.13.1/8.13.1/Debian-9) with ESMTP id i7QHnVl8003639; Thu, 26 Aug 2004 10:49:31 -0700 Date: Thu, 26 Aug 2004 10:49:32 -0700 (PDT) X-X-Sender: rasmus@t42p 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 Subject: Re: [PHP-DEV] Learning from Python: PEPping the PHP Development Process From: rasmus@php.net (Rasmus Lerdorf) 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. It smells a little too processy to me, but I wouldn't mind a system that borrowed some of the ideas. Like a single collection point for feature proposals and a common format for them. We could simply steal PEAR's PEPR infrastructure for this (http://pear.php.net/pepr/pepr-overview.php). -Rasmus