Communication in Communities - the personnel
summary
Community documentation faces concrete constraints and fixes: four tech writers for nearly a thousand engineers creates a scale problem, so quiet one‑on‑one coaching and short formal writing sessions are the tools used to raise confidence; three recurring contributor needs are identified—Australian‑educated engineers who were told they’re “bad at English,” non‑native speakers who lack formal English training, and people blocked by the “bad at tech” stereotype—and simple fixes (teach acronyms and proper nouns, private review, bite‑size practice) work.
AI-written summary · about
related talks
33mIncluding People
38mNon-native English speakers in OS communities: A True Story
33mBuilding Compassionate Communities in Tech
14mInclusive leadership across cultures: Practical patterns for global engineering teams
49mPanel Discussion: Words Matter: Inclusive Language in Software, Open Source, & the Enterprise
24mWhat is Community Engineering?
50mCreating a Healthy Community Culture
48mPanel Discussion - Women In FOSS