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 | [EMAIL PROTECTED] | gnupg-keyid 0x5CE1DECB
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
