Making PostgreSQL Hacking More Inclusive
summary
Postgres hacking faces concrete barriers: non‑native English slows long-form emails, off‑list decisions demoralize authors, and time zones mean many threads finish while others sleep — the list averages 140 emails per day with peaks at 10 a.m. UTC and 4 p.m. UTC. Practical fixes include asking for clarification instead of dismissing unclear posts, giving newcomers extra time and a specific critique, documenting off‑list decision paths, and honoring commitments (for example don't commit on Friday unless you can fix fallout immediately).
AI-written summary · about
chapters (6)
related talks
46mPanel Discussion: How to Work with Other Po
24mEverything You Need to Know About Diversity in 25 Minutes
05mDiversity Within the Postgres Community
36mExploring the English Divide: A look at Open Source Inclusion
23mPostgreSQL Europe Diversity Task Force
43mTrying to be Barbie in Ken's Mojo Dojo Casa House
25mCognitive biases, blindspots and inclusion
49mHacking In-Group Bias for Fun and Profit