From 5fb15584761b5d8555952c1bdb5ca7f40b7ad201 Mon Sep 17 00:00:00 2001 From: Elaina Natario Date: Fri, 19 Jul 2024 14:30:10 -0400 Subject: [PATCH] remove terminology guide (#708) --- README.md | 1 - terminology/README.md | 15 --------------- 2 files changed, 16 deletions(-) delete mode 100644 terminology/README.md diff --git a/README.md b/README.md index d7d53e39..5b384622 100644 --- a/README.md +++ b/README.md @@ -31,7 +31,6 @@ programming in style. - [Inclusive Culture](/inclusive-culture/) - [Open Source](/open-source/) - [Product Review](/product-review/) -- [Terminology](/terminology/) - [Working Together](/working-together/) ### Protocols diff --git a/terminology/README.md b/terminology/README.md deleted file mode 100644 index 579b125a..00000000 --- a/terminology/README.md +++ /dev/null @@ -1,15 +0,0 @@ -# Terminology - -The language we use has power. Being as concise and descriptive as possible helps to lessen ambiguity. This leads to shared understanding and better outcomes. - -## Terms - -* Use `blocklist`, and not `blacklist`. -* Use `allowlist`, and not `whitelist`. -* Avoid using `master` and `slave`. - * For git, use `main`. - * For databases, use `write database` and `read replica`. - * For other scenarios, use terms such as `parent` and `child` or `leader` and `follower`. Be mindful of scenarios where other commands will create language like, sending `kill` signals to `children`. -* Use terms such as `excused` or `exempted` in place of `grandfathered`. -* Use `negative space`, and not `white space`. -* Use `billable hours`, and not `man hours`.