Re: Capturing reasons for votes for historical sake?
| From: | Mike Schinkel | Date: | Tue, 17 Mar 2020 19:32:08 +0000 |
| Subject: | Re: Capturing reasons for votes for historical sake? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-109110@lists.php.net to get a copy of this message | ||
> On Mar 17, 2020, at 4:26 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:
>
> On Mon, Mar 16, 2020 at 8:09 PM Jakob Givoni <jakob@givoni.dk> wrote:
> On Mon, Mar 16, 2020 at 1:29 PM Mike Schinkel <mike@newclarity.net> wrote:
> > If we had that we could list the reasons and the number of votes that choose those reasons
> > on the RFC for historical purposes.
>
> Thanks Mike, exactly what I was thinking when I started writing RFC:
> COPA (https://wiki.php.net/rfc/compact-object-property-assignment)!
>
> As you can see in my "Voting" section, I had the idea to capture
> reasons for no-votes, to document it in the outcome of the RFC, should
> it fail.
> It would have saved my research quite a bit if I had had the no-vote
> reasons for the RFCs I reference at the bottom.
>
> +1 on the idea from me!
>
> FWIW this has been discussed a few times already, and I believe the consensus is: We're
> happy to have *optional* reasons for votes, if someone actually implements it.
>
> For the number of times someone has brought this up on list, there has been a distinct lack of
> volunteers for actually making it happen ;)
>
> Nikita
Hi Nikita,
What would be required to implement it? I assume it is in PHP code? What access would be required?
-Mike