Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90409
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5690B64F.9050405@gmail.com>
References: <CAAyV7nFbngZ42qzbSFyveH+vsyir9QNtMJq8H=u9VqTBVBv5Og@mail.gmail.com>
	<CAAyV7nHrip8Ljxjdi2DiGbcnXxY9JK+pN+LCwYKqsjJNvEyUrg@mail.gmail.com>
	<910b145571b2c3e98338d54c0dd6a981@mail.gmail.com>
	<CAAyV7nGGJ3-mCZhDcmhcjqgEOMUBQwvA0vVEE67K4Vmot4ep5Q@mail.gmail.com>
	<CAPgLKii-L-TvKLiSYNdcXxmkr60k2_93EE7hc9LSL=3NQwQjRw@mail.gmail.com>
	<CAESVnVqrXQHpYabkOZvVhbGVUNtQLLS_h=OsnaaQWhEeHWx+uw@mail.gmail.com>
	<CAAyV7nGV4Vawdq67j0eZa4j+R2zM_14-KZpBe_S6JUOc7-9Yfg@mail.gmail.com>
	<568FEBB2.4090001@gmail.com>
	<CAEZPtU4mD9h77nDG3_sVr+ySRac=HmFta2g+pOjrm-uFyGqZCw@mail.gmail.com>
	<569007F5.3030004@gmail.com>
	<CAEZPtU4cm1zDiN+_3_29A51qGKO-LO+qXN30syNK9-Bo6sDGZw@mail.gmail.com>
	<56902C5E.2020401@gmail.com>
	<CAEZPtU67wLe8rq5FhxK6gtP6SNkk2LRTCL3m+DhQPhFp_iPyFg@mail.gmail.com>
	<5690A7E6.3010605@gmail.com>
	<CAEZPtU6HOC3n8xsxEmWogoscSwcGqGSsU=_w4QnP-LwZdtUUgQ@mail.gmail.com>
	<5690B64F.9050405@gmail.com>
Date: Sat, 9 Jan 2016 14:32:18 +0700
Message-ID: <CAEZPtU4kmJ21ccSiU8ytGNU3Otjv_6SMbd36j2aUToO4MDDbWQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c32ddc25d3ef0528e1b49e
Subject: Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct
From: pierre.php@gmail.com (Pierre Joye)

--001a11c32ddc25d3ef0528e1b49e
Content-Type: text/plain; charset=UTF-8

On Jan 9, 2016 2:27 PM, "Stanislav Malyshev" <smalyshev@gmail.com> wrote:
>
> Hi!
>
> > One problem we discuss this using two different ends. I mainly focus on
> > providing tools to ensure we have a safe context. While you seem to
> > ensure that we do not mistakes, do not ban innocent or apply censorship
> > inadvertently.
>
> If you looks at creating safe context without worrying about mistakes,
> then this is easy - just ban everybody who sends anything anybody
> doesn't like.

A minimum effort is required for this discussion. Really.

Did I ever say that? No, I did not.

What I said is that these are two different points and should be discussed
separately. Yes, it will be part of the RFc but talking many points at the
same time is impossible.

Content of the CoC, roles of the group, actions or no action defined, etc
are different points which should be discussed, one after another.

Early points like the toc of the CoC can be discussed with assumptions.
Assumptions like 'let say we trust the group to begin with". Then we can
discuss how the group is chosen. For example.

This is not code or tech matters, we cannot have unit tests.
>  No need for process, votes, etc. Of course, that would
> ruin the community, but safety would be ensured. I hope that illustrates
> absurdity of looking for safety alone, without ensuring safeguards. For
> the sci-fi rendering of the same theme, I recommend Watchbird by R.
> Sheckley: http://www.gutenberg.org/files/29579/29579-h/29579-h.htm
> This is how safe context without safeguards looks like.

--001a11c32ddc25d3ef0528e1b49e--