Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56137 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89358 invoked from network); 8 Nov 2011 03:04:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Nov 2011 03:04:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.27 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 66.111.4.27 out3.smtp.messagingengine.com Received: from [66.111.4.27] ([66.111.4.27:55374] helo=out3.smtp.messagingengine.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AD/A0-17624-D3C98BE4 for ; Mon, 07 Nov 2011 22:04:29 -0500 Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id EFADD20B6F for ; Mon, 7 Nov 2011 22:04:26 -0500 (EST) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 07 Nov 2011 22:04:26 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=OBvMV/0NcQ5f9MFem4pnbX hNii4=; b=G5MzqaYnI8EZyXi3Mc8DcGHdtwk6qeuxTCLIMan5R6yXiYCuUsoLRL mQQR3Zm1hXjpDB3/PBgpbl8a3oE6xPvKNbOxwkxFwgWwFptpk/nVIY3RPbJoE1CF cdBYl/j0tnLVBgSPnV7w+EijWzDR8XE47rgF8APRO3SBeS4RPHl3s= X-Sasl-enc: OWTAjkLa9xLGLPPf/CG8c64O/WvPKOrpryTET+gLhAQm 1320721466 Received: from [192.168.42.6] (c-24-13-85-162.hsd1.il.comcast.net [24.13.85.162]) by mail.messagingengine.com (Postfix) with ESMTPSA id B76908E0083 for ; Mon, 7 Nov 2011 22:04:26 -0500 (EST) Message-ID: <4EB89C36.5000503@garfieldtech.com> Date: Mon, 07 Nov 2011 21:04:22 -0600 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: internals@lists.php.net References: <4EB81703.7030605@hoa-project.net> <4EB81C84.8010609@hoa-project.net> <4EB820BB.2030009@lsces.co.uk> <4EB822D4.4060306@hoa-project.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] SplClassLoader RFC Voting phase From: larry@garfieldtech.com (Larry Garfield) On 11/07/2011 01:42 PM, Ferenc Kovacs wrote: > On Mon, Nov 7, 2011 at 7:26 PM, Ivan Enderlin @ Hoa< > ivan.enderlin@hoa-project.net> wrote: > >> >> >> On 07/11/11 19:17, Lester Caine wrote: >> >>> guilhermeblanco@gmail.com wrote: >>> >>>> To participate of php-standards group, feel free to join here: >>>> http://groups.google.com/**group/php-standards >>>> >>> >>> Not while it's not a php list ... >>> >>> +1. It would be great if PHP could host this mailing-list. It would be >> an act of kindness ;-). > > > The group decided to take off from php.net AFAIK: > http://greg.chiaraquartet.net/another-200 The standards group was originally on php.net, and moved off when it was basically thrown off for declaring that they were the self-appointed dictators of what was Correct PHP(tm). After backing down from that, and it was concluded that the group was not an "official PHP" anything, it was determined that they therefore should not be on php.net. There was a lot of drama around that whole PR fiasco. Since then the group was basically silent for a year and a half, but has recently started to inch back to life and discuss what to do moving forward, and opened the list to public membership. I still think it should remain off-PHP, because it is *not* an official PHP Group blessed committee, but that doesn't mean core devs should not be involved. If anything, the low degree of communication between "people who write PHP" and "people who write in PHP" is, and has long been, one of PHP's great weaknesses. I think this entire thread has shown that very well. That is something that needs to be addressed, just as much as inter-framework communication does. Perhaps moreso. --Larry Garfield