Paste website: clear direction on the use of oppressive language #510
-
|
We should take an opinionated stance on the use of oppressive language and propose alternatives to common oppressive terms that are unfortunately the standard in many products. We could consider aligning with others in Twilio: https://docs.google.com/document/d/1MgSPsBo4pnjLWa5IQ_oP-71MkvhRsT4CBOV8AHij2lM/edit?ts=5ee8e77d#heading=h.2wmlzn77jhuo |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Tagging @ctecks in here to get this discussion going. |
Beta Was this translation helpful? Give feedback.
-
|
Fully in support of this effort, and heartened about how quickly folks have moved on it. I want to call out Shradha's post in #team-rd-all:
What we can do is consider if there are any UI elements, or UX terminology that might fall into this category of oppressive language. The only one that springs to my mind is "white space", however that's a description of space that is white/clear, and I've heard it used interchangeably with "negative space". Interested to hear if that chimes with anyone, and if folks can identify other terminology, advice, or practices that we can and should address. |
Beta Was this translation helpful? Give feedback.
-
|
I would recommend starting with the defaults and then adding more as we see them. |
Beta Was this translation helpful? Give feedback.
-
|
Small update: I swapped out the usage of blacklist/whitelist in our entire codebase #518. We have a backlogged ticket to remedy master/slave terminology. |
Beta Was this translation helpful? Give feedback.
-
|
Another update: we should no longer have |
Beta Was this translation helpful? Give feedback.
Small update: I swapped out the usage of blacklist/whitelist in our entire codebase #518. We have a backlogged ticket to remedy master/slave terminology.