When words are more than just words: Don't BlackList us
summary
Argument: replace exclusionary words in code tests docs with concrete alternatives, and expect friction not ideology. Action items: replace "master" with "main", update CI and deploy configs, change database/replica names and API docs. Evidence: git adds default branch support, RFCs shift Oct 2018–Feb 2021, login.gov completes a months‑long migration, companies and Linux/Google/Puppet/ GitHub adopt steps. Cost: duplicated branches, config edits, deploy pipeline fixes, and integration tests—doable but requires planning and follow‑through.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:46Main actors are willing to change
- 15:23Ask politely!?
- 16:37Propose Alternatives!?
- 18:38Contact maintainers!?
- 19:36It may not that easy to ask!?
- 26:00Be prepared
- 29:04We all need to be involved
related talks
49mPanel Discussion: Words Matter: Inclusive Language in Software, Open Source, & the Enterprise
41mWords Matter
36mInclusive, Accessible Tech: Bias-Free Language In Code And Configurations
15mAdopting Open Source Practices To Build More Inclusive Products and Services
47mCode Cowpokes and Word Wranglers: from Mutual Admiration to Solidarity
32mBuilding inclusive Open Source communities
23mKeeping Your Open Source Project Accessible to All
40mKeynote: Who and What We're Leaving Behind