Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85162 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47376 invoked from network); 18 Mar 2015 03:52:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Mar 2015 03:52:14 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.170 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.170 mail-pd0-f170.google.com Received: from [209.85.192.170] ([209.85.192.170:34285] helo=mail-pd0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 46/34-20523-E66F8055 for ; Tue, 17 Mar 2015 22:52:14 -0500 Received: by pdbni2 with SMTP id ni2so29736595pdb.1 for ; Tue, 17 Mar 2015 20:52:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8HZz0AD0yVjrgMY4I96Qf/xO4SM7SBWskiTsQgpuU9M=; b=h+KOkPQFw7Cd01+iwSVM0q5m2SxoRFBgQLNUTMYn8IitxQ96GVrmh3T24UUKZb6sU+ ReeBZGC0aLAiF2L1Bzb8rrDIrAm2q8+cBfaD2hK1ztED+BpfETquGWdl0uDk4Mv4hrTI Fv1kFjSEiwVoRp7Wuolp5OFibh4k5hEbouiZiAjrYl+iMdvtk+HDOHEEfUNX4+XkET86 rswZ3tiW1MijxWAtUy3jqBTuKKDntnkpHP+TNNgBbYZWGf01H8zytT/1RiRM8llxSKWo mIqPP/cnmbw8rFChBm0UgPAoqJTlCCsTXzw/q++7P28KY+RY4EqHUz4UKaxYH3Sc4Roq KzZA== X-Received: by 10.70.131.15 with SMTP id oi15mr157400142pdb.161.1426650731332; Tue, 17 Mar 2015 20:52:11 -0700 (PDT) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id bt2sm24891886pad.12.2015.03.17.20.52.10 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Mar 2015 20:52:10 -0700 (PDT) Message-ID: <5508F669.4030804@gmail.com> Date: Tue, 17 Mar 2015 20:52:09 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Pierre Joye CC: Dan Ackroyd , Stelian Mocanita , PHP Internals List References: <5508B7BA.6000108@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Vote process change proposal From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Private emails, pressure and what many, including myself, consider as > harassment is a big issue in many OSS projects, and for PHP too. I am What exactly you are calling "harassment"? I have a feeling we are talking about different things, so it would be nice to explain what exactly is harassment ans some specific examples of when that happened in PHP would be nice. E.g., if I email you and explain you my POV on certain topic, is it harassment? What is I ask your opinion on certain topic? What if I ask you to vote on certain RFC? What if I ask you for explanation of your vote? > not sure what can be done to solve that but private discussions should > be avoided at any price to avoid such bad things to happen. And this Sorry, but I completely disagree. Not only you have absolutely no right and no business to tell me who I choose to talk in private (and, of course, to anybody else as well), but there's absolutely no reason to avoid it. I've had hours of very productive private discussions about various technical topics, both in PHP and outside, and there's absolutely nothing wrong with it. I'm not sure which "such bad things" you mean but I'd like to see some "bad things" that actually happened because of it. Of course, that doesn't mean people should not discuss important things in public, especially if they are of public (understood either as PHP devs or PHP users or wider) concern. Both modes have their uses. And of course it doesn't mean people should not follow the RFC process and provide the necessary explanations and support for their opinions and proposals. But I don't think we lack that, in most cases. There are outliers and bad RFCs from time to time, but we can deal with them when they come. > Now, I do agree as well that discussions can be affiliated to > lobbying. But the key difference is that a discussion on the list is > open and should be backed with technical argument (or principles when > it comes to design). Lobbying, and you know that perfectly, is totally > different story. Let be straight about what is happening and do not > hide our head in the sand for the sake of ignoring a growing and > devastating problem. OK, let us be super-straight. *What* is, on your opinion, happening? While you call us to be straight and claim there is a devastating problem, you seemingly forgot to straightly say what is actually happening and which devastating problem it is? Please do so. > We cannot afford to loose more new contributors, > no matter the reason. Sorry, but we will lose contributors, no matter what. People change, circumstances change, availability changes, people burn out, people get busy, people lose interest, people lose patience with other people disagreeing with them... Tons of reasons why people move on. So giving out such blanket statements "no matter what" doesn't seem very useful to me. I agree the community here is not ideal, and could benefit from more kindness and supportiveness, and the processes could be improved. I don't think anybody is against putting forward specific thoughts on how to do it (though not all thoughts would be good ideas, naturally). But however hard we try, for some people it would prove not to be to their taste, and we can not say we can not let that happen "no matter the reason". -- Stas Malyshev smalyshev@gmail.com