rfc:change-terminology-to-allowlist-and-blocklist

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
rfc:change-terminology-to-allowlist-and-blocklist [2020/06/16 09:01] – edit for language derickrfc:change-terminology-to-allowlist-and-blocklist [2020/06/16 12:08] – brzuchal
Line 1: Line 1:
-====== PHP RFC: Change terminology to AllowList and BlockList ======+====== PHP RFC: Change terminology to ExcludeList ======
   * Version: 0.9   * Version: 0.9
   * Date: 2020-06-09   * Date: 2020-06-09
   * Author: Michał Marcin Brzuchalski <brzuchal@php.net>   * Author: Michał Marcin Brzuchalski <brzuchal@php.net>
-  * Status: Draft+  * Status: Under Discussion 
 +  * Target Version: PHP 8.0
   * First Published at: http://wiki.php.net/rfc/change-terminology-to-allowlist-and-blocklist   * First Published at: http://wiki.php.net/rfc/change-terminology-to-allowlist-and-blocklist
  
-Change uses of "whitelist" and "blacklist" in Opcache configuration with better self-descriptive terminology.+Change the use of "blacklist" in Opcache configuration with better self-descriptive terminology.
  
 ===== Introduction ===== ===== Introduction =====
-The words "whitelist" and "blacklist" require additional context to figure out the exact intention of a specific +The word "blacklist" require additional context to figure out the exact intention of a specific 
-configuration. This proposal suggest to change these to names that better reflect what the functionality does.+configuration. This proposal suggest to change this to a name that better reflects what the functionality does.
  
 ===== Proposal ===== ===== Proposal =====
-The proposal is to replace all occurrences of "whitelist" and "blacklist" to their respective alternatives "allowlist" and "blocklist". +The proposal is to replace all occurrences of "blacklist" to the alternative "exclude_list".
-There is also a draft [[https://tools.ietf.org/id/draft-knodel-terminology-00.html|IETF document]].+
  
-A list of Open Source projects with similar terminology change is listed in [[https://wiki.php.net/rfc/change-terminology-to-allowlist-and-blocklist#references|references]] section.+A list of Open Source projects with similar terminology change is listed in [[https://wiki.php.net/rfc/change-terminology-to-allowlist-and-blocklist#references|references]] section. There is also a draft [[https://tools.ietf.org/id/draft-knodel-terminology-00.html|IETF document]].
  
 ==== Change INI directive name ==== ==== Change INI directive name ====
-A new INI directive called ''opcache.blocklist_filename'' will be introduced and will configure the same internal value as the already existing ''opcache.blacklist_filename''.+A new INI directive called ''opcache.exclude_list_filename'' will be introduced and will configure the same internal value as the already existing ''opcache.blacklist_filename''.
  
 The INI directive called ''opcache.blacklist_filename'' will remain as is but with additional soft-deprecation in the docs and  The INI directive called ''opcache.blacklist_filename'' will remain as is but with additional soft-deprecation in the docs and 
Line 26: Line 26:
 ==== Change in opcache_get_configuration function ==== ==== Change in opcache_get_configuration function ====
 The ''opcache_get_configuration()'' function currently returns an associative array with information about Opcache. The ''opcache_get_configuration()'' function currently returns an associative array with information about Opcache.
-A new key named ''blocklist'' will be added to resulting array with the same value as the original ''blacklist''+A new key named ''exclude_list'' will be added to resulting array with the same value as the original ''blacklist''
 key which will remain untouched with additional soft-deprecation in the docs. key which will remain untouched with additional soft-deprecation in the docs.
  
Line 33: Line 33:
 Most of the changes are internal only with two exceptions for which this patch requires RFC: Most of the changes are internal only with two exceptions for which this patch requires RFC:
  
-  - The new ''opcache.blacklist_filename'' INI directive +  - The new ''opcache.exclude_list_filename'' INI directive 
-  - An extra ''blacklist'' key in the returned array value of ''opcache_get_configuration()''+  - An extra ''exclude_list'' key in the returned array value of ''opcache_get_configuration()''
  
 Whether the use of the ''opcache.blacklist_filename'' INI directive triggers a deprecation notice is a subject to a secondary vote. Whether the use of the ''opcache.blacklist_filename'' INI directive triggers a deprecation notice is a subject to a secondary vote.
Line 49: Line 49:
  
 ==== To Opcache ==== ==== To Opcache ====
-This proposal modifies Opcache structure and function names by replacing "blacklist" with "blocklist".+This proposal modifies Opcache structure and function names by replacing "blacklist" with "exclude_list".
  
 ==== php.ini Defaults ==== ==== php.ini Defaults ====
  
-  * php.ini-development changed name of ''opcache.blacklist_filename'' into ''opcache.blocklist_filename'' +  * php.ini-development changed name of ''opcache.blacklist_filename'' into ''opcache.exclude_list_filename'' 
-  * php.ini-production changed name of ''opcache.blacklist_filename'' into ''opcache.blocklist_filename''+  * php.ini-production changed name of ''opcache.blacklist_filename'' into ''opcache.exclude__filename''
  
 ===== Future scope ===== ===== Future scope =====
-The possibility to remove ''opcache.blacklist_filename'' INI directive and ''opcache_get_configuration()["blacklist"]'' in the next+The possibility to remove ''opcache.blacklist_filename'' INI directive and ''opcache_get_configuration()["exclude_list"]'' in the next
 minor PHP version: 8.1. minor PHP version: 8.1.
  
rfc/change-terminology-to-allowlist-and-blocklist.txt · Last modified: 2020/06/16 12:10 by brzuchal

Page Tools