Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110586 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 23436 invoked from network); 16 Jun 2020 13:50:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Jun 2020 13:50:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6A8191804DC for ; Tue, 16 Jun 2020 05:35:39 -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=-1.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS 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-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) (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 ; Tue, 16 Jun 2020 05:35:38 -0700 (PDT) Received: by mail-pl1-f176.google.com with SMTP id k6so3377176pll.9 for ; Tue, 16 Jun 2020 05:35:38 -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:content-transfer-encoding; bh=y2D39C6WG6uu8WSvIQd2/lMBdYvnkCMdiCywrcdxHCU=; b=DuBIvah0WcTYDj1XA1d7Uss266lESQku/CRL+7t1/o54oVQRcvO+/AkF+6gjCaT5mM b2I4odOz36sRKFNOqZz2ZBTT5QXaSq4UvkvXhY8amjWX1iW505SR/E9VLJW8IIbzOmmF a+1lX0yD9gfv2Pwhxyg71BB7kKyJQaq0ydntiCh94AaopQefBsecNsXeidm1Gf+nRXq+ V3kQbk5Tjw1Zz3P9Xx9g5Mk62JaKZF/EnEiXT32Z1/IIthOr/5A4B8NXqKbGzQv7hJgf /LjIjYmm5WDV59UMqpkGqrjJWrUhTuh8Jq2mFlHkxnsDmnjz4mOt789gToiFgCqUIOzO R3Pg== X-Gm-Message-State: AOAM532qkw2UnQO8JZmIsFHTW0TJaMygOd1ArWldkusBYzyxlcjigIRR qE4CG682IN3+OeqvopoOuyPc8UQrDjF04Sw2/pUcag== X-Google-Smtp-Source: ABdhPJwPYluWfSSQP1+zE0oyWf04zi2ZmW1z9tGmIa3aVLV65iSNi+RoLrSxNEceTMBupaYPxekeTTvJc3WjfKRZoCs= X-Received: by 2002:a17:90a:240c:: with SMTP id h12mr2669740pje.42.1592310935834; Tue, 16 Jun 2020 05:35:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 16 Jun 2020 15:35:24 +0300 Message-ID: To: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= Cc: PHP Internals List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC][Discussion] Change terminology to ExcludeList From: kalle@php.net (Kalle Sommer Nielsen) Hi Den tir. 16. jun. 2020 kl. 15.15 skrev Micha=C5=82 Brzuchalski : > > Hi Internals, > > I'd like to start a discussion period for my RFC which proposes to change > the use of "blacklist" in Opcache configuration with better > self-descriptive terminology. I disagree with this statement, and I do not believe that just because you think it is a better terminology, it should be justifying the BC break that comes with this change. Like I expressed in the PR when it was originally posted and the other topic currently active on internals that it seems much like a change for the sake of change. This is clearly a political change and something we as a project should refrain from doing. If this RFC comes to pass, are we going to change the PHP.net logo to declare our political allegiance to the cause in America? Attempting to change something which has no correlation to racial remarks but using it as an argument that it can be is an absurd argument to me. > The RFC is here https://wiki.php.net/rfc/change-terminology-to-excludelis= t The pull request in the linked RFC does not seem to reflect all the details of this RFC, the PR also changes the whitelist to allowlist, something that is not noted in the RFC itself among other things, or did I miss something? --=20 regards, Kalle Sommer Nielsen kalle@php.net