From 579d05aae6a317c3571eed45bf5ca08d29efc45e Mon Sep 17 00:00:00 2001 From: Tyler J Russell <22531310+Nytelife26@users.noreply.github.com> Date: Tue, 13 Apr 2021 20:50:24 +0100 Subject: [PATCH 1/4] chore: better suggestions for blacklist / whitelist --- content/language/word-list.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/language/word-list.md b/content/language/word-list.md index 02f4d5d..f2d684e 100644 --- a/content/language/word-list.md +++ b/content/language/word-list.md @@ -10,8 +10,8 @@ Lists which permit or deny a set of nouns, or select enabled features. **Proposed alternative:** -* allowlist/denylist -* allowedNouns/deniedNouns +* `whitelist` -> exception list, inclusion list, list of allowed X / allowed X list +* `blacklist` -> exclusion list, prohibition list, list of unauthorized X / unauthorized X list **Reasoning:** @@ -20,7 +20,7 @@ Because colors in and of themselves have no predetermined meaning, any meaning w In the case of whitelist/blacklist, the terms originate in the publishing industry – one dominated by the USA and England, two countries which participated in slavery and which grapple with their racist legacies to this day. From a technical communication perspective, using whitelist/blacklist as a naming convention applies metaphor (and, in turn, unintended meaning) when it isn’t needed. -More directly descriptive words like allowlist/denylist enhances understanding. Allowlist/denylist, or simply using allowed/denied as an entity prefix has the added benefit of being easily translatable to other human languages. +More directly descriptive alternatives such as the ones proposed above both avoid these connotations and also provide the additional benefit of being accessible to readers from other linguistic backgrounds. Other proposed alternatives such as `allowlist`, `denylist`, `grantlist`, `blocklist`, et cetera, do more harm than good when dealing with languages other than English, so they should not be used. **Recommendation:** Adopt immediately From 0c5e18ea37ebcb69509c56c2adea1717243c677d Mon Sep 17 00:00:00 2001 From: Tyler J Russell <22531310+Nytelife26@users.noreply.github.com> Date: Tue, 13 Apr 2021 20:54:19 +0100 Subject: [PATCH 2/4] chore: add another resource for blacklist / whitelist --- content/language/word-list.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/language/word-list.md b/content/language/word-list.md index f2d684e..1482e6a 100644 --- a/content/language/word-list.md +++ b/content/language/word-list.md @@ -30,6 +30,7 @@ More directly descriptive alternatives such as the ones proposed above both avoi * [IETF Network Working Group: Terminology, Power and Oppressive Language](https://tools.ietf.org/id/draft-knodel-terminology-00.html) * [Android PR](https://9to5google.com/wp-content/uploads/sites/4/2020/06/android-aosp-allowlist-explanation.png) * [cURL PR](https://github.com/curl/curl/pull/5546) +* ["Inclusive Language", a statement by Kludge Cyber Systems](https://github.com/kludge-cs/transparency/blob/master/open-statements/2021-04-04--TERMINOLOGY.md) ## Master, slave From 076e317312e12bc81790e270ce0e99b3aa7d61af Mon Sep 17 00:00:00 2001 From: Tyler J Russell <22531310+Nytelife26@users.noreply.github.com> Date: Thu, 15 Apr 2021 00:13:03 +0100 Subject: [PATCH 3/4] chore: remove denylist example --- content/faqs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/faqs.md b/content/faqs.md index 785c347..e3221e4 100644 --- a/content/faqs.md +++ b/content/faqs.md @@ -38,9 +38,8 @@ Newspeak involved multiple changes but the most essential were: Everything in the conscious language initiative is *the exact opposite* of that. -For example, "Denylist" is both more precise and more accurate than "blacklist"; - -"Primary" is both more precise and more accurate than "master" in projects that have made the switch. +For example, "Primary" is both more precise and more accurate than "master" in projects that have +made the switch. The goal of this project is to use more precise words, in order to avoid unintended connotations that some common words and phrases have. Not From 33a034c8cf90ebac6caa12c456969dc505b4f135 Mon Sep 17 00:00:00 2001 From: Nytelife26 Date: Fri, 16 Apr 2021 03:39:43 +0100 Subject: [PATCH 4/4] chore(faqs): add pr suggestion and kcs appendix link --- content/faqs.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/faqs.md b/content/faqs.md index e3221e4..67af046 100644 --- a/content/faqs.md +++ b/content/faqs.md @@ -38,8 +38,11 @@ Newspeak involved multiple changes but the most essential were: Everything in the conscious language initiative is *the exact opposite* of that. -For example, "Primary" is both more precise and more accurate than "master" in projects that have -made the switch. +For example, "Primary" is both more precise and more accurate than "master" in +projects that have made the switch. Some project choose to use "main" as an +alternative for brevity. On the other side of this paradigm, projects have +elected to use terminology pertaining to "secondary" for instances of the +primary branch - for example, "indev", "clone", "staging", and others. The goal of this project is to use more precise words, in order to avoid unintended connotations that some common words and phrases have. Not @@ -58,9 +61,10 @@ Here are some resources on the topic: * [Broken Metaphor: The Master-Slave Analogy in Technical Literature (2007)](https://www.jstor.org/stable/40061475?seq=1) - article in JSTOR, requires free membership to read * [Terminology, Power and Oppressive Language](https://tools.ietf.org/id/draft-knodel-terminology-00.html) - article with recommendations by Mallory Knodel and Niels ten Oever * [Why "master" matters](https://twitter.com/mislav/status/1270388510684598272) - A twitter thread. + * Point 3 of "A Framework for Analysis" in [Kludge Cyber Systems' "TERMINOLOGY" Statement](https://github.com/kludge-cs/transparency/blob/master/open-statements/2021-04-04--TERMINOLOGY.md#a-framework-for-analysis) ## How do I get my organization involved? -* Join our [mailing list](https://groups.google.com/g/inclusivenaming) to receive project updates and invitations to community meetings. +* Join our [mailing list](https://groups.google.com/g/inclusivenaming) to receive project updates and invitations to community meetings. * Identify key people in your organization who can represent this effort in an ongoing fashion * Read our Implementation Guide and other resources to start making effective changes