Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75972 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84747 invoked from network); 23 Jul 2014 19:02:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2014 19:02:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.51 mail-wg0-f51.google.com Received: from [74.125.82.51] ([74.125.82.51:52172] helo=mail-wg0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/32-06925-3D600D35 for ; Wed, 23 Jul 2014 15:02:43 -0400 Received: by mail-wg0-f51.google.com with SMTP id b13so1576717wgh.10 for ; Wed, 23 Jul 2014 12:02:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=f9eJKq/KUbDPR+cEMd82NVjgzQ8LWKT4zI+OUpkcEFY=; b=QqixQFpVOuojNAzCxs1V2vwmmXF9SxlXNIcnyXMo+n3f52qlbdcm5wikgRkqbj5RSD OhmJY8o9KHzS2iv3c0JdPSC4vgkEVgAeHwuEZqBW6YACB2pyUEAZv7PqqDQR0M5zbQBz axrAvEfeC52tdPWj5bjiLOAepfJzmfULnaKO15O2K4lX6JMrnho7NZ+kOz+Wb72+FBNw qWQiYE4AYbI17IZL7/mLKNuch2TDtiX7Ros0D/D1QCHtLkAvA0B5bIeX/hXNBtPUAjw8 +PVdDP35FKQRAd39+jNA8arFAxCRi843G+2Jr62dOv6FJlWfe40iTXRQd2zVESh0oo+i 25wA== X-Received: by 10.180.101.129 with SMTP id fg1mr27416975wib.20.1406142160658; Wed, 23 Jul 2014 12:02:40 -0700 (PDT) Received: from [192.168.0.177] ([62.189.198.114]) by mx.google.com with ESMTPSA id 10sm8572450wjx.26.2014.07.23.12.02.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jul 2014 12:02:39 -0700 (PDT) Message-ID: <53D0062A.20905@gmail.com> Date: Wed, 23 Jul 2014 19:59:54 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: internals@lists.php.net References: <53CFB2CD.5050703@hoa-project.net> In-Reply-To: <53CFB2CD.5050703@hoa-project.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: PHP Language Specification From: rowan.collins@gmail.com (Rowan Collins) Ivan Enderlin @ Hoa wrote (on 23/07/2014): > My idea was to constitute a **PHP Consortium** (yes, the name is > classy but it reflects the reality), responsible to maintain and edit > the PHP Specification. With what members? Members from the PHP Group > (maintainers of php-src), from Facebook (maintainers of HHVM), from > HippyVM, from JPHP etc. and from others important projects (e.g. > Symfony, Zend etc.), just like the PHP Group does with the RFC votes. This sounds like a nice idea, but there would then be an awkward relationship between this process and the existing RFC process. Currently, an RFC can be proposed and discussed within internals@ which makes changes to the language as implemented by the de facto reference implementation. If that process is not allowed to change the specification directly, then the Zend/php.net implementation would cease to conform to the specification, until such time as The Consortium also accepted the change, and updated the specification to match. If the change was rejected, there would be a power struggle: either the RFC process would have lost power over the language, or the specification would disagree with its oldest and most popular implementation. On the flip side, there is definitely value in representatives from other implementations having a voice in changes that affect them, but that could just mean ensuring that members of those projects are involved within the current framework. Regards, -- Rowan Collins [IMSoP]