Communication

Abstract From navigating different incentive structures to fostering healthy collaboration, this practical session delivers hard-earned wisdom from 25+ years of open source experience. Whether you’re a newcomer curious about contributing or a seasoned maintainer, “Open Source Survival Guide” offers concrete rules that help technical professionals, community leaders, and companies work effectively in open source environments. Learn how to build trust, share knowledge, handle contributions, and avoid the pitfalls that can damage projects and careers. ...

Pulled directly from the introduction of DevOps’ish 272 Conway’s Law and GitOps are two things that go hand in hand. I’d like that not to be the case, but in building and working with an upcoming demo of multi-cluster GitOps, I’m worried GitOps might not reach an escape velocity over Conway’s Law. Conway’s Law states, “Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.” This might seem natural but think about the different ways we communicate now. E-mail, text messages, phone calls, Slack, Discord, Twitter, etc. are all communication tools that serve various purposes. But, in GitOps, whether you design around a good developer experience (using git as the only interface) or design around a minimalistic amount of tooling (one secret management solution), that tooling has to fit within Conway’s Law usually. ...