Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104936 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 44267 invoked from network); 25 Mar 2019 18:31:19 -0000 Received: from unknown (HELO hos109.unaxus.net) (195.191.240.18) by pb1.pair.com with SMTP; 25 Mar 2019 18:31:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=heigl.org; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=CSM5dJ2N7hkOuezX1OxtFMPNrWxHihn5AeSlWM4n144=; b=hhlv4oh9tOzzrvv049iGdbJLBt WYNaFW2VyWBaldmKujgApSV63CTZJNm6ZCaqJwNKP9rkDi+C45GsCHjv6zCyIMlzCiVAGrhttzFjq e33W6O46R3KPph14rwQ7hsw2kevrinLeQonDOjUTidrgahanh4XDgS6vK5O97ivzwYL7mrgeSXx+i r+9B7eQwy5fR/6tUFc10uA25kPWY5n5+499O6Q84zxoXLJtKfBI+GlgM7p+1Tpd4NRjfpgr/O4j4t NBQhI4++NqNpKfQk4gkXNIEM+0FPz5N3mEyLTO0XESMQ0Vz1fwIbN3xkZW5F/x8vNFl4XRgzxupDV 3qEbXxxA==; Received: from [46.114.6.110] (port=32979 helo=[10.167.206.110]) by hos109.unaxus.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1h8RSe-003Hhq-28; Mon, 25 Mar 2019 16:24:28 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (15G77) In-Reply-To: Date: Mon, 25 Mar 2019 16:24:27 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <1D4D58A6-DCF2-449E-9219-8F036B70E50A@heigl.org> References: To: Peter Bowyer X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - hos109.unaxus.net X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - heigl.org X-Get-Message-Sender-Via: hos109.unaxus.net: authenticated_id: a.heigl@heigl.org X-Authenticated-Sender: hos109.unaxus.net: a.heigl@heigl.org Subject: Re: [PHP-DEV] RFC Process: more productive conversations From: andreas@heigl.org (Andreas Heigl) > Am 25.03.2019 um 15:39 schrieb Peter Bowyer : >=20 >> On Mon, 25 Mar 2019 at 14:02, Dan Ackroyd wrote:= >>=20 >> I don't believe forcing people to explain their votes actually does that.= >>=20 >> It does something quite similar, of forcing people to try to >> articulate how the RFC needs to change for them to change their vote >> from a no to a yes. At least that is how I have perceived the >> intentions of people who have asked for 'no' voters to explain their >> vote. >>=20 >=20 > It also ties in with the view previously expressed that we should restrict= > voting rights because (my paraphrase) "too many people can vote for > something they don't understand and won't have to maintain". >=20 > Asking people to say why they voted the way they did helps explore this: > can people give a cogent reason for their vote? Shall we then also expect people that vote "yes" to explain why they voted f= or the feature? To see whether they understood what they where voting on? Then we should couple the vote to a comment in the wikinpage and without a c= omment there's no way to vote.=20 That way all the information would be readily available in the RFC and no on= e would need to add comments after an RFC was voted upon. Because IMO that i= nformation as well as the process that lead to acceptance of the RFC are als= o important to afterwards make clear why that feature was implememted the wa= y it was. So all RFCs and also all voters would be treated the same. Just my 0.02=E2=82=AC Cheers Andreas=20