Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90662 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57127 invoked from network); 15 Jan 2016 15:12:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jan 2016 15:12:30 -0000 Authentication-Results: pb1.pair.com header.from=stig.bakken@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stig.bakken@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.46 as permitted sender) X-PHP-List-Original-Sender: stig.bakken@gmail.com X-Host-Fingerprint: 209.85.215.46 mail-lf0-f46.google.com Received: from [209.85.215.46] ([209.85.215.46:33677] helo=mail-lf0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/72-39304-C5C09965 for ; Fri, 15 Jan 2016 10:12:28 -0500 Received: by mail-lf0-f46.google.com with SMTP id m198so137160340lfm.0 for ; Fri, 15 Jan 2016 07:12:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zZpv/DfmqceczwBIQPWR3P/sOMJ/lkOUwz6E0ccgE1s=; b=WAjQ5nhDyYxc75Tqx0l4iSZVtx4CdXCvf5or8ZwoT7CDWqSfSzvVCwj0/h1p3OJ4nE A/7XpA3ScMEULWJ94MAjd48sXvrdChi4vW3jgU/R92FHJneRL08lxQPMTdGLxqtSTEE0 bQJlL1SvbL8PsYaLamZLzJtnSpoOVjW4oDC+Wl+5pa8lAshzlv4s/1cOv2YtmTeHaiKl OaCcMmQV/6YpaUgP1BPfmb7zb58lmavcMS9XsKDLkTo9VYfiEw30QZI5iWP3FcaWgWae 4lfyCQMRikr4o4hOjI3LevjRmU9hY+a14E5yiCYgzbi7bCY7KTf1Fxx4IKX2hFGtO4rU QNIQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stigbakken-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zZpv/DfmqceczwBIQPWR3P/sOMJ/lkOUwz6E0ccgE1s=; b=wcUdgqmQAjXsBzYYlWT9P7ol0wOscLrQfzQ9ZUM6OEQS7voj2YxbK7bK5zrYLiEhCi 0cTpxe2JXeq8eK95Juks4AZb5XvP4oREnJXtE6j80buM94S0Fnh+CtP8zIiNnixvLBHf +6AqBhCH8QZw95Aewzr7NpVc8vefbDaE9x2CU7hyfbFt8JHs+OnNgq0lrbqw4Y1pLlG+ 3Mjw2u84BbSvY3lVZ5Rds7QTlUpaZxcU+3X6OUVj6L/bUPdywmV5SPooBXynQykV8Mu4 QB2g+neLhWweRstUfl6kYag/GYFrBXMje0dX9eINTym1DQn32/7M4rdCh03ugWPOrLGZ jrjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=zZpv/DfmqceczwBIQPWR3P/sOMJ/lkOUwz6E0ccgE1s=; b=COOY3V6388dYlbqyk4QSHuoD1TeU3kSjJBtyjg69xR4HXRgtXh9IuxeZ2Gae9lfzNz c89ng01jowmhDY5qH2V6kPcMhYLV1Q50VfrFKGxRyK9jWIAeEI+VBl0XhnlsCJf+0Dsy IiJ/Gx7uSim3+vAfPPXqaeZyaQ304rc+ayY6f9ogQo/Ovo3NkncVHeOoEQT1VhNTqaKh 0D3VmxEV8HUxMA/VW3AUZCYl1DJ4xbghTaqTfEQRKKTsVPCBYeVP4RlFxs6yPD6WM2co FcAzNCupEkNnRD35fXopZnwL/NUZwZcSS+vRj/kg98P4EOgESlPPMjpBxYkMFh9+MoY+ +1Aw== X-Gm-Message-State: ALoCoQkcG2874qZVz8QzYiJDHn55uRV0JAfpG8UIqMNaDTUMi16gyrU/JvPTR98h0uMw+stfgVom/8ux7HdVTeCZ/pe7xK9l/g== MIME-Version: 1.0 X-Received: by 10.25.39.8 with SMTP id n8mr3512245lfn.117.1452870745630; Fri, 15 Jan 2016 07:12:25 -0800 (PST) Sender: stig.bakken@gmail.com Received: by 10.25.89.15 with HTTP; Fri, 15 Jan 2016 07:12:25 -0800 (PST) In-Reply-To: <5698FE79.7000300@php.net> References: <8B865D2A-6762-430D-9EA1-9B693DE8E8C3@zort.net> <56948002.1080802@gmail.com> <56958530.2090903@gmail.com> <5696A315.9020509@thefsb.org> <5696A98B.3060907@garfieldtech.com> <5698FE79.7000300@php.net> Date: Fri, 15 Jan 2016 16:12:25 +0100 X-Google-Sender-Auth: jSRhbpnpQ6rrdN94GjVK9HIokes Message-ID: To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= Cc: Zeev Suraski , Larry Garfield , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a113fa404b2b215052960d463 Subject: Re: [PHP-DEV] Re: Internals and Newcomers and the Sidelines -- "let's proceed to ideas" From: stig@stigbakken.com (Stig Bakken) --001a113fa404b2b215052960d463 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Jan 15, 2016 at 3:13 PM, Fran=C3=A7ois Laupretre wrote: > Le 14/01/2016 16:47, Stig Bakken a =C3=A9crit : > >> >> I agree whole-heartedly with Zeev here! >> >> Anyone who has a clue about organizational psychology will tell you to >> focus on what you want more of, not on what you want to eliminate. Heck= , >> anyone who is a parent today should understand this intuitively. >> >> The main focus of a CoC should be positive, describing or even giving >> examples of respectful behavior, that way people are guided towards >> "wanted" behavior, instead of having to figure it out by process of >> elimination from a list of what NOT to do. Granted, there is such a thi= ng >> as common sense, but it's not always that common, so providing positive >> guidance is effective. >> > > I also think positive guidelines are way more effective than punitive > rules. And, as we are talking psychology, I suggest we complement the > approach with the powerful concept of 'compliance without pressure'. This > concept states that someone will naturally respect better something he > freely and explicitely agreed with (sorry for my poor english). > > In our case, it may take the form of a short statement, listing positive > behaviors we want to encourage in the community, expressed in the first > person, expanding the idea of 'I'll try to act with more empathy and > respect among other community members'. Then, publish it and just let > people click on a button when the want to mark their personal engagement = to > follow these guidelines. Under the statement, just list the names of peop= le > who 'signed' on it. The key point is that this must be a voluntary > decision. There must be no pressure on list members to sign this 'good > conduct' statement. This may sound naive but such 'soft power' mechanism > already proved excessively successful in a lot of similar situations. > I really like this idea. It may not effectively give "compliance without pressure", as people will expect one to mark their engagement, so there would be some social pressure within the community. But I don't see that as a problem. Reading through the CoC-related threads I must admit that I'm a bit uneasy about the fact that the RFC process, which was designed to discuss technical features in the PHP core, is being used to define something approaching bylaws for the entire project. I understand that RFCs are a handy tool, but I still question whether it is the right one to use here, at least with the CoC RFC's scope including "punishment" of community members. - Stig --001a113fa404b2b215052960d463--