Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94559 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91590 invoked from network); 18 Jul 2016 19:28:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jul 2016 19:28:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.195 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.195 mail-pf0-f195.google.com Received: from [209.85.192.195] ([209.85.192.195:36833] helo=mail-pf0-f195.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 87/75-52781-EED2D875 for ; Mon, 18 Jul 2016 15:28:46 -0400 Received: by mail-pf0-f195.google.com with SMTP id y134so8283267pfg.3 for ; Mon, 18 Jul 2016 12:28:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=sltikLzKcQVejROIQTGTtuQg84VQ6gYu++1nwKG67fk=; b=jAMMC3auuhKrdCi55DHhn8an5TWiNF4VeWslECwfOIGrdoTWKu3EooZ90LZaWykhyw +W0TpyeWSLqWwwjM7XFWnDCh0TrLA61cVlJv+9f2tG2SDMiej+9cTypfV8rpnBJspBxl /gTlmpGLp3BKHTdSmclaDnCxBqgGF76YL2/v/d2EYjjTN8ossXHR3ec9+RuHvceUlYTZ jE9p80dZ3d8pBuJdZqt+gUslj4EehfYD/AwG8+oR4xAfUOn6ZKj+nfztzgjbzIOG3HP2 XdPQRGSNzV/MXiMfRKFcz8xAX7mRyUr2BOOQe+0gHl2TVrgA1mdDpKOnTsqWCmmXiF67 PAqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=sltikLzKcQVejROIQTGTtuQg84VQ6gYu++1nwKG67fk=; b=JNBpRPxyk+XOKxM67YILSJ2YZr7Wk8gvcX2XhhqAFIyq9LVui9k0TI9wAh3hCDyLxF UJtANbimQpB4oY0p2HusJ/1IDipJUinfM8SEg5M0O2oQvTydMKhVCca49/U6nLudcLn1 O3zKZpU2tSXGjG9jKyw0U1manRiUmkYDyJmgn7Q660iedhqcZDoF8tcc3tb3E2cyaFCU J7j08XvyYRxiTpMYeLrkDQNQT54p/6gh2d4yQ0uxQJRCCPg4jad3gUTQpeTP3QXmZ+uW 8fsjx+Ht1tZjlqQ6pAC9xc+PEmsOkNX4XMom24tp893bGp1+zL3duQlCWaAdiMtGbcvv Dzbg== X-Gm-Message-State: ALyK8tK5WxIMlVP2EPJLPHJTeH+RvRFHpONvxYZuZuBt9ntfQpPpvQkYQTxOW+eRB1pHSQ== X-Received: by 10.98.2.208 with SMTP id 199mr48777293pfc.80.1468870123699; Mon, 18 Jul 2016 12:28:43 -0700 (PDT) Received: from Stas-Air.local (76-220-46-95.lightspeed.sntcca.sbcglobal.net. [76.220.46.95]) by smtp.gmail.com with ESMTPSA id bz5sm645511pac.13.2016.07.18.12.28.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 12:28:43 -0700 (PDT) To: Pierre Joye , Davey Shafik References: <5bad172a-4570-78f8-814e-987299241a2b@gmail.com> Cc: PHP Internals Message-ID: <8b71fde5-4b17-0698-6c31-e1da8ed89a2b@gmail.com> Date: Mon, 18 Jul 2016 12:28:40 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] orphaned extensions in 7.1? From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > xmlrpc is used quite a lot still (limesurvey f.e. or moodle as this > other reply confirmed), removing without previous warnings or not even > trying to get a maintainer before moving it sounds a bit like a bad > move to me. Well, we're not destroying the code. Anybody who builds their own can as easily check out PECL repo, and distributions can and do build PECL modules without any problem. The difference is mainly whose responsibility it is. If it's in core, PHP team as a whole bears responsibility on what happens there, and if we don't actually have anybody to maintain it, the claim that we do is a lie, and we're making promises on which we can't deliver. So we should either seek maintainers or admit we don't maintain it. So I don't see it as a BC issue but mainly as an issue of clearly communicating of who is responsible for given extension and what promises we are making. That said, we probably need a bit better procedure on how that process should work, I'll try to write an RFC in my copious free time to set up guidelines and maybe do some re-inventarization of our extensions for 7.1. -- Stas Malyshev smalyshev@gmail.com