Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74540 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11726 invoked from network); 28 May 2014 08:24:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 May 2014 08:24:29 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.107 smtp107.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.107] ([108.166.43.107:47715] helo=smtp107.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 62/83-15325-C3D95835 for ; Wed, 28 May 2014 04:24:29 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7D16998590; Wed, 28 May 2014 04:24:25 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 29A7A98588; Wed, 28 May 2014 04:24:25 -0400 (EDT) Message-ID: <53859D38.9010503@sugarcrm.com> Date: Wed, 28 May 2014 01:24:24 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Ferenc Kovacs , PHP Internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] about the latest frontpage entry From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Would like to know what do you guys think about the best step, I see the > following possible options: I wonder why I didn't see any discussion about it here. Did I miss it? If not, it would be a good idea next time to announce such things upfront and solicit feedback. Of course, usually php.net news do not require that, but usually they also are much more routine than announcing a big rewrite of the engine in progress. > > - keep it as is > - remove it > - rewrite it to be more formal and factual(only talk about what it is > atm. not what it could be in the future). > - create a post explaining that this post is controversional among the > core-devs, so it is reflects more of the authors opinion than the projects > official view on the topic. I would propose to include link to the RFC and the branch for people to actually look at, right now it's a bit of "there's a new thing there called phpng, it's awesome, we're working on it". Those who know about it already know that, those that do not, would probably need some more info about it for that announcement to be useful to them, IMHO. Of course, that all provided it is not removed :) I personally think it's more harm than good to remove it. It was a bit premature posting it on php.net instead of personal blog, but what is done is done, and it is better to use it in positive direction. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227