How distributed Open Source projects handle the need for in person trust
summary
Open source communities treat remote-first work as requiring occasional in-person rituals: they run yearly or twice-yearly conferences with recordings plus unconference sessions and long coffee breaks, keep decisions archived in public written form, and use tools like Etherpad, recorded talks and Slack. Practical moves that translate: bundle business trips and extend stays, schedule ritual coffee slots, use random Slack chatbots or breakout rooms for serendipity, and insist decisions remain documented and searchable.
AI-written summary · about
chapters (7)
- 0:00Introduction to trust in distributed projects
- 2:55Why trust is essential for open collaboration
- 4:49Challenges of remote trust building
- 8:43Communication spectrum and trust costs
- 9:48Open source trust-building strategies
- 11:58Cost-sensitive in-person trust tactics
- 15:35Balancing synchronous and asynchronous trust
related talks
23mWhat Makes Open Source Communities Thrive Remotely?
45mPanel Discussion: Open Source as a Second Language
47mDistributed Teams — Can They Work?
21mChanging face of Developer Communities in the time of Covid-19
31mAsynchronous Remote Work
56mBuilding Trust in Teams
28mBuilding bridges beyond the screen: Cracking the code of remote team-building
49mCommunities Over Code: How to Build a Successful Project