RE: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct

> -----Original Message----- > From: Dan Ackroyd [mailto:danack@basereality.com] > Sent: Monday, January 25, 2016 12:48 AM > To: Stanislav Malyshev <smalyshev@gmail.com> > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct > > A significant number of technical RFC discussions have been less productive > than they should be, due to people repeatedly sending emails against an > RFC, that repeat what they have already said, which is not a productive use > of anyone's time, and makes people (including > myself) not want to put forward ideas, or to participate in the discussions. Arguing against an RFC is at least as legitimate as arguing for it; Arguably, even more so - given our bias for status quo. Put another word - the assumption (at least on the technical side) that the current situation is good, and there needs to be a very robust case enjoying widspread support in order to change it. The nature of divisive RFCs - RFCs that garner strong support from both people in favor of them and against them - is that one camp is unable to convince the other for prolonged periods of time. That typically results in both camps raising the same reasons, both in favor and against, and 'continuously improving' their case. That's completely legitimate. It may be tiring - it's in fact almost definitely tiring, but there's no way around it - certainly not via a CoC that would censor one side or the other from championing what they believe in. The only solution to the divisive RFC syndrome IMHO - that 'immunize' internals from having toxic discussions - is to radically bump up the pass threshold for RFCs. Zeev