Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110546 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 25102 invoked from network); 15 Jun 2020 23:52:58 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Jun 2020 23:52:58 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 854F218050A for ; Mon, 15 Jun 2020 15:38:16 -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=4.0 required=5.0 tests=BAYES_50, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 15 Jun 2020 15:38:15 -0700 (PDT) Received: by mail-lj1-f175.google.com with SMTP id a9so21195895ljn.6 for ; Mon, 15 Jun 2020 15:38:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zQn7jiKJYQMr68JnritJ5pRSfshBYMq0S4kVYMctHqU=; b=OJdGi1qgTrSfDMNapNvIdMO/ij+3dHcQn28xLvRS5lK124AKGx6eNadgm9WUiMveWV CRRD0X1GVKzzihB3TWxL2xm2AHnSLVwe+o6dz5MMTJhJZbil/rNua/RkCLY68FbBrncH A86t+OFyS1PUeUZPqIYx6Uj6nS4b79Xmp7srwEag1+JALUlTWIpg1pDt7iujBVIAgX/L rM4hBfL8NXNPESxrI1BfF2CL8Ge5W+hIolPNZ7yLu41+0wNEnb+L+0VoOCkwriDInAvY hk6ZilIerdubqye/4TX6ENO3p4/df+A3bL7R8Azrz5Zvk3jdETRIAm4hkW/fLt1sLEtR XFuA== X-Gm-Message-State: AOAM5319hkP6CiJwe1bU1DOxn92uQJOUQmYEK1yCs+h3C/V6JZjZbCJr Xq++m03VhVb5Ebn0hHec85U9qeghSWUWZ1xh09qLjw== X-Google-Smtp-Source: ABdhPJxIWTyivjmYRJ6CvQQTzxa9oGa/A46/S3OtlVXg0rmy/jIrfq3OIq7IWM26D0BbUelnG76UiUg5frdN/e1Xd1k= X-Received: by 2002:a2e:9786:: with SMTP id y6mr13442512lji.398.1592260690711; Mon, 15 Jun 2020 15:38:10 -0700 (PDT) MIME-Version: 1.0 References: <4b921c5f-db2b-1e2a-ed2a-1add5c9b6663@gmail.com> <20200615174645.GP14030@phcomp.co.uk> In-Reply-To: Date: Mon, 15 Jun 2020 17:37:59 -0500 Message-ID: To: Deleu Cc: Lynn , PHP internals Content-Type: multipart/alternative; boundary="000000000000dc335e05a82714fe" Subject: Re: [PHP-DEV] About the use of the terms master/slave and blacklist, proposal to replace. From: pollita@php.net (Sara Golemon) --000000000000dc335e05a82714fe Content-Type: text/plain; charset="UTF-8" On Mon, Jun 15, 2020 at 4:41 PM Deleu wrote: > As white men, we're being dismissive, insensitive and strongly suggesting > we don't want change. While people may not feel offended by any of these > terms being discussed, this thread alone already serves as reason for > people to feel like there's no room for diversity in the internal community > of php. > This. We are (by and large) an awfully pasty group to be saying "This isn't a real problem" and dismissing it out of hand. A white person saying, "These words aren't problematic" is like responding on bugs.php.net with "It works on my machine". > I believe that if we cannot come together to take the small (potentially > insignificant) step towards making changes that signal a welcoming > environment, how are we going to actually take the big steps? > > OP initially came to Gabriel and I (as 8.0 RMs) to judge our response on a small scale. My answer was essentially "That's not my call, take it to internals@" which he did, and frankly I'm disappointed by the reaction he got. I'm not saying this HAS to happen, or even necessarily SHOULD. I really don't know if these words are a problem or not because I'M NOT QUALIFIED to answer that question. I really wish we'd had a better discussion than what we've started with though. As to BC; You know I hate BC breaks for academic reasons, and (at the moment) this certainly feels like a BC break for academic reasons, but again... Don't know how abstract the problem is, just offering my pasty hot-take. It also doesn't have to be a violent BC break. We can alias new names to old and have a nice leisurely migration path on the way to 9.0 (or even 10.0). Last, regarding neutrality. This proposal is literally aimed at adopting more-neutral language. It's not a partisan move to say that harmful language should be avoided. -Sara --000000000000dc335e05a82714fe--