Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:32799 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3263 invoked by uid 1010); 16 Oct 2007 01:08:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 3247 invoked from network); 16 Oct 2007 01:08:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2007 01:08:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain prohost.org from 64.233.184.235 cause and error) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 64.233.184.235 wr-out-0506.google.com Linux 2.4/2.6 Received: from [64.233.184.235] ([64.233.184.235:33421] helo=wr-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/00-02076-7EE04174 for ; Mon, 15 Oct 2007 21:07:52 -0400 Received: by wr-out-0506.google.com with SMTP id 58so1034761wri for ; Mon, 15 Oct 2007 18:07:49 -0700 (PDT) Received: by 10.114.103.1 with SMTP id a1mr7711109wac.1192496868094; Mon, 15 Oct 2007 18:07:48 -0700 (PDT) Received: from ?10.3.0.147? ( [66.116.112.8]) by mx.google.com with ESMTPS id l38sm6238326waf.2007.10.15.18.07.46 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 15 Oct 2007 18:07:47 -0700 (PDT) In-Reply-To: <20071015204922.ddc7ae0c.wmoran@potentialtech.com> References: <20071015140534.e44b8be8.wmoran@potentialtech.com> <4713B5D3.9000207@daylessday.org> <20071015151617.0706a365.wmoran@potentialtech.com> <4713C1E6.5060505@daylessday.org> <20071015204922.ddc7ae0c.wmoran@potentialtech.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: Cc: Antony Dovgal , internals@lists.php.net Content-Transfer-Encoding: 7bit Date: Mon, 15 Oct 2007 18:07:45 -0700 To: Bill Moran X-Mailer: Apple Mail (2.752.3) Subject: Re: [PHP-DEV] My musings on problems I've had with the PHP community From: ilia@prohost.org (Ilia Alshanetsky) A few people had already given fairly clear reply as to why things happen the way they do, but since it seems are you still unclear about cause, I'll regurgitate the past comments once again. ;-) First of all you should keep in mind that PHP is an open source project as is the case with many other such projects, people who are contributing their time and effort are volunteers. Thus they tend to focus on things that are interesting to them, such as the extensions they've written, components of the language they use for their day-to- day work, etc... So while there maybe a good number of "Core Developers" few may look at bugs in areas they are not interested in or feel they lack detailed knowledge about the workings of a particular code. As such few extensions have more then one author/ contributor/maintainer and most developers tend to specialize in various areas of the language. There are certainly some components like the standard extension or the language core where there is more then one contributor, but generally each extension is being actively maintained by a little as one person or as many as 3 at the most. Unless the extension is abandoned by its author, other developers will as a rule not get involved in its development, unless previously cleared by the author to do so, or making a trivial change/fix. In the case of the SOAP extension, there is a fairly active maintainer (who also happens to be the author) who knows the extension the best and does his best to fix issues in said extension as CVS log will show. I appreciate the frustration you may have with having a bug sit for some time and waiting for someone to examine it, even though it has a patch attached. That said most bugs do get fixed, especially those with patches attached to them. Some developers may wait till RC is announced before going through their bug queue, so that they can examine all outstanding issues in one go rather then look at them individually to save time, which can contribute to a slow response. Ilia