Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109076 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12040 invoked from network); 16 Mar 2020 20:06:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Mar 2020 20:06:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 517091804F8 for ; Mon, 16 Mar 2020 11:29:09 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-qv1-f45.google.com (mail-qv1-f45.google.com [209.85.219.45]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 16 Mar 2020 11:29:08 -0700 (PDT) Received: by mail-qv1-f45.google.com with SMTP id n1so5640207qvz.4 for ; Mon, 16 Mar 2020 11:29:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=VzEuZTaRQKFMc2pNW8GM55zRu3murZCiuT5vda4yzlU=; b=GKdTaBlnDEEoiuZZI6UVgbIsWY8dxRrdJY2epR/F25M9fZF4cfETAIv4KDjhpxLQxa /PXQf+zft8+VHQZxR5Pc91u66LoD9EAWuxL+/Xk+8C3XbZnHC5JTZDvjT66mYwbZk5d5 Y+6QH31I+Tqb4p06LM0a4b9oVt5HBA/8qfDyoTrdSEhp2K78MyrG0MKrFbEPGycBcCNa 8Fkd+RZNL7lkMBhLwBqsAt6aHzsO/WKNcpPuWjZN8UWbPkEq2jadKgQ7+EA/7L8exPfZ tFKTKVoHdQETbEn/qKtnVBDzTPeV/u4cZzTpywUAjm8zRO+/N2vj8g3giwZuxlF3eE0L cZ0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=VzEuZTaRQKFMc2pNW8GM55zRu3murZCiuT5vda4yzlU=; b=VzH694Z9YlBL0juNjnhlVOt/EuD3F8pDLwHiDoiWpr+8BqvEQTkvmIutnWzKk0Nj1u j11/nd3OaSkUICydDwoWqOdkBJ/pG3+ZVkzT/GwQ6LqLCDjLMvs6gDQD//yBRZkD2bVH SoTQ/5TxW6ECHFCSx+XvM714UrRMOmb6wDuNh/D6A+y/EAsHjma4uXjDpGleQBTWz0Lu +CEf55Dv5mTvNVQQcI9tuc84Dh3rRrgBOiSSnknR0etjqUPeW0pLxgLNou0BDd8qznIw TINQ8uPh1hskH3f3XP9xWrZdef84Nmp2KFTy9Y+q1A/jX+QkevMIOzwRdcZ5TEVuLKa3 RN5w== X-Gm-Message-State: ANhLgQ3ZVOpRRnAawf6WcULySy5QLiA1HM0H/3p+XBYLjhUd1oDjLyTP bkUMhpLRNPOh2rHZ1zxNiBwu5eBZpXk/rg== X-Google-Smtp-Source: ADFU+vt7FgeTbiD7gIR2D984OG/VHETCqvp9kYKG5geAk8bxWg8o7tai7HGKhdIUkwIPUfrqdgqutA== X-Received: by 2002:a0c:fa03:: with SMTP id q3mr1098380qvn.228.1584383347009; Mon, 16 Mar 2020 11:29:07 -0700 (PDT) Received: from ?IPv6:2601:c0:c680:5cc0:908f:386e:e286:3224? ([2601:c0:c680:5cc0:908f:386e:e286:3224]) by smtp.gmail.com with ESMTPSA id u49sm402242qtb.52.2020.03.16.11.29.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Mar 2020 11:29:06 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Message-ID: <14383D05-EA33-4CD2-9648-40AA29A837A5@newclarity.net> Date: Mon, 16 Mar 2020 14:29:05 -0400 To: PHP Internals X-Mailer: Apple Mail (2.3445.104.11) Subject: Capturing reasons for votes for historical sake? From: mike@newclarity.net (Mike Schinkel) Hi all, Seeing people referencing former RFCs that failed when someone brings up = an RFC (which is a good thing to reference, BTW) I am finally compelled = to comment in hope there would be will to improve it. When court justices rule on important decisions they write opinions, or = join with the majority or minority opinion. That way judges and others = in the future can know why things were decided a certain way. =20 However in PHP we have no way of knowing why people voted against a = proposal except maybe for those very few who commented negatively on the = mailing list. Which is far from concise and frequently not conclusive.=20= It is a real shame that the PHP voting process has no way to capture a = concise description of why people voted against an RFC. A "No" vote = could mean any of the following, or something completely different, and = their reasons are really important when it comes to future consideration = of the same issue: 1. I hate the idea and never want to see it in PHP 2. I'm okay with the idea but=20 a. I have a small issue with "x" b. I have a big issue with "y" c. I prefer to see it implemented using "z" approach instead 3. I love the idea but=20 a. Can't support it given "x" b. I want it to be implement using "y" approach instead 4. We can't do this until we do "x" first 5. We should do "x" instead 6. Or who knows what other reason? Would it be possible to add a feature when voting were people either = need to type in a one to two sentence reason why they voted "no" on a = proposal OR select from the reasons that others have already given when = voting down the specific RFC? =20 If we had that we could list the reasons and the number of votes that = choose those reasons on the RFC for historical purposes. -Mike