Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98594 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93341 invoked from network); 19 Mar 2017 21:54:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Mar 2017 21:54:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=jakub.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=jakub.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.171 as permitted sender) X-PHP-List-Original-Sender: jakub.php@gmail.com X-Host-Fingerprint: 209.85.161.171 mail-yw0-f171.google.com Received: from [209.85.161.171] ([209.85.161.171:36265] helo=mail-yw0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/15-18522-32EFEC85 for ; Sun, 19 Mar 2017 16:54:45 -0500 Received: by mail-yw0-f171.google.com with SMTP id o4so79999933ywd.3 for ; Sun, 19 Mar 2017 14:54:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=j0I6/QLb9qVd7vtmBlUQGGPGqUL3poPB6pUSOfvfR7I=; b=gk+1TiZp33dHPWc5143/1dauBG4JXpOm/v7rYsqCJvg82bSfHzIWSFk+9H3ZZ7Bnuv WVEDvRqmvyZ5QLY29GkIm1VktheocrrEyIXPNedA3mHkRo03gci+PvQ6Ki1RLTyY/EhO hn9cmvUPorWBmQIa+PfCOeVmXg+D1p7iRAKwC0jG0DPhAsuatdEBRmXEerfqKIo7Q2kj VxLEPmRM7o6X5EtdnvEDbKi0kuDcJn7aMSTIDrJwLb9BupYWETvMj7Dt/AeSVL//TfIi cxWTwyzP4rBlwSXVCMgD7f8wd7OBX7B+lUOj15CNHo4NpBxiB3fqib8fuaRslOLxUF7n 5xJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=j0I6/QLb9qVd7vtmBlUQGGPGqUL3poPB6pUSOfvfR7I=; b=PEE4h9MW9x3hxIiwGNwSruS87P/YFqFt7gu7UMIwkIcdT74PHf6Cy90L99JD5lcF4J 9FIlTDAAR6V5G0l4NSL3AcVvr9gojwxxDH1Y+Ud+fQBmDPHn1TLpYg0yyvV6Q5/4IhUc 0KGWjcNqicXDyD+yRBt8SheA0/TYBSai/JMKEjwtmcI5q5YGJHYsYZbQcKs4lIFnfMr9 yuTIoPptLhDkKHSFcNRB0WgPdSIMA8rxZzVFxgPkx7YaHEsVj+IGrJ4IZ0jO1xKXMAbZ uiNwJTmo1btThAQ2dNwqPIh4M6CZ/cuy0g7wuS47yqdiXPddxw27BkPfmcNghH2mnp0V jyhg== X-Gm-Message-State: AFeK/H23Z8T2DA0nAysPUys9p4ugXkHF5+X3frVpvJymmaozn4S7KKZmky3d1fGYHH/mvjSI4J6wh1KTTfScgQ== X-Received: by 10.13.201.1 with SMTP id l1mr12223795ywd.282.1489960480968; Sun, 19 Mar 2017 14:54:40 -0700 (PDT) MIME-Version: 1.0 Sender: jakub.php@gmail.com Received: by 10.129.72.201 with HTTP; Sun, 19 Mar 2017 14:54:40 -0700 (PDT) Received: by 10.129.72.201 with HTTP; Sun, 19 Mar 2017 14:54:40 -0700 (PDT) In-Reply-To: <3aa0cb2a-4142-046e-d69f-b5481384099b@gmail.com> References: <15fa63cb-6ca6-b809-20b8-5b0e2d357b29@gmx.de> <1304f0ec-2957-2fd0-070e-9f096e3fbb6a@gmail.com> <3aa0cb2a-4142-046e-d69f-b5481384099b@gmail.com> Date: Sun, 19 Mar 2017 21:54:40 +0000 X-Google-Sender-Auth: MXqd_8KZtpbOvWxIsCyyYEcTSjM Message-ID: To: Rowan Collins Cc: PHP internals list Content-Type: multipart/alternative; boundary=001a114e6c0e32cbe7054b1c7569 Subject: Re: [PHP-DEV] Re: [RFC] Extended String Types For PDO From: bukka@php.net (Jakub Zelenka) --001a114e6c0e32cbe7054b1c7569 Content-Type: text/plain; charset=UTF-8 On 19 Mar 2017 21:19, "Rowan Collins" wrote: On 19/03/2017 19:32, Jakub Zelenka wrote: > I completely disagree with this. If there is not enough votes, it means > that poeple either don't care (possibly don't have time or don't read > properly mailing list) or don't understand the proposed thing. > Yes, those are the most likely reasons. There is also the possibility that for some technical or timing reason people missed the announcement. I think it shousld up to the maintainer to decide in such case and not to > block a feature because not enaugh people is interested in it. > There is currently nobody authorised to make that decision, and granting it to extension maintainers feels like a significant change to that role. As I understand it, one of the big differences between a PECL extension and a bundled one is that once in core, it's subject to decision-making by the whole project, not the authors of the code. I don't really think that we any definition for mantainer role. Currently it varies depending on the extension. For example you won't see many RFC's in date ext which is very well maintained by Derick and most of the changes are decided by him which I think is a very good thing and works very well. But even if we leave it as it is (accept it with only few votes) it is > still much better than block it if there is no interest. > The entire RFC and voting process assumes that "no change" is the default option - a language change requires two-thirds to make the change, not two-thirds to reject it. If there were a "quorum" rule, it would be entirely consistent for not enough votes to have the same effect as an insufficiently large majority, and reject the change. Sorry but I just don't agree with that. We are talking about a feature for PDO that not many voters is interested in. That's completely different than a language change. The interest in other core extensions is often the same. If we had such rule on the minimal number of votes, one person could easily block any progress on the any extension. It would not only slow down the development but also annoy maintainers and people working on extension. That's just a very bad idea IMHO. Cheers Jakub --001a114e6c0e32cbe7054b1c7569--