I'm curious how they hold their technical architecture together. Is the architecture mature enough that there are no decisions to be made? I know if I ran my team without syncing up directly on things we'd end up with horrific inconsistencies all over the place and it would become impossible to support. I would guess longer term quality would suffer as well.
how do FOSS projects run by volunteer contributors hold their architecture together?
either one person is calling all the shots, or decisions are made through email discussions or irc or whatever forum they favor nowadays.
synchronous meetings are not required. if you consider that in a meeting everyone takes their turn, people respond to each other, and eventually maybe vote on decisions, all this can be done by email. it just takes a bit longer, and you have to factor that in your time planning.
not having meetings doesn't mean that people don't talk to each other.
They say that they write a lot, so maybe what other organizations do with direct sync up, they do with detailed documents and async discussions around those documents.
