Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68646 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20874 invoked from network); 28 Aug 2013 19:45:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Aug 2013 19:45:25 -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.75 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.75 smtp75.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.75] ([108.166.43.75:51111] helo=smtp75.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/64-33204-3535E125 for ; Wed, 28 Aug 2013 15:45:23 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 9F4071E8091; Wed, 28 Aug 2013 15:45:20 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 431B51E8089; Wed, 28 Aug 2013 15:45:20 -0400 (EDT) Message-ID: <521E534E.2060603@sugarcrm.com> Date: Wed, 28 Aug 2013 12:45:18 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Lior Kaplan CC: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= , PHP Internals References: <521E468E.5070406@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Attitude against distributions... (Was: JSON non-free license) From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > http://marc.info/?l=php-internals&m=136768085009866&w=2 This is great but this is not exactly what I'm talking about. There's a big difference between having an extension that does JSON in PECL and replacing part of PHP core (and very commonly used part) by something else. It very well may be that Remi's extension is ways better that standard one, and it would be a big step forward for PHP to start using it instead of what we have now. But it should be an explicit decision reached by consensus of PHP community, through RFC process, discussion, vote and so on. Now, as I said, Debian can choose what they distribute, including unilaterally. But we can't both say it's Debian's decision alone and that PHP devs should consider it a PHP issue - if it's a PHP issue, than the decision to replace core extension (and not the decision to create PECL extension, which has much less impact and has the consensus almost always implied - who would object against having a PECL extension that does something useful?) should be explicitly taken by PHP community. So if you think it is a PHP issue - please create an RFC with the arguments to that effect, let's get it discussed and reviewed and have it treated as PHP issues should be treated. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227