**Parent Topic**: [[Software/README]] Hard-won recommendations for distributed (cross-site) SRE projects, distilled from Viceroy: - **Only go cross-site when you must.** The cost is higher action latency and more required communication; the benefit (if you get the mechanics right) is much higher throughput. Single-site has its own cost: no one outside knows what you're doing. - **Vet contributor commitment.** Motivated contributors are valuable, but not equally — beware those joining for a "notch on their belt" or to code on something shiny without committing to maintain it. **Casual contributions dilute ownership**: when the contributor leaves, their features go unsupported and get dropped. - **Divide and conquer.** Split into many reasonably-sized components, each assignable to a small group preferably within one site, with clear deliverables and deadlines — but don't let **Conway's law** distort the software's natural shape. - **Decide locally where trust is high**, with an agreed arbitrator for deadlocks; argue debates fully but with a **strict time limit**, then document and move on. - **Write everything down** (design docs, reviews, standards) to offset distance, and **meet in person** when it matters — team summits at a *neutral* location so no site has home advantage. - **Scale project-management overhead with the project**; start light.