Adopting Open Source Practices To Build More Inclusive Products and Services
summary
Claims that adopting inner source increases documentation quality, code reuse and cross-team collaboration; evidence includes a company-wide single git server with most repos visible internally and production use of reusable Terraform modules that other teams pick up. Concrete practices: add welcome READMEs, assign maintainers, standardize tools, track contributions. Accessibility checklist: swap terms like rename master branch and whitelist/blacklist replacements, add pronouns, compensate community contributors, and deploy language plugins (Slack examples) to surface biased language.
AI-written summary · about
chapters (5)
related talks
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
23mKeeping Your Open Source Project Accessible to All
13mHow can we truly arrive at "open-source everywhere"?
52mBottom-Up Open Source Culture
30mInnersource: open source collaboration patterns beyond public FOSS projects
39mSolving (team) dependencies - the Open Source way
54mInnerSource 101 and the Apache Way
