Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110551 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 45322 invoked from network); 16 Jun 2020 00:54:29 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Jun 2020 00:54:29 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id DA8F91804B7 for ; Mon, 15 Jun 2020 16:39:46 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS8075 40.80.0.0/12 X-Spam-Virus: No X-Envelope-From: Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11olkn2026.outbound.protection.outlook.com [40.92.20.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 15 Jun 2020 16:39:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=l//4n+q8vKYgMGi+NH1sJWciOcmXVGsi6GhmMuFtKEqpk9VmXT2qOQ1F34IIKjr83arzTOzZXPSCGOYIdwsCndKXrezdTrnUU7hTrcjAnkpZ3RfZz4aPDc3g92QirrRODvi8PiCPXvMT3qd5BPDgbIrX/aeG7/YZgoEymIJUGKn9Ci1LAti4nzs6BahI9GtLcVlt4BbOwo8452OQHw89Uj1WCHIVG9v7XHK78XVbdpI/RT/cs50pDRAUgdtHTcEs1SKDVUgGAktnPxto8VkmRj772bDPuIoR0ae8hFhQRWwts3jovb/8vpcmYAU1f55N5/JgX/hapzE8IYOxANsg2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WIzC6FJTI7XgOCcujzQcDFmHR706nhNYT7jGgodSy1U=; b=b358ejXUiTCpjalrgR1Rh513z1fjrtMt1seG4PVXt8K8YbmYZwFdjoXwipC/yTQr5egIRIL81WQaTuJeQw7krkKziHs5qEhOx6KOh48LaidyeSwMxb8Mq+CaWffBR7+7wanBBq7hxoRAPMUKRdSQNbUYWKNljR05BVcoPsI5+eLAZDlm3tJEIG+UseekrmHbTvuJV6HpjcY3pgMF0wdPj1cfHygeXcDvltQNdOTr8NzCD4uOr6wS3X5LaV0/AHu024Thq5VXQ+rWStQN+OpVq1CswUMSauxvOG3rpclhf/pglkzMumkKylWfA3jFOmR1AhwT3LVn6CC12+BO6EUreA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WIzC6FJTI7XgOCcujzQcDFmHR706nhNYT7jGgodSy1U=; b=BDO/I6eg2wJnEgTiXRECDXFpJghyUDI4wQ9stHL2YXWnscOLG6QZzPMPMkh4buKFkK2SiZUzjB5SiFk/3v54v5UOruDDvav7wc1o4N+voqUs/cZbiwatbuq30ItSwCYTWSTbo5mj69vQFIHdeUBBDtagupDRZNtveZPJW4ymwyHMUaZWsLM9Kmf53yMCyksr4Z+PF2M/O1mx3JWaZ3vUI2NoQwpGbAGEABPXS27vZKBZb7WepVEG9NWqBsuXjDZ9wncB9B6YY91ozPXx6aCGgncL7SVhHMizYcO8nysfQGfxjepZykRy5rsnX0tlr7UcSE8ErGYfDwk6hqeJTGiTXQ== Received: from BN8NAM11FT068.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4b::4f) by BN8NAM11HT151.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4b::205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.18; Mon, 15 Jun 2020 23:39:45 +0000 Received: from BY5PR15MB3729.namprd15.prod.outlook.com (2a01:111:e400:fc4b::40) by BN8NAM11FT068.mail.protection.outlook.com (2a01:111:e400:fc4b::325) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.18 via Frontend Transport; Mon, 15 Jun 2020 23:39:45 +0000 Received: from BY5PR15MB3729.namprd15.prod.outlook.com ([fe80::f135:8063:e2d0:3865]) by BY5PR15MB3729.namprd15.prod.outlook.com ([fe80::f135:8063:e2d0:3865%5]) with mapi id 15.20.3088.028; Mon, 15 Jun 2020 23:39:44 +0000 To: Kalle Sommer Nielsen , Deleu CC: Lynn , PHP internals Thread-Topic: [PHP-DEV] About the use of the terms master/slave and blacklist, proposal to replace. Thread-Index: AQHWQyuHHkr5WfpYOk2F1OKhH/JEQKjZ5pIAgAAM9oCAAAUqAIAAPE6AgAATRgCAAAYggIAAA0WAgAADBMY= Date: Mon, 15 Jun 2020 23:39:44 +0000 Message-ID: References: <4b921c5f-db2b-1e2a-ed2a-1add5c9b6663@gmail.com> <20200615174645.GP14030@phcomp.co.uk> , In-Reply-To: Accept-Language: pt-BR, en-US Content-Language: pt-BR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:F7C68ACA5E301CABAA4A61A125E24D2666ADA54A98AC8FE9E120AFFDBEB5F8D3;UpperCasedChecksum:3AA033DE2BCE929065CBA883E5A33614E06C9F29EB0F12E72D4AC3BEB9A6BEF6;SizeAsReceived:7707;Count:45 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [Wj0NLif4PlJxQWH+pQvo4k5YGC/zb62YhznijEV4zseHhkBMB1DdwuRc1EzSkBwY] x-ms-publictraffictype: Email x-incomingheadercount: 45 x-eopattributedmessage: 0 x-ms-office365-filtering-correlation-id: de49fa57-7eda-415b-08b5-08d81185623b x-ms-traffictypediagnostic: BN8NAM11HT151: x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: gPjxROsALc2ul7hOZddEvDV7dgp+8liUpJ5nClr2/2XJOG1x7ikvuPkGwsOp0lyPe7+cDtaiV2xdwjStE143GpziqoG1J9iYhnLq05F/tzd/UxmBufZB++kOZSHOLBQVe/R/KgxXsYhWc7KuWQ9ghOK4pOQXiKR38z3ECSDBy2EG3yZCcugXFdGntaTiMZBKlk4GdfvGxHFx2McR2vUuq9BO9bHJ1DMUBbw5D7wUxvluL7b2zEfrxMqvgV/0+pQ1 x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:0;SRV:;IPV:NLI;SFV:NSPM;H:BY5PR15MB3729.namprd15.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:OUT;SFP:1901; x-ms-exchange-antispam-messagedata: ygUNgTNOPRZZ0sEJC9XlT9vDwbJPIzZGmgfexWoFAcasQe09fMWteakh5EHO9xbLkZ0YLXNIk4e76bw2WhBGzTostGILehinO5NftVp5fxhECUrCcZX+S1n6Fr8ImqF6JdwH8mJoMA4UgJeiUKY5pb+JjyjKxliGZAo3ORl95DejKpZ8AI3UmdlOqaqnSLseTnzWK6cCOjk7hXEgMeI45A== x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_BY5PR15MB372932B9BCA1637E74D427CB929C0BY5PR15MB3729namp_" MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: de49fa57-7eda-415b-08b5-08d81185623b X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jun 2020 23:39:44.8084 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8NAM11HT151 Subject: RE: [PHP-DEV] About the use of the terms master/slave and blacklist, proposal to replace. From: danielrodrigues-ti@hotmail.com (Daniel Rodrigues Lima) --_000_BY5PR15MB372932B9BCA1637E74D427CB929C0BY5PR15MB3729namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The simple fact that we don't know how to deal with this type of discussion= can say a lot about of our community. Anyway when I started this discussion I didn't imagine that I would receive= so many negative feedbacks. -- Cheers, Daniel Rodrigues. geekcom@php.net https://twitter.com/geekcom2 ________________________________ De: Kalle Sommer Nielsen Enviado: segunda-feira, 15 de junho de 2020 20:23 Para: Deleu Cc: Lynn ; PHP internals Assunto: Re: [PHP-DEV] About the use of the terms master/slave and blacklis= t, proposal to replace. Den tir. 16. jun. 2020 kl. 02.12 skrev Deleu : > > > 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. -- regards, Kalle Sommer Nielsen kalle@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php --_000_BY5PR15MB372932B9BCA1637E74D427CB929C0BY5PR15MB3729namp_--