Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110591
MIME-Version: 1.0
References: <CABdc3WrM1bmef-GNZpoYgTj-RE4aCpC3SHsUP2=UgJ2zmDDOKw@mail.gmail.com>
 <5ee8bad6.1c69fb81.b52b9.7c83SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <5ee8bad6.1c69fb81.b52b9.7c83SMTPIN_ADDED_MISSING@mx.google.com>
Date: Tue, 16 Jun 2020 09:54:27 -0400
Message-ID: <CAES=RMub5KXt52YyuEm_ujJpHHZ_nM78xw--RiMYkugmzCJOpQ@mail.gmail.com>
To: Mark Randall <marandall@php.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000c8daf105a833e1b8"
Subject: Re: [PHP-DEV] Re: [RFC][Discussion] Change terminology to ExcludeList
From: jr@rushlow.dev (Jesse Rushlow)

--000000000000c8daf105a833e1b8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I would agree that, in the current global climate, merely commenting on
this RFC could have a significant impact outside of PHP internals on the
individual(s) participating - muchless voting on it. As an example if a
voting member has a product or service they offer - there is the
possibility for a negative financial impact due to their vote / comments.
Their opinions could very easily be construed / misinterpreted as a
political statement.

Thanks,
Jesse Rushlow

On Tue, Jun 16, 2020 at 8:28 AM Mark Randall <marandall@php.net> wrote:

> On 16/06/2020 13:14, Micha=C5=82 Brzuchalski wrote:
> > I'd like to start a discussion period for my RFC which proposes to chan=
ge
> > the use of "blacklist" in Opcache configuration with better
> > self-descriptive terminology.
>
> IMHO this RFC should not come to a vote, the current RFC process is
> ill-equipped to handle such a vote.
>
> This RFC, disguised in a cloak of wanting to improve readability, is
> clearly political. Not political in terms of the inner politics of the
> PHP internals group, but in terms of the larger world.
>
> At the time of publishing, there are currently countless riots,
> protests, counter-protests, harassment and criminal acts surrounding
> this issue. It cannot reasonably be argued that the timing is anything
> other than a political statement, the commonly accepted term would be
> virtue signalling.
>
> In this climate, it is likely impossible to hold a meaningful vote on
> the issue. Internals on internals are not hidden behind some corporate
> monolith like Github / Microsoft. Our names are our own, our contact
> details readily available.
>
> Anyone voting against this RFC on the proposal on any of the perfectly
> legitimate grounds to do so, such as the BC issues, will still
> immediately be labeled a racist and is likely to receive threats or
> harassment.
>
> Anyone voting for it is likely to receive harassment too.
>
> As I said, the current voting system is ill-equipped to handle such a
> setup. If you expect everyone who wants to have a free say, to have a
> free say, there must be an element of anonymity that simply does not
> exist in our current processes.
>
> The RFC author has already stated in R11 that they have started
> receiving harassing emails in relation to it.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--000000000000c8daf105a833e1b8--