Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110550
MIME-Version: 1.0
References: <BY5PR15MB3729227C6536FA3D0EBE2335929C0@BY5PR15MB3729.namprd15.prod.outlook.com>
 <4b921c5f-db2b-1e2a-ed2a-1add5c9b6663@gmail.com> <20200615174645.GP14030@phcomp.co.uk>
 <CANS-=peH1x-1LAr6pxp4bvToVB8hQ7GT_2xynsDmp1W7bDR7ag@mail.gmail.com>
 <CADK1yXJEV_Kuxhr6LqLd+9sXkaboXH5cLW3NnJBaa7=Op72ZXg@mail.gmail.com>
 <CAJW__o12mwJ68=yKQzNTAGf+ViFV-=TMhhtRPw9weP1wJ+at5g@mail.gmail.com> <CADK1yXLhKubQXvQrt4-zgS4BftyAyXeMHvYm+=qsH+UB8os3+Q@mail.gmail.com>
In-Reply-To: <CADK1yXLhKubQXvQrt4-zgS4BftyAyXeMHvYm+=qsH+UB8os3+Q@mail.gmail.com>
Date: Tue, 16 Jun 2020 02:23:41 +0300
Message-ID: <CAJW__o2+4r3BZ9_ieCAFjo5KA5Pde7seJNJ467ntkFR+kBJ1vA@mail.gmail.com>
To: Deleu <deleugyn@gmail.com>
Cc: Lynn <kjarli@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] About the use of the terms master/slave and blacklist,
 proposal to replace.
From: kalle@php.net (Kalle Sommer Nielsen)

Den tir. 16. jun. 2020 kl. 02.12 skrev Deleu <deleugyn@gmail.com>:
>
> > I am sorry but I do not think you understand the scale of which the
> > PHP project is at.
>
> I'm sorry but you did not get my point. As mentioned above theres 170 pla=
ces mentioning the term blacklist. When I said "the argument of BC without =
knowing the scope" I meant to express that perhaps 1, 10 or 100 of these co=
uld be changed without any BC impact, meaning that perhaps they barely need=
 an RFC in the first place as it could potentially be just internal code. I=
nstead of being negative and dismissive of a chance at a diverse and welcom=
ing environment, let's see what we can easily do first and take the first s=
tep towards making a statement in favor of a better community.

So let me get this straight, you feel uneasy that internally in PHP
there is something called blacklist, a variable or something that, and
changing those are making a statement in favor of a better community.
Well that is also a biased opinion, I am certain we can dispute what
is better for the community for days without end. What purpose does it
serve to change the internal variables from blacklist to blocklist
when it still needs to interact with the term blacklist, why would we
use two different terminologies for the same thing?

I am being negative towards this change because like I have stated
before that it is a change for the sake of change and I do not find
the justifications presented here to be strong enough reason to break
working code because you feel offended by some political propaganda
that has made you believe that blacklist is a racial slur, or whatever
it might be. Censoring industry terms that has correlation to racial
remarks whatsoever sends a signal that "Hey the PHP project would
rather allow breaking your code because it needs to be diverse", what
happens when the next flavor of the month term comes that needs to be
censored for whatever reason, should we then also break that? Because
if that was the case we could do that nonstop.

I still don't think it will make the community better by breaking
already working code. To say that the current naming is not diverse
and welcoming is almost disrespectful in itself.


--=20
regards,

Kalle Sommer Nielsen
kalle@php.net