alt Hacker NewsOpen source software is not the best argument for distributed teams when you need to iterate fast.
Hell, I had commit rights to a popular open source “AWS Solution” when I was there and it took so long to get something approved to be pushed into the mainline that I ended up forking it for individual customers (AWS ProServe) and then eventually getting most of it merged back in later.
Now that I’m not at AWS, even though I know the team there, I doubt I could get something approved to merge back in even though I was the third highest contributor to the project for awhile.
> Open source software is not the best argument for distributed teams when you need to iterate fast.
You want to actually compete for fast iteration? We'll happily take you on over at ardour.org ...
Yes, there are some FLOSS projects which may take a long time to approve PRs. Even in our case, that happens sometimes when someone proposes something we're not convinced by but also cannot reject immediately.
Meanwhile, it's not unusual for comments in our discourse server to lead to direct changes in the main branch within hours.
So while FLOSS may contain examples against distributed teams, it also contains very strong, and very numerous examples that argue in favor of it.