Re: Capturing reasons for votes for historical sake?

From: Date: Tue, 17 Mar 2020 19:35:29 +0000
Subject: Re: Capturing reasons for votes for historical sake?
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-109112@lists.php.net to get a copy of this message
> On Mar 17, 2020, at 9:11 AM, Paul M. Jones <pmjones@pmjones.io> wrote: > > > >> On Mar 16, 2020, at 13:29, Mike Schinkel <mike@newclarity.net> wrote: >> >> Hi all, >> >> 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. > ... >> 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? > > I would be against making it a *requirement* but I sure would be happy to see it as an > *option*. Just curious if the "requirement" was only "you have to enter in something" would that still be an issue for you? It is not like we could reasonably validate that they entered something intelligible. They could just say "I don't like" and that would meet the "requirement." > -- > Paul M. Jones > pmjones@pmjones.io > http://paul-m-jones.com > > Modernizing Legacy Applications in PHP > https://leanpub.com/mlaphp > > Solving the N+1 Problem in PHP > https://leanpub.com/sn1php > > >

« previous php.internals (#109112) next »