Divisive Language and what you should know
summary
The foundation directs projects to remove oppressive terms but leaves actual word choices and timing to each technical group, not a central mandate. TripleO already replaces blacklist/whitelist with context-specific alternatives; MariaDB’s newer releases have renamed master/slave upstream. Recommendations include offering multiple replacement options, keeping aliases for backward compatibility (tenant_id → project_id style), auditing docs going forward only, and avoiding a no blanket search-and-replace approach because renaming branches or public APIs is often a major, multi‑year engineering effort.
AI-written summary · about
chapters (7)
- 0:00Meeting logistics
- 3:04Language inclusion stance
- 6:59Implementation strategies
- 17:12Scope and historical context
- 19:29Project-wide engagement
- 36:11Process and resources
- 44:06Community conduct and wrap-up
related talks
05mThe Slings and Arrows of Open Source
30mHow to talk like an Engineer
10mSecurity Starts With Plain Language
04mpreventing Cover-Your-Ass engineering
15mSRE "Power Words"—the Lexicon of SRE as an Industry
40mOpen Discussion on Understanding Cu...
34mNorDevCon2020 Day 2 - Part 8 - James Seconde
25mCognitive biases, blindspots and inclusion