Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75902 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16240 invoked from network); 22 Jul 2014 22:25:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2014 22:25:21 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.199 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.199 imap11-2.ox.privateemail.com Received: from [192.64.116.199] ([192.64.116.199:54453] helo=imap11-2.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 87/96-21666-FC4EEC35 for ; Tue, 22 Jul 2014 18:25:19 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 521E68800E6; Tue, 22 Jul 2014 18:25:17 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap11.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap11.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Jj_v0kmmizQE; Tue, 22 Jul 2014 18:25:17 -0400 (EDT) Received: from [192.168.0.15] (unknown [90.210.122.167]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 4A5038800D5; Tue, 22 Jul 2014 18:25:12 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: Date: Tue, 22 Jul 2014 23:25:03 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: To: Sara Golemon X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] Re: PHP Language Specification From: ajf@ajf.me (Andrea Faulds) On 22 Jul 2014, at 23:22, Sara Golemon wrote: > We're happy to setup the framework for curating that document > (probably as a github project), but don't want to be all controlling > with it, so if the PHP Group as an organization wants to own it and > manage updates to it over time, all the better. If that means FB sets > it up then hands it over, that's an option too. This is the > discussion I'd like to start now, so that we can work out a strategy > for what that looks like. Myself I think it=92d be best if the PHP Group runs it. The same = organisation controlling the specification and the reference = implementation of sorts (Zend PHP) is probably more practical than some = external organisation. It=92s also worked pretty well so far. :) -- Andrea Faulds http://ajf.me/